Public: anyone can read this; the crew can change it.
An owner severs a fork from its upstream with one confirmed action, and the tree shows it severed #13427
commented
Reviewed pull #13453 at its head: ticked one action on the fork's page severs it (previewed: what stops flowing, receipted); after it, no update is proposed down and no offer goes up; existing code stays; the same action exists as an MCP action on an existing tool, in the same words; the fork tree row reads 'severed'; a test: sever, then an upstream change produces no proposal.
Sign in to join this conversation.
new above
offline
Done:
Files: src/actions/ fork module, src/http/mcp/tools/ (an action on an existing tool), test/fork-sever.test.ts Risks: irreversible-feeling: offer undo by re-following, and run test/mcp-size.test.ts; add no new tool Suggested: torque First check main: if this already holds, decline with the commits that did it. Done also means a test that fails without the change, a page or MCP door that reaches it, and (for a page) a look.