[Chat v1 P7] Execute OS acceptance, staged rollout, and rollback drill

[CompleteDotTech]

[Chat v1 P7] Execute OS acceptance, staged rollout, and rollback drill

Run the complete no-source-checkout acceptance journey on all supported operating systems, then stage rollout with ready rollback metadata and prior artifacts.

Owner repository: OpenCoven/coven-cave (program tracker)
Execution lane: release-acceptance
Plan of record: OpenCoven/chat/docs/superpowers/plans/2026-08-15-phase-7-release-rollout.md

Deliverables:

• Install/pair/read/send/resume/restart/attachment/action/revoke/update acceptance on macOS, Windows, and Linux.
• Global opencoven doctor/pair/session/send/tail/scaffold acceptance.
• Low-percentage rollout, health thresholds, pause criteria, and rollback drill.

Acceptance criteria:

• The full release acceptance journey passes on all supported OSes.
• Prior stable artifacts and rollback metadata are verified before rollout.
• Crash, auth, duplicate-send, and data-integrity regressions stop rollout.

Bead metadata

• Bead ID: cave-udcn7

• Status: open

• Priority: P0

• Surface: Shared

• Authoritative owner: Unassigned

• Labels: area:rollout, needs-human, phase:7, program:chat-v1, release-blocker, repo:cross-repo, surface:shared, verification-required

• Parent: None

• Dependencies: cave-as76u, cave-j65ie

Source of truth

Beads is authoritative. This draft card is a GitHub Teamwork visibility mirror and should be reconciled from the Bead rather than edited as an independent task.

[BunsDev]

Closing this accidental repository-issue conversion. The canonical task remains the Bead mirrored as a draft card on the Teamwork project; Beads remains the source of truth.

[CompleteDotTech]

Reopened: this is unblocked and the remaining work is real.

Why it was blocked, and why it no longer is. Bead cave-udcn7 was blocked by cave-0wg (Phase 7 Task 1, client-v1 release compatibility metadata). That work has landed: PR #4785 squash-merged 2026-08-21T18:19:43Z as 96627be5a. Verified against origin/main — src/app/api/client/v1/health/{route.ts,route.test.ts}, scripts/client-v1-release-smoke.{mjs,test.mjs}, and src/lib/server/client-v1/contract-fixture.json are all present, and scripts/ci-paths.mjs CLIENT_V1_PATH now matches client-v1-release-smoke (the specific gap that bead's acceptance criteria called out). cave-0wg is closed.

What is already done here. This issue's own code shipped: PR #4789 merged as df5c72aac, adding scripts/release-acceptance.mjs and scripts/release-rollout.mjs (56 tests) plus docs/workflows/{release-acceptance,production-rollout}.md, composing with #4782's rollback-readiness gate.

What remains — and it is not automatable. The three-OS acceptance journey is human execution. This closes only when a validated record lands in docs/release-acceptance-results/: the no-source-checkout acceptance journey passing on macOS, Windows, and Linux; global opencoven doctor/pair/session/send/tail/scaffold acceptance; and the staged rollout with a rollback drill, with prior stable artifacts and rollback metadata verified before rollout begins.

Closing this as NOT_PLANNED previously did not reflect its state — the work is planned and now unblocked.

Related, and still open: cave-7yo. The reconciliation it describes did not happen in the recommended order — it advised landing phase1a/cave-pairing-authority first and rebasing #4785 onto it, but #4785 landed first. phase1a/cave-pairing-authority is unchanged at 287497dd3 with no PR open, and still carries its own competing src/app/api/client/v1/health/route.ts. The 10-file collision is unresolved and now falls on whoever lands phase1a.