Harden cross-platform publishing, reconciliation, and deletion

[0thernet]

What changed

• Harden image publishing for X, LinkedIn, Bluesky, Substack Notes, and Threads.
• Retain provider-accepted targets and reconcile them through exact read-only evidence.
• Add deterministic duplicate-risk successor intents without clearing prior evidence.
• Add exact current-account Bluesky post deletion using URI/CID revision binding and authoritative absence proof; keep unproven deletion paths unavailable or capture-required.
• Update the cross-post skill with settlement, duplicate accounting, headed execution, and cleanup guidance.
• Preserve the primary worktree's Google contacts/Gmail, Substack inline-audio, and isolated local-development work.
• Reconcile provider semantic identities, adapter archives, and contract inventory with automated source-closure integrity.

Why

Several publish runtimes crossed the durable dispatch boundary before preparatory image upload completed, while accepted provider identifiers were not persisted before independent readback. Upload-only failures could therefore look possibly applied, and successful creates followed by readback drift could not be reconciled exactly.

Deletion needed a narrow, evidence-backed semantic exception instead of weakening the global high-authority boundary.

Impact

Pre-create failures are safely retryable. Provider-accepted writes retain their exact targets for settlement. Duplicate-tolerant publication is explicit and linear. Bluesky cleanup can delete only an exact authored revision; other unproven deletion paths remain fail-closed.

Validation

• bun run check
• 2,542 main tests passed
• 18 heavy omni tests passed
• 0 failed
• package, website, build, standalone smoke, and skill validation passed

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
wrench	Ready	Preview	Aug 19, 2026 8:55pm