relative links under .abcd/work/ are checked by no lint root

relative links under .abcd/work/ are checked by no lint root

links_resolve is a blocker, but blockers only fire inside a configured root:

• record-lint roots: .abcd/development
• docs-lint roots: docs, README.md

.abcd/work/ is in neither, so no relative link in the working tier is ever resolved. That covers the issue ledger, the reviews charter, DECISIONS.md, and CONTEXT.md.

Confirmed incidence, not theory: the first draft of iss-2608221457227162 used ../../development/... for two ADR links. From .abcd/work/issues/open/ the correct depth is three levels, so both were dead on arrival. make record-lint and abcd docs lint both exited 0. The links were fixed by hand after a manual check.

The partial coverage is what makes this easy to miss: issue_id_unique and issue_impact_valid are configured with explicit .abcd/work/issues paths, so the ledger visibly is linted, just not for links.

Grounds

• pursued: a dead relative link anywhere in .abcd/work outside reviews/ fails record-lint; one that passes would show it wrong