docs/SPAWN.md (around line 86–93) still says the follow modes are "the owner's recorded choice" that nothing acts on. Since #2631–#2656 they act: an hourly check fetches the parent's code; tell-me sends one inbox card per new tip with its commits; take-updates opens or updates one take pull that a person merges; the chain page, API, terminal and MCP offer take-now; sever stops it all.
Done looks like:
[ ] A section "Following the parent forge" in docs/SPAWN.md says the above in a few short paragraphs: what is fetched and where (refs/upstream/*, upstream.json), how often (CHECK_MS), what each mode does, the take branch name, and what never happens (main is never moved, nothing auto-merges). It replaces the stale sentences.
[ ] A test reads the doc and fails if CHECK_MS, TAKE_BRANCH or either value of FOLLOW_MODES (from src/spawn/upstream.ts, src/spawn/take.ts and src/spawn/chain.ts) is not in it, the way test/cluster-doc.test.ts keeps docs/CLUSTER.md honest. Name it in GATE in scripts/gate.ts.
docs/SPAWN.md(around line 86–93) still says the follow modes are "the owner's recorded choice" that nothing acts on. Since #2631–#2656 they act: an hourly check fetches the parent's code; tell-me sends one inbox card per new tip with its commits; take-updates opens or updates one take pull that a person merges; the chain page, API, terminal and MCP offer take-now; sever stops it all.Done looks like:
docs/SPAWN.mdsays the above in a few short paragraphs: what is fetched and where (refs/upstream/*,upstream.json), how often (CHECK_MS), what each mode does, the take branch name, and what never happens (main is never moved, nothing auto-merges). It replaces the stale sentences.CHECK_MS,TAKE_BRANCHor either value ofFOLLOW_MODES(fromsrc/spawn/upstream.ts,src/spawn/take.tsandsrc/spawn/chain.ts) is not in it, the waytest/cluster-doc.test.tskeeps docs/CLUSTER.md honest. Name it inGATEinscripts/gate.ts.bun x tsc --noEmitand the new test.