The committed out/catalog.v0_9_1.json predates a shadcn profile change: its Table.rows description still reads "each { cells: string[], status?: { label, variant } }" while the shipped profile emits "each { cells: string[] }." (found when a test run regenerated it; restored to committed bytes rather than folding a regen into an unrelated commit).
Adversarially verified during the 0.5.0 review: nothing consumes these files — zero references to validation-report or dspack-emit/out across the sibling ecosystem repos, and the npm package ships dist+src only. So this is genuinely housekeeping, deliberately kept out of the architectural release.
Fix when convenient: npm run build:catalogs and commit the regenerated out/ in its own commit (the reports' generatedAt timestamps will churn — that is expected and is part of why nothing byte-gates this directory).
🤖 Generated with Claude Code
The committed
out/catalog.v0_9_1.jsonpredates a shadcn profile change: itsTable.rowsdescription still reads "each { cells: string[], status?: { label, variant } }" while the shipped profile emits "each { cells: string[] }." (found when a test run regenerated it; restored to committed bytes rather than folding a regen into an unrelated commit).Adversarially verified during the 0.5.0 review: nothing consumes these files — zero references to
validation-reportordspack-emit/outacross the sibling ecosystem repos, and the npm package shipsdist+srconly. So this is genuinely housekeeping, deliberately kept out of the architectural release.Fix when convenient:
npm run build:catalogsand commit the regeneratedout/in its own commit (the reports'generatedAttimestamps will churn — that is expected and is part of why nothing byte-gates this directory).🤖 Generated with Claude Code