T-LDH4-surface-failing-baseline-at-pickup

Status: closed/superseded · Impact: medium · Complexity: small

Goal

The baseline-capture step (/sdlc:task-work Step 3a) records a failing suite but doesn’t flag it prominently at pickup, so an implementer can spend time mid-task discovering that a suite was already red on origin/main. task-work should loudly surface “baseline contains a failing suite” at Step 3a — so a pre-existing failure is known up front and isn’t mistaken for damage the current change caused, shortening the discovery loop.

A pre-existing divergent duplicate of TextMatchSpec (declared in both text-match.ts and the text-constraints.ts stub) was breaking npm run build and the cli/index.test.ts suite on origin/main; it surfaced only mid-implementation and was fixed here by single-sourcing the type. The baseline-capture step recorded the failing suite but it was not flagged prominently at pickup — surfacing “baseline contains a failing suite” loudly at Step 3a would shorten the discovery loop.

— from T-TXAP-text-predicate-builders post-mortem (https://github.com/sksizer/markdown-contract)