Summary
bash scripts/verify-release.sh can legitimately run longer than a 20-minute wrapper on the current local development host. During the Track B close-out on 2026-05-25, a 20-minute wrapper timeout made the baseline look red even though the full script later completed successfully with VERIFY-RELEASE: PASSED.
Evidence
- Short wrapper timed out during backend pytest / runtime proof investigation.
- Full longer run passed on
master HEAD 4b3572b.
- Local evidence log:
C:\Users\scott\OneDrive\Desktop\Claude\_tmp_track_b\civicrecords-verify-master-long-20260525.log
Requested fix
Add one or both:
- a startup banner naming expected runtime / operator timeout guidance; and/or
- sub-script chunking so long phases emit clearer progress and can be run independently.
This is not blocking Track B. It is backlog hygiene so future operators do not repeat the same 20-minute wrapper-timeout investigation.
Summary
bash scripts/verify-release.shcan legitimately run longer than a 20-minute wrapper on the current local development host. During the Track B close-out on 2026-05-25, a 20-minute wrapper timeout made the baseline look red even though the full script later completed successfully withVERIFY-RELEASE: PASSED.Evidence
masterHEAD4b3572b.C:\Users\scott\OneDrive\Desktop\Claude\_tmp_track_b\civicrecords-verify-master-long-20260525.logRequested fix
Add one or both:
This is not blocking Track B. It is backlog hygiene so future operators do not repeat the same 20-minute wrapper-timeout investigation.