Context
The pipeline that turns a repository into a wiki exists end to end, and nobody can run it without already knowing the ordering. It spans two MCP servers, and the ai-architect server's own instructions say the ordering "is not guessable; a caller that gets it wrong gets an empty or misleading result rather than an error."
Tools in this category are one command that prints a path to a file you can open. Until that exists here we have capability and no product — and any head-to-head measurement is measuring an operator's memory of a tool sequence rather than an artifact.
This is the prerequisite for the evaluation in cdeust/ai-architect-mcp-codebase#197, not a follow-up to it.
Scope
A skill that runs the existing ordering (index → resolve → cluster → skeleton export → ingest → page write) and prints the absolute path of the generated index.md.
Chaining only. No new generation logic in this issue. If this starts growing a generator, it has drifted into the narrative-fill issue and should stop.
Acceptance criteria
- A single invocation against a clean checkout of an unindexed repository produces a directory containing
index.md plus one page per community, and prints its absolute path.
- Every internal link in
index.md resolves to a file that exists. Asserted by a test that walks the emitted links, not by reading the generator.
- Each prerequisite failure (no index, unresolved graph, no clustering) fails loudly, names the missing step and the command that satisfies it. Each arm has a test asserting the emitted message itself, not only a non-zero exit.
- The nominal path emits no warning. Asserted.
- No prose-generation code is added; the diff is wiring.
- Test isolation: the run binds to a temporary
CLAUDE_DIR and a temporary store, never the real ones.
- An empty or unparseable repository produces a valid wiki stating that it is empty, with a count assertion. A run that silently does nothing must fail the test.
- Completion Ledger in the PR.
Out of scope
Context
The pipeline that turns a repository into a wiki exists end to end, and nobody can run it without already knowing the ordering. It spans two MCP servers, and the ai-architect server's own instructions say the ordering "is not guessable; a caller that gets it wrong gets an empty or misleading result rather than an error."
Tools in this category are one command that prints a path to a file you can open. Until that exists here we have capability and no product — and any head-to-head measurement is measuring an operator's memory of a tool sequence rather than an artifact.
This is the prerequisite for the evaluation in cdeust/ai-architect-mcp-codebase#197, not a follow-up to it.
Scope
A skill that runs the existing ordering (index → resolve → cluster → skeleton export → ingest → page write) and prints the absolute path of the generated
index.md.Chaining only. No new generation logic in this issue. If this starts growing a generator, it has drifted into the narrative-fill issue and should stop.
Acceptance criteria
index.mdplus one page per community, and prints its absolute path.index.mdresolves to a file that exists. Asserted by a test that walks the emitted links, not by reading the generator.CLAUDE_DIRand a temporary store, never the real ones.Out of scope