Development record
a roots entry pointing at a non-existent directory makes docs-lint / record-lint pass with zero findings, silently disarming every per-file blocker rule for that tree; the shipped scaffold's roots default triggers it in any adopter whose docs live elsewhere. GitHub mirror: #360
issueresolvedmajoriss-2608270500208736
a roots entry pointing at a non-existent directory makes docs-lint / record-lint pass with zero findings, silently disarming every per-file blocker rule for that tree; the shipped scaffold's roots default triggers it in any adopter whose docs live elsewhere. GitHub mirror: #360
Frontmatter
| id | iss-2608270500208736 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | major |
.abcd/work/issues/resolved/iss-2608270500208736-a-roots-entry-pointing-at-a-non-existent.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610040758095861ahoy install seeds .abcd/docs-lint.json with roots ["docs", "README.md"] whatever the repository holds, so in a repository with no docs/ folder the documentation check it has just armed cannot run: abcd lint docs exits 2 with 'roots entry "docs" does not exist', and neither the install receipt nor bare abcd ahoy says the seeded check is broken. Reproduced at 57d5ec9fa in a scratch repository holding only a README.md, after an install given --scan-deep false. A downstream lab reported the check as silently disarmed; at tip the lint fails loudly on a missing root (since iss-2608270500208736, which already named this seed as the trigger), so the defect is the seed its fix left in place, not a silent pass.