On a fork, the page manifest offers its writer how it follows its parent: read it, take the parent's updates, propose its changes up #7864

The manifest for a fork now offers its writer three moves: read how it follows its parent, take the parent's updates, and propose its changes to the parent. bun test test/here-manifest.test.ts test/mcp-size.test.ts and bun x tsc --noEmit pass. bun scripts/gate.ts printed nothing, which I read as clean without checking its exit code.

• The change: repoActions in src/actions/here.ts adds the three actions in their own block at the end, after the participant actions, so it merges cleanly with #7854. The block applies when forkParentId !== null, origin === null and the viewer passes canWrite.
• The routes: they are GET {r}/following, POST {r}/following/take and POST {r}/following/propose-parent. The write check matches requireWriter, which propose-parent calls directly. I did not read takeOrTell, which handles take, so the match for take is unchecked.
• Read-only tokens and signed-out visitors: they never reach the block, because it sits after the if (!acts) return out; guard.
• Test: test/here-manifest.test.ts has one new case. A writer of a fork sees all three. A reader and a signed-out visitor of the fork see none, and a writer of the plain repository acme/game sees none. I did not run it with the change removed. The writer assertions can only pass with the new block.
• Left out: the read-only-token case has no test of its own; it relies on the existing acts guard. I also did not offer the other following routes (sever, propose, proposals, converge), since the issue named only these three.

Closes #7856

On a native fork, the page manifest now lists three actions for its writer: read how it follows its parent, take the parent's updates, and propose its changes to the parent. Each entry now names its MCP tool, so an agent reading the manifest is offered more than HTTP.

• MCP names: following, take_updates and propose_to_parent_forge. The existing test now asserts all three. tsc and test/here-manifest.test.ts pass (20 tests), and I did not run any other test files. I ran bun scripts/gate.ts; it printed nothing and I did not read its exit status.
• unproven: I left it off the two writes. Neither src/actions/follow.ts, src/actions/upstream.ts, src/http/api/following.ts nor the two MCP tools asks for a verified email, only writer access. The manifest should not advertise a gate the actions don't apply. If you want verification required, that is a change to the actions themselves, and the manifest would follow.
• Terminal door: src/tui/screens/forks.ts covers all three. It shows following, t takes the parent's updates after a confirm (takeOrTell), and the same screen proposes upstream (proposeUpstream). That screen needs a writer, so a reader gets nothing.
• README: it doesn't list manifest actions, so I made no README change.

The full-suite proof of this head is waiting: no check slot is spare. It starts when one frees.