T-KY0Y-enumerate-activated-gated-fixtures

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

Goal

When a task flips an IMPLEMENTED[...] (or any feature-gate) flag that activates previously-gated fixtures or tests asserting placeholder / illustrative values, the readiness gate or the task spec template should require those fixture files be enumerated as modify rows in ## Files to touch. Today an implementer can be blind-sided: the activated fixtures must be edited (e.g. to tighten placeholder ids to the real synthesized output) for the acceptance criteria to pass, yet nothing in the spec points at them.

The task’s ## Files to touch table omitted the four gated fixture files (tests/fixtures/validation/text/22..25-*.ts), yet AC-7 cannot pass without updating their expected finding ids (the harness asserts id exactly and the builders emit synthesized per-entry ids) — the implementer had to discover this from the fixtures’ own comments. When a task flips an IMPLEMENTED[...] flag that activates gated fixtures asserting illustrative/placeholder ids, the readiness gate or the spec template should require those fixtures be enumerated as modify rows.

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