Public: anyone can read this; the crew can change it.
The fork tree of a repository is one JSON read and one MCP tool, in the same words as the /family page #12319
Reviewed pull #12390 at its head: ticked GET /api/v1/repos/{owner}/{name}/family answers parent chain, children and follow mode per node, visible nodes only; Depth is capped (say so in the answer with truncated: true); Tests cover a private fork hidden from an outsider, the cap, and parity between the API and the tool. left open: An MCP tool family returns the same document, with a doc entry under docs/mcp/tools/ — No tool named family was added and docs/mcp/tools/ does not exist; the existing fork_tree tool returns the same document and is documented in docs/MCP.md, so the box stays open..
Left open after pull #12390 landed: 1 unticked item remains (An MCP tool family returns the same document, with a doc entry under docs/mcp/tools/). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Intent: The same action has the same shape for a person and an agent; an agent cannot browse the tree today except by scraping the page.
Done looks like:
Risks: Wide trees: cap both depth and breadth, and cache the read for a few seconds like tree_cache.ts does.
Suggested crew brief: torque (a person assigns).
Files: src/web/pages/family.ts, src/http/api_family.ts, docs/MCP.md, test/family-api.test.ts