docs: record the verified hydrated release

[jm9e]

The composition plan still called0.6.0 the released baseline after hydrated wires shipped. It now distinguishes that earlier realization from the current bitruntime0.7.1 / bitwire0.6.0 cohort and records the actual release commit, checksum, fresh package consumer and independent15-case composition replay. The partial0.7.0 release remains accurately described.

Documentation only. Local Markdown targets, project naming and staged diff checks passed; the maintained CI gates run unchanged.

[jm9e]

Independent review accepts PR46 at exact head 1912f2c. No findings.

Reviewed the complete two-file documentation diff. The v0.7.1 annotated tag resolves to 583174d; release run37691354522 passed, including the fresh public Go module smoke; the public tarball metadata reports SHA256 78e0ce694162cecc5b6f0ff503df91631dadb12ea97915af2848fd1637db5f0d. Receipt6047570121 records the separate actual-download checksum and installed package smoke. Receipt6047513997 accurately describes my independent 15/15 composition replay against the actual public tarball and public bitwire0.6.0; its local result.json confirms both installed versions and passing exit codes. Library implementation paths have no diff between v0.7.0 and v0.7.1. The failed v0.7.0 release remains accurately distinguished from its published Go tag, and the text does not claim delivered bitnode deployment.

All 10 local Markdown links/anchors in the changed documents resolve at the exact reviewed commit; naming and git diff --check pass. Documentation-only scope needs no additional invented runtime tests. Acceptance remains subject to the repository's unchanged required CI before integration; Communications retains integration ownership.