[P2][Plan 5] SF-024 — Make publishing secondary to review, save, and export

[Ankit6149]

Confirmed problem

When an official connector is available, the primary dark action becomes Publish approved draft. This makes the product feel like a publishing dashboard even though its intended position is review-first content creation with deliberate handoff.

Scope

• Keep Save, Copy/Open, and Export as the primary review actions.
• Move direct publishing into a secondary deliberate area.
• Require the current draft to be non-stale, approved, connector-ready, and permission-valid.
• Show destination account/context and require confirmation before a live post.
• Never present a successful publish state without platform/API confirmation.

Acceptance criteria

• Publishing is not the dominant default action in Review.
• A stale, failed, unapproved, or needs-review draft cannot publish.
• The confirmation identifies platform/account and current draft version.
• Copy/export/manual handoff remains complete when no connector exists.
• API failure cannot appear as published.

Required verification

• Action-priority UI tests.
• Publish guard matrix.
• Connector unavailable/rejected/success/failure fixtures.
• Keyboard and confirmation-dialog tests.