catalog-integrity

Topics in the source

• Catalog integrity
• Use when
• Callable command
• Inputs and outputs

Run after changing a skill contract, family metadata, evidence artifacts, catalog derivation, or generated catalog assets. The command runs the existing artifacts/forge/scripts/build-catalog.js and test-catalog.mjs from their migrated workspace locations. It builds the catalog and project summary in a temporary validation directory, and checks an unchanged copy of the source manifest before generation can conceal inventory drift. A local check does not rewrite tracked release metadata. If it reports stale inventory, run node artifacts/forge/scripts/build-catalog.js and include the refreshed manifest in the source change. The validator allows a shallow checkout for local inspection. CI retains strict history checks and uses the same --check-manifest guard. Publishing still regenerates release metadata. Input: the current checkout's root distribution families and generated artifacts/forge/public/data/ assets. Output: concise pass/fail lines and a non-zero exit on invalid counts, metadata, evidence vocabulary, payload split, or provenance. Never paste credentials into the command. A local shallow-history warning is not a release pass; a CI shallow-history failure blocks publishing.