T-XYKD-readiness-gate-accept-basename-path-match

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

Goal

The implementation-ready gate resolves every path-shaped citation in a task’s prose against the live codebase and disqualifies the task when a citation doesn’t resolve. Today it demands an exact repo-root-relative path, so a bare, unambiguous basename in Goal prose (e.g. declarative/text.ts where only packages/core/src/declarative/text.ts exists) trips the gate and parks an otherwise implementation-ready task. This task softens the SDLC plugin’s path claim-resolver so a citation that uniquely matches one file by basename is accepted (or, alternatively, requires the task template to demand repo-root-relative paths), so trivial relative citations no longer gate readiness. Originating from T-D8TE-ratchet-biome-complexity-ceiling in https://github.com/sksizer/markdown-contract.

Originating post-mortem: the readiness gate flagged a Goal-prose bare declarative/text.ts citation as a path disqualifier because only the full packages/core/src/… path exists on disk, nearly parking an otherwise implementation-ready task on a one-token relative-path citation. The path claim-resolver could accept a unique-basename match (or the task template could require repo-root-relative paths) so trivial relative citations do not gate readiness.