[ThorFuchs]

The documentation landing page still describes 1.7.0 as unreleased and 1.6.1 as stable after publication. Read GitHub's latest published stable release once per existing Native documentation build, retain that exact JSON snapshot, and derive the release/source/available DocC links from it. The website remains static; libraries gain no network behavior.

The version-neutral heading continues to describe main's qualified references. Source version metadata reads the existing CLI version authority, independently of the observed release. CI requires valid observed metadata and fails on fetch/validation errors; an unconfigured local preview stays offline with a neutral link. Snapshot hashes and normalized release identity are recorded in the Pages receipt/build-info, while the raw response stays in CI evidence. No tags or frozen release assets change.

Validation at 428582e:

• 22 site/release-metadata regressions, preserving all 12 original guide/index cases; includes future-version substitution, draft/prerelease rejection, malformed/foreign/ambiguous assets, bounded fetch, replay and failure behavior.
• 26 qualification-harness cases; public privacy/inventory checks (1,508 files, 49 metrics, three profiles); unchanged CLI source identity; diff and workflow YAML checks.
• Actual read-only GitHub fetch selected published 1.7.0 and its uploaded DocC asset.
• Existing Playwright 1.62.1 / installed Chrome 156 preview at 1440×1000 and 390×844: meaningful content, correct release links, actual GitHub release navigation and return, no horizontal overflow or preview console/page errors.
• Full affected docs and required Native/Linux checks run on this PR; no hosted outcome is preclaimed.

Only five documentation/workflow files change. Parallel PR #71 / 1.8 worktrees remain untouched. Existing strict check names, read-only build permissions and the separately gated Pages deployment are preserved. Metadata refresh happens whenever the existing documentation lane runs; this does not add a release-publication trigger or client-side polling.

[ThorFuchs]

The owner explicitly authorized approval, protected merge and live Pages deployment in the repository session. GitHub rejects author self-approval (422); this comment records the review and owner decision without representing a separate approval. The active main ruleset requires zero approving reviews and retains strict Native / native, Native / safety and Native / docs checks, resolved threads and no bypass.

Reviewed exact head 428582e, tree 28769dbf5e6364f67d8b29d7cb3e4eb336d10d25, against unchanged main cbd3a81. The five-file change uses one retained read-only release snapshot, bounded fetch/input, no token redirects, no stale CI fallback and an explicit offline preview. Source/release identity and existing check permissions/names remain separate and intact. All eight source-bound Native/Linux matrix checks passed; review threads are empty. Local 22 site/metadata tests, 26 harness tests and desktop/mobile release-link previews passed. No library, tag/release asset or parallel 1.8 worktree change. Merge via ordinary protected squash with an exact-head lease, then verify the resulting source and actual Pages deployment.