docs(v1): synchronize published stable state

[aetherxeg-source]

Purpose

Synchronize current-facing repository documentation after the successful public v1.0.0 release transaction.

Public release facts already verified:

• stable GitHub Release v1.0.0 published;
• release workflow 37771109825 — SUCCESS;
• crates.io publication workflow 37771295572 — SUCCESS;
• stable v1 channel resolves to the same immutable source as v1.0.0;
• exact registry install cargo install execsurface --version "=1.0.0" --locked — PASS;
• release asset SHA-256 6892dc54e6f3f842cfecffa77ae0814c9e30aec219f2251c7c39a9f19f02ca7b.

Scope

Documentation/state synchronization only. No runtime, observer, baseline, policy, Action implementation, schema, or release-control code changes.

Current-facing docs are changed from Alpha.6/RC wording to stable v1.0.0. Historical Alpha.6 and Alpha.5 records remain unchanged.

P9 closeout is recorded as RELEASE_V1_0, while P9.1/P9.5 remain explicitly waived as release blockers / evidence incomplete, not falsely marked PASS.

Independent external validation is not claimed.

Project classification remains runtime behavioral verification / execution semantics / semantic-evidence correctness, not cybersecurity research.

Known external metadata cleanup

The published GitHub Release is correctly stable (prerelease=false) but its release-body source still contains the pre-publication status line PUBLICATION PENDING. The repository's current release record is corrected in this PR. The available GitHub connector does not expose release-body update mutation, so that external metadata line is retained as an explicit cleanup item rather than silently ignored.

[aetherxeg-source]

Post-release synchronization review completed on exact head 1a1af31ab536b4ff82d676ac525575860fd199d6.

Decision: V1_POST_RELEASE_SYNC_PASS_BOUNDED.

Verified:

• ExecSurface v1.0.0 is already published as a stable GitHub Release;
• immutable v1.0.0 and moving v1 resolve to release source e70169b959f2163715090c371335fa6c5591e3e4;
• release workflow 37771109825 succeeded end-to-end;
• crates.io publication workflow 37771295572 succeeded;
• all 12 required PR workflows are SUCCESS on this exact head;
• the prior RC1 failure was a shallow-checkout ancestry harness defect only; correction adds fetch-depth: 0 without weakening the ruleset/tag/source assertions;
• runtime semantics are unchanged;
• README/STATUS/support/evaluation metadata now describe the already-published stable v1 state;
• independent external validation is not claimed;
• project classification remains runtime behavioral verification / execution semantics / semantic-evidence correctness, not cybersecurity research.

This review authorizes merging the post-release synchronization PR. It does not modify the immutable v1.0.0 release source or tag.