Setup's marker detection reports an absent conventions file as a resolvable marker.missing gap even when the folder it would be created in cannot take a new file: with the repository root at mode 0555 and no AGENTS.md, detectMarkerDrift raises marker.missing (required, resolvable), install promises to plant the block and its write refuses on every run (permission denied creating the lock or the temporary file beside it), so the gap never closes and each run repeats the promise. The defect is on main: detectMarkerDrift there classifies an absent file as missing without asking whether its folder can take one.

Setup's marker detection reports an absent conventions file as a resolvable marker.missing gap even when the folder it would be created in cannot take a new file: with the repository root at mode 0555 and no AGENTS.md, detectMarkerDrift raises marker.missing (required, resolvable), install promises to plant the block and its write refuses on every run (permission denied creating the lock or the temporary file beside it), so the gap never closes and each run repeats the promise. The defect is on main: detectMarkerDrift there classifies an absent file as missing without asking whether its folder can take one.

Grounds

• pursued: an absent or outdated conventions file in a folder abcd cannot create files in raises a non-resolvable gap and install leaves no marker gap outstanding; a resolvable marker gap for such a folder, or a run that still reports marker.missing in Remaining, would show it wrong