forked from mosaicstack/stack
mos-dt-0andClaude Opus 5
e85a088f85
ci-postgres reports FAIL under an overall-success pipeline on #2170 and #2175 while all eight functional steps pass. Most likely a service-pod teardown artifact; the test step's pg_isready fail-fast guard passed, so the database was available during the run. Low severity, but the pattern matters: a red that is routinely present and routinely correct to ignore trains operators and agents to discount reds, and the discounting generalises. Six instances of a meaningless green are already banked; a meaningless FAIL is the same erosion with the sign flipped. Recorded rather than normalised — the first time it is waved through without a note is when it becomes background noise. RM-55: treat a non-terminal-success sub-step under an overall-success pipeline as a reportable anomaly, and make the CI contract state which steps may fail without failing the pipeline. An implicit allowance is indistinguishable from a bug. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>