jupiter:adopt

To consolidate scattered spec files into a unified docs tree, run the adopt pipeline on your repository. It centralizes specs under a canonical docs/master-spec structure organized by module or feature and emits an index.json for discovery.

Yes, you can incrementally update a master-spec tree without rebuilding everything. The workflow supports incremental updates and safe re-writes, allowing you to canonicalize new specs while preserving existing documentation structures.

Yes, this spec consolidation workflow works for both multi-module and single-module repositories. It orchestrates reorganization into a canonical docs tree and applies frontmatter-driven configuration to scale across different repository structures.

You auto-generate surface stubs for undocumented code by running the adopt pipeline. It automatically emits surface stubs during the spec consolidation process, enabling surface augmentation and identifying undocumented code areas.

The best way to resolve file move conflicts when reorganizing spec files is using the pipeline's auditable file moves with safe conflict handling. You can also use the --force flag to safely rebuild the master-spec tree from scratch.

To analyze behavioral gaps in your consolidated documentation, run the adopt pipeline with the --deep flag. This enables behavioral-gaps analysis alongside the standard per-bucket split-candidate analysis emitted in the index.json.