test(flows): expect the Software Garden v2.0.42 catalog entry
Change
#142/#143 bumped Software Garden in web/data/recommended-flow-catalog.v1.json to v2.0.42 (entry version 4, ref 3c58ee1) but left recommended-flow-catalog.test.ts pinned to v2.0.26, so main CI has failed since. This updates the Software Garden expectations only; Babysitter correctly stays on 8b33eba.
Validation
- The source sha256
4339c0c4…was verified against the raw file at3c58ee1. recommended-flow-catalog.test.ts5/5; full web suite 374/374 tests (theprerender-cache-keyfile fails only locally, on a module missing from a sharednode_modules).
Unblocks CI on open PRs, e.g. #145. Not changed: lib/flow-plugin-catalog.ts:89 and content/docs/relayflows/recommended.mdx:37 still link the Software Garden source at 8b33eba.
🤖 Generated with Claude Code
[!NOTE]
Low Risk
Test-only expectation updates to match existing catalog data; no production logic changes.
Overview
Aligns recommended-flow-catalog.test.ts with the Software Garden catalog bump already in recommended-flow-catalog.v1.json (entry version 4, release v2.0.42, ref 3c58ee1, updated URLs and sha256). The HTTP detail assertion for software-factory now expects the same ref.
Babysitter extension expectations are unchanged (still pinned to 8b33eba). This fixes CI failures from tests still asserting v2.0.26 metadata; no runtime catalog or API behavior changes in this PR.
Reviewed by Cursor Bugbot for commit aea10c483b65ef820186c4dc5c58b03ff2b81d57. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by cubic
Updates the recommended flow catalog test to expect the Software Garden v2.0.42 entry, fixing the CI failure on main caused by the catalog bump leaving the test pinned to v2.0.26.
- Expects entry version 4 with ref
3c58ee1and the verified source sha2564339c0c4…for Software Garden. - Babysitter expectations are untouched and stay pinned to
8b33eba.
Agent Relay sessions
claudesession1e2adfbe· opened viagh pr create· last active 2026-10-07