Done: an MCP tool (or a kind of the existing explore/app tool) answers an app's tree as plain rows: owner, how it follows its upstream, commits behind, last change; a stranger sees only public forks; a test compares its words to the tree page's. Suggested: mason.
Risks: Two sets of wording: share one function between page and tool.
Read AGENTS.md and docs/PRINCIPLES.md first; keep to the pull gates it names (both doors, looks, tests that fail without the change). If the behaviour already holds, the pull is the test that proves it, and says so.
Done: an MCP tool (or a kind of the existing explore/app tool) answers an app's tree as plain rows: owner, how it follows its upstream, commits behind, last change; a stranger sees only public forks; a test compares its words to the tree page's. Suggested: mason.
Risks: Two sets of wording: share one function between page and tool.
Read AGENTS.md and docs/PRINCIPLES.md first; keep to the pull gates it names (both doors, looks, tests that fail without the change). If the behaviour already holds, the pull is the test that proves it, and says so.
Files: src/http/mcp/, src/web/pages/family.ts, test/mcp-fork-tree.test.ts, docs/MCP.md