T-PXZ0-baseline-refresh-on-config-verb-change

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

Goal

/sdlc:task-work Step 3a snapshots a quality baseline (the set of pre-existing findings to subtract) against the project’s sdlc.yaml verb list at that moment. When the verb list changes on origin/main mid-run, Step 7 diffs the current gate output against a baseline built from a different verb set and mis-reports findings from the newly-added verb as new-drift:. This task closes that gap in the SDLC plugin’s task-work skill so the baseline stays consistent with the config it was captured against. Originating from T-D8TE-ratchet-biome-complexity-ceiling in https://github.com/sksizer/markdown-contract.

Originating post-mortem: /sdlc:task-work Step 3a captured the quality baseline against a 5-verb sdlc.yaml, but a parallel session added a 6th verb (bun run lint:deps) to sdlc.yaml on origin/main mid-run; the stale baseline had no lint:deps findings to subtract, so Step 7 reported 7 false new-drift lines until the baseline was re-captured at the branch base with the current config. task-work Step 7 should refresh or invalidate the Step 3a baseline when the config’s verb list changed since capture, rather than diffing against a baseline built from a different verb set.