T-KS7C-ensure-ready-enumerates-peer-test-twin

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

Goal

This repo’s task-spec template and implementation-ready readiness gate (/sdlc:task-ensure-ready / the implementation-ready contract) let a behavior-changing acceptance criterion list only one of the several files that pin the same contract under ## Files to touch. Closing this gap means prompting the spec author to enumerate the co-located peer-test twin (<module>.test.ts) alongside any fixture a behavior-changing AC touches, in repos whose convention pins the same contract in both a fixture and a co-located unit test. The need surfaced during implementation of T-5LHY-docrule-receives-projected-tree on git@github.com:sksizer/markdown-contract.git, described there as:

A behavior-changing AC often changes more than one file that pins the same contract, but ## Files to touch lists only the obvious one. In the originating task the integration fixture tests/fixtures/validation/23-text-forbids-body-root was listed, but its co-located peer-test twin src/core/text-constraints.test.ts — which pins the same whole-document forbids position — was not, so the unit test had to be re-pinned (toBe(2) -> toBe(3)) mid-implementation. Proposed fix: the task spec template / readiness gate (/sdlc:task-ensure-ready or the implementation-ready contract) should prompt the spec author to enumerate the co-located peer-test twin (<module>.test.ts) alongside any fixture a behavior-changing AC touches, in repos whose convention pins the same contract in both a fixture and a co-located unit test. Related to but distinct from sksizer/dev PR #512 / task T-KY0Y, which covers the gated-fixture variant of this same Files-to-touch under-enumeration theme — the receiver may wish to consolidate the two.