T-A7MY-ensure-ready-flags-stale-language-touchpoint

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

Goal

A task’s ## Files to touch and ## Today tables cite paths the implementer is supposed to create or modify, but nothing checks whether a cited path’s file extension matches the language the surrounding tree actually uses. When a spec authored before a language migration names a .py path in a tree that has since gone fully TypeScript (or vice versa), the readiness gate passes — the new-kind row has no existence check — and the implementer silently re-derives the right extension mid-flight. A lightweight ensure-ready / task-review signal that flags a Files-to-touch or Today path whose extension is anomalous for its directory would catch the stale-citation case at authoring time instead of at pickup.

From T-SPBO-commit-helper-routes-through-tempfile’s post-mortem: “Spec named the helper as plugin/scripts/sdlc_commit.py, but the project is fully TypeScript (plugin/scripts/ has 23 .ts, zero .py; D0006/M0002 en-masse port). Implemented as sdlc_commit.ts to match the substrate. The spec’s Files-to-touch row went stale against the language migration — task-review / ensure-ready could flag a .py Files-to-touch path in a TS-only plugin/scripts/ tree as a likely-stale citation.”