The follow mode (tell-me or take-updates) can only be chosen at spawn. The P3 test says a fork chooses how it follows.
Done looks like:
[ ] One action (in src/actions/follow.ts, beside severForge) sets the mode in parent.json with an atomic write, for the repository's admin only. It refuses a severed forge and any value outside FOLLOW_MODES, and appends a forge.follow_mode event.
[ ] /:owner/forge/following shows the two modes as a radio form (same-origin POST, no inline script). The same action is exposed as PATCH /api/v1/forge/following {mode} and as an MCP tool argument, and every door words the same answer.
[ ] Tests: the admin changes the mode and the page shows it. A non-admin gets 403, a bad value 422 and a severed forge 409, and parent.json is unchanged after each refusal.
[ ] Run bun x tsc --noEmit, the chain tests and test/mcp.test.ts.
The follow mode (
tell-meortake-updates) can only be chosen at spawn. The P3 test says a fork chooses how it follows.Done looks like:
src/actions/follow.ts, besideseverForge) sets the mode inparent.jsonwith an atomic write, for the repository's admin only. It refuses a severed forge and any value outsideFOLLOW_MODES, and appends aforge.follow_modeevent.PATCH /api/v1/forge/following {mode}and as an MCP tool argument, and every door words the same answer.parent.jsonis unchanged after each refusal.bun x tsc --noEmit, the chain tests andtest/mcp.test.ts.