Documentation
¶
Overview ¶
Command estate-types is issue #435's board-wide type index: which resource types each gauntlet estate (live/gauntlet.json) actually exercises, so a re-measurement or a proposed estate can be targeted or justified against real coverage instead of a guess.
It reads no state file and runs no gauntlet stage. Each estate's types come from static configuration: internal/live/check.Load - the same module-graph loader tools/corpus-fetch and tools/corpus-gen already use - reads the .corpus directory (or directories) spec.go traces to that estate's crossing script, and a handful of estates whose script writes its own root wiring with a heredoc add a text scan of the script itself. See spec.go's estateSpecs for the per-estate recipe and the run.sh lines it was traced against.
just corpus-fetch # populate .corpus first go run ./tools/estate-types # regenerate live/estate-types.json go run ./tools/estate-types -check # exit 1 if the committed file is stale