jupiter:rewrite

To consolidate master specs into a single document, the rewrite workflow orchestrates cataloging and scanning to merge scattered module-level specs into one coherent master file per module. It also generates a sidecar index to track provenance.

A sidecar consolidated-index.json is used to track provenance and structure during spec consolidation. It summarizes the buckets, topics, and origins of the unified master specs to maintain clear documentation lineage.

Yes, you can safely clean up original source files after consolidating specs because the workflow prompts for optional deletion. It never deletes original sources without explicit consent, ensuring your data remains protected.

Spec consolidation works specifically for multi-module project setups to unify module-level specs and surface stubs. It orchestrates the cataloger, scanner, and writer workflow to produce consolidated documentation for each module.

The best way to unify scattered Jupiter master-specs is running the consolidation workflow. It orchestrates the cataloger, scanner, and writer to merge documentation while emitting a sidecar index to capture provenance.

You should not delete original sources during a spec rewrite if you want to preserve raw documentation lineage. The workflow includes safeguards that prompt before deleting, ensuring you only remove files with explicit consent.