docs+ui: extend verify-this-review with the attested-run verification path

[JSONbored]

Problem

apps/loopover-ui/content/docs/verify-this-review.mdx (route /docs/verify-this-review, #8231) documents the reproducibility posture and currently — correctly, today — names the trusted-execution boundary an explicit non-goal (line 96: the runtime itself is "an attestation problem — a trusted-execution boundary, not a replay"). Once the attested runner (blocked-by) persists real envelopes, that passage becomes stale and the walkthrough gains a second verification path that must be documented with the same "anyone can check this" rigor as the replay path.

Requirements

• Update the non-goal passage: replay remains the universal path; attestation is the additional path for runs that carry an envelope.
• New walkthrough section: given a persisted run's AttestationEnvelope, how a skeptic verifies it — recompute reportData from the published corpus checksum + SHAs via buildAttestationReportData, check it against the attestation report's user-data binding, and verify the report against AMD's certificate chain (link the standard tooling; do not vendor it).
• Surface attestation status wherever backtest verdicts already render publicly (the public-rule-precision consumers / fairness page links) — a run shows unverified / verified / failed when an envelope is present, and renders exactly as today when absent.
• No overclaiming: the docs must state plainly what attestation does NOT prove (data provenance of the human-override history — Research: is TEE hardware attestation necessary, or does a reproducible-backtest checksum approach cover the real threat? #8136's T3), mirroring the honesty discipline of the existing page.

Deliverables

• verify-this-review.mdx updated (non-goal passage + attested-run section, both paths walkable end to end)
• Attestation status rendered on the public verdict surfaces, absent-envelope rendering unchanged (tested)
• Docs-page checklist honored (nav entries + pinned tests per the established docs-page pattern)

Links & Resources

• Parent epic; attested-runner sub-issue (blocked-by); docs+ui: 'verify this review' — public reproducibility walkthrough + measured-accuracy display #8231 (the walkthrough this extends), Research: is TEE hardware attestation necessary, or does a reproducible-backtest checksum approach cover the real threat? #8136 (T3 honesty requirement)
• apps/loopover-ui/content/docs/verify-this-review.mdx, src/review/public-rule-precision.ts

Boundaries

Docs + read-only rendering only. No scoring, gating, or persistence changes; no claims the envelope contents can't back.

maintainer-only — public accuracy-claims surface.

[linear-code]

JSO-5907