[8.10] Readiness record — `evidence complete` declared, `release approved` tracked

[rootwarp]

Plan reference: plan/glamsterdam-2026-09-05/issues/08-phase-8-network-soak-and-observability.md · Issue 8.10

Description

Record the readiness evidence after the soak: the tag, the commit SHA 8.9b passed, the per-layer KAT results, the soak window and snapshot set — and declare evidence complete, the phase's exit state. release approved is out of this issue's reach (D16).

Implementation Notes

• docs/gloas-observability.md: one readiness section citing 8.9b's Decision Log entry and 8.8's snapshots; every fact is a reference, nothing is re-derived here.
• Record release approved separately as blocked, accountable role UNASSIGNED, decision owner (project sponsor) named as needed (Q1). Do not invent a name, do not self-approve, and never let the recorded gap read as approval.
• If 8.8 restarted on a rebuild, the record names the final SHA only and links the superseded run.

Acceptance Criteria

• docs/gloas-observability.md declares evidence complete with tag, SHA, per-layer KAT results, soak window and snapshot set — all referencing 8.9b / 8.8 artifacts on that SHA.
• The same record shows release approved as blocked, role UNASSIGNED, decision owner = project sponsor (Q1); satisfied by recording the blocked state, never by approval (D16).
• docs_freshness green; no path is invented.

Testing Notes

documentation only.

Points: 1 · Type: chore · Priority: P0 · Scope: 0.5 day · Blocked by: #339 · Blocks: —