docs(docs): accept typed effect seam and plan rollout

[coreplane-switchboard]

Accepts decision record 0074 and adds an implementation-ready four-unit plan for runner-owned side effects. This gives push, rebase, GitHub writes and connectors one typed receipt boundary without granting child shells write authority.

Why: The record proposal passed its cold-reader gate, while #2197, #2196 and #2200 confirmed that effects the runner does not perform cannot be authoritative transition facts.

Where to look

1. Accepted record status Promotes record 0074 from proposed to accepted; generated decision documentation follows this source.
2. Acceptance re-evaluation Records the cold-reader and review gates, restates both halves of the bet, and adds the two post-proposal fixtures.
3. Plan authority and rollout Sets four person-merged units, one-release shadowing, shared spec obligations and fail-closed stop conditions. ⚠ A loose stop condition could let implementation weaken an existing guard.
4. Push product contract Makes exact-tree gates, runner receipts, directive-run publication and shell-route removal explicit U1 requirements. ⚠ This contract decides what may publish and what counts as ready.
5. Remaining effect contracts Defines the shared rebase service, marker-reconciled GitHub writes and compile-time connector registry.
6. U1 acceptance fixtures Binds the parser, exact-tree, readiness and directive open-PR cases to runnable proofs, including issue 2200.
7. Cross-unit verification contract Names the bound proof and receipt-runnable predicate for the documentation change and each implementation unit.

Feedback wanted: Check that U1 fully covers directive and ship-parented coding runs, and that each unit's receipt predicate is concrete enough to become its contract.

Risk: Docs-only, but this plan governs four security-sensitive implementation PRs. A missing fence could preserve a rival write route; rollback is reverting this PR before implementation begins.

Verified: Passed decisions:check, docs:check, specs:check, hygiene:check, scoped Prettier and the PR-title gate; CI remains the full gate.

Decisions (3)

• Keep record-number reservation out of these four units. Issue ship: two record-writing children pick the same next free record number (#2194 and #2195 are both 0074) #2196 proves the same runner-owned-effect rule, but record 0074's accepted rollout already has four bounded units. The plan records reservation as follow-up rather than hiding a fifth effect inside connector work.
• Expose shadow and on, never two writers. Shadow must observe without writing while the legacy path publishes for one release. On removes the shell route, so no steady state can treat both legacy shell publication and typed push as authoritative.
• Put typed push on every coding harness. Issue execution: repo:use refuses a directive run's push to the branch it was told to work on when that branch heads an open PR #2200 occurred in a directive run, not a ship child. The boundary belongs to the coding harness, with ship readiness as one consumer of its receipt.

Validation (6 criteria)

Criterion	Proof
Record status and accepted-body rules remain valid	npm run decisions:check passed: 114 records valid; accepted-body amendment rules passed against origin/main.
Generated decision index reflects accepted record 0074	npm run docs:gen updated docs/explanation/design-decisions.md; npm run docs:check passed for all 12 generated sources.
Plan references valid spec and code/test paths	npm run specs:check passed: 51 specs and 5680 proof references checked; every Code/Tests path exists.
Public documentation adds no unrecorded private imprint	npm run hygiene:check passed: 9 files checked, existing allowed hits unchanged.
Changed documentation is formatted	npx prettier --check on the decision, plan and generated index passed.
PR title follows repository release grammar	npm run check:pr-title -- "docs(docs): accept typed effect seam and plan rollout" passed.

For agents

Branch rebased onto origin/main at 57a0e07 before push; pushed head is f75abf6. docs/explanation/design-decisions.md is generated by npm run docs:gen; review its status-row change but do not hand-edit it. No runtime code or tests changed.
Requested by @justinhelmer in slack:C0BRRHKFLCB

🤖 Generated with Claude Code

[coreplane-switchboard]

LGTM: The acceptance amendment and implementation plan are internally consistent, preserve the decision-record history, and bind each rollout unit to concrete proofs.

Note

Approved · head f75abf6 · no findings

Full review

No findings; the acceptance amendment and implementation plan are consistent and ready to merge.

[github-actions]

Auto-approved: coreplane-switchboard[bot] reviewed this PR and posted an LGTM verdict (see its review). This repository opted in through its REVIEW_BOT_LOGIN and REVIEW_BOT_ID variables.