T-O66A-gap-report-honors-kind-new

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

Goal

The paths claim resolver (and gap-report) that back the task readiness gate false-positive a “moved” finding when a genuinely-new file’s basename collides with exactly one existing file, forcing citation reshapes and renames purely to green the gate. This task teaches the resolver kind: new awareness so genuinely-new files aren’t reported as relocations. Surfaced by T-DAEM-daemon-and-json-api in git@github.com:sksizer/markdown-contract.git.

The paths claim resolver and gap-report false-positive a ‘moved’ finding when a genuinely-new file’s basename collides with exactly one existing file — e.g. every new moon project’s moon.yml (vs packages/core/moon.yml), or a new api.ts (vs prototype/web-ui/types/api.ts). It has no kind: new awareness and never cross-references the ## Files to touch ‘new’ column. Fix: gap-report/the paths resolver should suppress a same-basename ‘moved’ finding when the cited path is declared kind: new in ## Files to touch. — from T-DAEM-daemon-and-json-api