Correct stale documentation and enforce link integrity #77

Problem

Published documentation contains stale repository references, source paths, development commands, version-qualified provider status, and duplicate legacy pages that conflict with the current package and workflows. The release documentation verifier checks identity metadata but not all README and documentation links, deployed navigation, assets, and fragments required by the ecosystem documentation standard.

Acceptance criteria

• Published setup, testing, architecture, provider-extension, and update guidance use canonical paths, uv, current APIs, and actual CI/test lanes.
• Duplicate legacy pages with obsolete commands and release claims are removed or consolidated into maintained guides.
• Version-qualified provider status matches the 0.2.0 release evidence.
• Every README link and rendered documentation content link is checked by CI.
• Rendered and deployed validation detects broken navigation, assets, internal links, and fragments.
• Focused tests demonstrate that broken links fail and valid documentation passes.
• Ruff, ty, tests, strict MkDocs, package build, actionlint, pre-commit, and ecosystem qualification pass.