Threads landed in the accounts drawer, alongside Instagram, Facebook, and LinkedIn. The publish engine routes text, image, and carousel through each network API correctly (Threads uses 2-step containers). LinkedIn got real carousels via document share: the system builds a PDF from the slides and publishes it as swipeable cards in the feed.
The Social Inbox landed in the Marketing Studio sidebar. Comments from Instagram and Facebook show up in a single list with per-network filters, unread counter, reply composer, and archive. Two sources run in parallel: a 10-minute cron as a fallback and a Meta webhook that, once wired up, delivers new comments in milliseconds with HMAC validation.
In the visual editor, Reels got destructive video editing via ffmpeg.wasm right in the browser, with start and end sliders and a live preview. When the canvas has text or shapes over the video, publish does burn-in: it captures the Konva overlay, composes it over the trimmed video, and uploads the final mp4 as the Reel. The 1-click repurpose clones the post into 4 other aspect ratios (1:1, 4:5, 9:16, 1.91:1, 16:9) with a smart-resize pass that detects full-bleed layers and adjusts the focus crop of vertical images.
The intelligence layer grew. The composer now generates caption variants A, B, and C per platform, and the engine alternates between them on every publish with a stable hash (the same job on retry picks the same variant). Before publishing, an estimate panel shows predicted reach and engagement (p25 to p75 with a confidence tier) based on your past posts, and flags when the chosen time matches your top historical slots. Hashtags generated by the AI can be scored against your corp history, bucketed as hot, warm, cold, new, or unknown.
Underneath, the publish cron got tougher: job claim is now atomic via FOR UPDATE SKIP LOCKED in a dedicated Postgres function, so two concurrent workers never grab the same job even if Vercel fires overlapping invocations. The Marketing Studio sidebar now surfaces Calendar, Inbox, Social Analytics, and Brand Kit as their own entries. Everything is localized in pt-BR, en, and es. X (Twitter) support and LinkedIn Inbox shipped in code but are off for now: X is pay-per-use and we want to validate with Brazilian SMBs before turning it on, and the LinkedIn Inbox requires a dedicated app per Community Management API rules and lands when concrete demand shows up.