Unified Documentation Set
Documentation With One Source
A documentation migration that joined website pages, installed docs, generated inventories, and CLI help.
4 milestones 14 tasks 53 agents
5 plan 14 execute 22 review
238k peak context
135k median execute
7h 22m total 13m 27s per task
9m 52s plan 1h 53m execute 1h review
165 edits 1.7k commands
codex harness
This run moved Gantry's published documentation toward one root `manual/` source set. Its milestones separated authored pages, generated inventories, installed documentation, and the retired manual command so each boundary could be checked without treating documentation as a single opaque change. The current tree retains the root source set, generated reference pages, installation-time materialization, and the shorter help surface. One website-rendering claim cannot be confirmed: the source-document view remains, but its reader and copied manual directory are absent from the current tree.
How this walkthrough is structured
Feature
What did the run build and ship?
The tree still has the root manual, generated reference markdown, materialized documentation, and usage help, while the website source-document reader is no longer present.
Build
How did Gantry structure the work?
The cut divided a documentation migration into authored source, generated reference material, installed copies, and the command surface that points readers to them.
Milestone 1
Manual Source Set
4 tasks 13 agents 1h 10m wall time 187k peak context
`manual/README.md` and the published pattern documents remain in the root `manual/` directory. The website still has the source-document partial that calls `Docs::SourceDocument`, but the current tree has neither `web/app/models/docs/source_document.rb` nor `web/app/documents/manual/`. The authored source set is therefore present, while the claimed website rendering path cannot be confirmed from the current tree.
This milestone carried the authored-page move into `manual/` while preserving existing website addresses and navigation. Its boundary was coherent for a fresh agent because page content, links, and rendering ownership all belonged to the published source set. The ledger marks the milestone green, but the run facts do not attribute stage results to individual milestones. That leaves the digest, rather than stage history, as the evidence for this boundary.
Milestone 2
Inventory Markdown Export
4 tasks 13 agents 1h 10m wall time 201k peak context
The root `manual/` directory contains generated CLI, configuration, handover, journal, harness, MCP, menu, pattern, and prompt pages. Those files identify `gantry export-reference-markdown manual web/app/documents/manual` as their regeneration command. The reference dataset and CLI specification remain the code-side sources for that export. The generated markdown contribution is still directly checkable.
This milestone moved code-backed inventories into generated markdown within the same source set. A fresh agent could hold the work because the contract joined one exporter, checked-in output, and website ownership rather than revising each inventory by hand. The ledger records a green result, and the run facts provide no milestone-local repair or replan record. The boundary was generated reference material, not prose revision.
Milestone 3
Materialized Docs
3 tasks 11 agents 37m 40s wall time 153k peak context
`src/engine/config.rs` embeds `manual/` as bundled documentation and materializes it under the configuration root's `docs/` directory. Its tests cover the default configuration location, a `GANTRY_CONFIG` location, replacement of edited documentation, and exclusion from managed defaults. The packaging documentation and source-archive script also name `manual/` as shipped source documentation. This materialization path remains visible in the tree.
This milestone put the published source set into the runtime configuration lifecycle and source archive. Its scope was narrow enough to isolate installation behavior from page authoring: embed the manual, write the docs tree, replace local edits, and keep it outside managed defaults. The ledger marks the work green, while the run facts do not retain milestone-level stage attribution. The brief supplies the architectural boundary.
Milestone 4
Help And Removal
3 tasks 11 agents 1h 25m wall time 238k peak context
The command specification retains `gantry agents init` as the agents surface. `src/commands/mod.rs` directs invalid agents usage and the installed orientation text to `~/.config/gantry/docs/README.md`, while the CLI specification defines the short usage rows. The archived plan records the removed topic reader, and the current command code no longer exposes it. The help and removal result can be confirmed against the tree.
This milestone removed the old manual-reader surface after the documentation set and materialization path were available. The fresh-agent boundary was the command contract: keep `gantry agents init`, make general help a usage message, and point readers at the installed index. The ledger is green and no milestone-local recovery appears in the run facts. That makes this a propagation and removal boundary rather than a recorded stress point.