[goloroden]

Closes #66.

What changed

• Every diagnostic carries the URL of its entry on the Linter Rules pages. The human format prints it as a dimmed see line at the end of each block; the JSON format adds documentationUrl.
• Meta.DocumentationURL() derives the address from the rule's metadata: the site, the Linter Rules page of the rule's extension (or the core page), and the anchor #<category>-<name> the pages already use. Nothing is stored per rule, so the URL cannot drift away from the page.
• The runner's rule reporter stamps the URL alongside RuleID and Severity. The diagnostics of parser, resolver, and runner carry only an ID; the pipeline fills in their URL before returning, and a Meta built from a bare ID resolves to the core page, where those entries live.
• A documentation test turns every URL back into a page path and checks that the page exists, so a moved or renamed page fails the build before a user follows a dead link.
• The CLI reference and the lint guide describe the see line and the JSON field; the guide's example output shows the new line.
• Side finding, fixed here: the documentation claimed the JSON output is "one object per line". The formatter writes a pretty-printed array, and both passages now say so.

Why

A finding named a rule ID but offered no way to the explanation. With the Linter Rules pages from #53 in place, the linter can point at the exact entry, from the terminal and from tooling that consumes the JSON output.

Verification

make qa is green, mkdocs build --strict is clean. Running the linter on a broken model shows the see line in the human format and documentationUrl in the JSON output. The links resolve once the pages are published with the next release.

🤖 Generated with Claude Code

https://claude.ai/code/session_014C8sbpnyEX9WQ3C3BP1KQ2