[P0] Private beta launch decision and cohort activation

[yacosta738]

Objective

Run the final go/no-go for the private beta and activate only a small cohort whose invitation, workspace access, support path, and publishing path are ready.

Classification

• INCOMPLETE launch-control work.
• Not blocked by LinkedIn provider approval.
• Publishing/scheduling evidence must remain USER_REPORTED_OPERATIONAL and must not be reclassified as provider-verified or multi-user-verified by this issue.

Exit gate

• Activate waitlist in production (flip toggle + pre-launch QA) #470 is complete, or an explicit exception is approved.
• [P0] Private beta release gate: VPS publishing/scheduling evidence, rollback and support runbook #651 is complete.
• [P0] Private beta invite and activation operations #652 is complete.
• [P0] Private beta operations: health, failure visibility, backup and rollback #653 is complete.
• [P0] Private beta user journey: first login, connect account, compose and schedule first post #654 is complete.
• A named cohort exists.
• Initial cohort size is defined.
• Support owner is defined.
• Daily review cadence is defined.
• Incident channel is defined.
• First invitation batch is prepared.
• Activation tracking is ready.
• First 24-hour review is scheduled.
• Every failure has an owner and next action.

Cohort policy

• Start with a small, manually approved cohort.
• Invite only users who accept the beta scope and supported-provider limitations.
• Do not claim provider verification or multi-user verification.
• Keep a rollback path that can stop new invitations and safely disable worker execution if needed.

Definition of done

• All exit-gate prerequisites are complete or explicitly accepted as exceptions.
• Named cohort, initial batch size, support owner, review cadence, and incident channel are recorded.
• First invitation batch is sent and activation outcomes are tracked.
• First 24-hour review is scheduled and owned.
• Any failed activation or publication has an owner and next action.
• No provider-verified or multi-user-verified claim is introduced.

[linear-code]

DALLAY-559