• Safe retries on POST /v1/posts: Send an Idempotency-Key header with your post creation requests and retry safely if a request times out or your connection drops. A retry with the same key and body returns the original result (marked with Idempotency-Replayed: true) instead of creating a duplicate post. Reusing a key with a different body returns a 422, a request still in flight returns 409 with Retry-After, and keys expire after 24 hours so you can reuse them for a genuinely new request. If a post was created but publishing hadn't been scheduled yet when a retry comes in, we return that post as-is rather than scheduling it again; use PATCH to set a scheduledAt when you're ready.
• Fixed tenant isolation for Facebook and LinkedIn connections: Accounts connected through the dashboard with a tenant_id for Facebook or LinkedIn are now correctly tagged with that tenant, matching how Google Business connections already worked. Previously these accounts lost their tenant association, so they could be missing from tenant-filtered account and post lists, and reconnecting the same account under a tenant could create a duplicate entry.