Development record
stale deep links: 04-surfaces README and 01-agents.md point to the intent reviewer as 05-intent.md section 6, but that section now appears later.
issueresolvednitpickiss-14
stale deep links: 04-surfaces README and 01-agents.md point to the intent reviewer as 05-intent.md section 6, but that section now appears later.
Frontmatter
| id | iss-14 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | nitpick |
.abcd/work/issues/resolved/iss-14-stale-intent-section-deeplinks.md
open on GitHub ↗ · commit history ↗
mentions2
- iss-303links_resolve (internal/core/lint/lint.go checkLinks) strips the #fragment before resolving and skips same-file # links, so no gate validates heading anchors even though both record-lint and docs-lint declare the rule blocking and the Makefile advertises it as catching a broken relative link; ~18 broken anchors sit on a green tree. Proposed: extend the rule to slug the target file's ATX headings and validate the fragment, landing warn-first
- iss-320brief and intent record cross-references carry dangling section anchors including five that misdirect a reader to the wrong section