chore(release): fill v0.62's step-8 attestation with the measured result (0-line diff)

[avrabe]

Two pre-tag obligations for v0.62.0, batched so #1158's 64-job CI was not restarted for prose.

1. Step-8 attestation — measured, not asserted

loop_conformance_check labels PR-head-vs-merge ATTESTED in both pretag and retro mode — squash-merge head refs are not durably fetchable at audit time — and directs the result into the step-7 review record. So filling it is a deliberate act, and it is now filled with the real measurement:

PR head  59441a80d40853346a6cea0030fbe05de9394510
merged   569ca7559da38b1d2c421e7c3f7c451a06b60ba3
git diff <PR head> <merged>  =  0 LINES

What CI verified, what the independent cold review audited, and what the v0.62.0 tag will name are byte-for-byte the same tree.

Recorded beside it: the four merge-ritual checks as they actually stood (9/9 required contexts green by name from branch protection; baseRefOid == origin/main at 5e6bc4400297; zero non-advisory reds across 64 checks — 63 pass, 1 skipped; status_evidence_check exit 0, 2 delivery-shaped commits — 2 attributed) and the CONFORMS verdict that preceded the merge.

An attestation with nothing behind it is precisely the vacuity this release spent its scope finding — a floor 1,892 short of its declaration, a rule blind to an unattributed commit, a sentence nobody checked. Shipping those findings while leaving this slot empty would have been incoherent.

2. A number that goes stale at tag time

Caught on a final read-through. The notes said "the release commit itself adds a further +213/−51" — true when 0a8c1e1f was the only release commit, wrong once there were four, wrong again after this one.

The fix is not a fresher figure but no figure: state the scope (feature merges vs release-assembly commits) and drop a number that keeps moving until the instant of tagging. Same treatment as the 17-hour figure and the v0.59 subcounts — attributed or scoped, never asserted.

Gates: claim_check 58/58 · status_evidence_check exit 0.

Refs #1136, #1158

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!