fix(flows): keep catalogVersion 4 (unbreak deploy), retain v2.0.42 source bump
The v2.0.42 bump also raised catalogVersion 4→5, which failed the deploy's verify-catalog-gates.mjs step (catalogVersion is pinned to 4 as the schema version). Reverts catalogVersion to 4; keeps software-factory source pinned to v2.0.42. npm run verify:recommended-flows passes both gates.
🤖 Generated with Claude Code
[!NOTE]
Low Risk
Metadata-only catalog version alignment with existing deploy verification; no runtime or source pin changes beyond fixing the version field.
Overview
Reverts an accidental catalogVersion bump from 5 back to 4 in recommended-flow-catalog.v1.json so deploy’s verify-catalog-gates.mjs (which pins schema 1 / catalog 4) passes again.
The companion check in verify-recommended-flow-catalog.mjs is updated to expect catalogVersion 4 as well. The software-factory flow source pin to v2.0.42 (ref, sha256, etc.) is unchanged—only the top-level catalog version field was wrong.
Reviewed by Cursor Bugbot for commit 1c80595ad09f0a89af7743bb19e95b45033958cd. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by cubic
Fixes the deploy gate failure introduced by the v2.0.42 source bump: the bump raised catalogVersion from 4 to 5, but the deploy's catalog-verification step pins it at 4 as the schema version. Reverts catalogVersion back to 4 in the catalog data and the verify script, while keeping the software-factory source pinned to v2.0.42. The per-flow version bump and source sha carry the v2.0.42 update, so npm run verify:recommended-flows passes both gates.
Agent Relay sessions
claudesession76506089· opened viagh pr create· last active 2026-10-06