📖 [Docs]: Specification anchors now pass Markdown linting

[Marius Storhaug (MariusStorhaug)]

Specification requirement anchors now use a form understood by both Python-Markdown and markdownlint, so requirements copied from the template keep their in-page links valid in repositories where MD051 runs.

Fixed: Requirement links reported as broken

Functional and non-functional requirement identifiers now use unspaced anchors. Authors can copy the specification template and link to individual requirements without their Markdown linter reporting valid references as broken.

---

Technical details

• Requirement-anchor guidance, the specification template, and the 25 existing capability-specification anchors now use {#id}; the link validator's help now demonstrates the same form.
• MD051 is re-enabled after the repository-wide anchor sweep, so future broken in-page links are again caught by markdownlint.
• Implementation plan progress — completed every documentation and verification step in Use unspaced requirement anchors in the specification template #141.

Changed surface	Standards checked	Framework docs checked	Result
src/docs/Ways-of-Working/Spec-Driven-Development.md	Markdown	Spec-Driven Development	Fixed in this PR
src/docs/Capabilities/**/spec.md	Markdown	Python-Markdown attr_list	Fixed in this PR
.github/scripts/Test-DocumentationLink.ps1	PowerShell	None (no framework-specific docs)	Aligned
.github/linters/.markdown-lint.yml	markdownlint MD051	None (no framework-specific docs)	Fixed in this PR

• Issue convergence sweep — reviewed every repository occurrence of the spaced anchor form. Use unspaced requirement anchors in the specification template #141 is the only delivery issue fully satisfied by this PR.

Relevant issues (or links)

• FixesUse unspaced requirement anchors in the specification template #141

[Marius Storhaug (MariusStorhaug)]

Superseded by #144, which delivered this change with the accompanying Markdown standard update.