docs(v1): remove stale Alpha-era current-facing guidance

SUPPORT.md

@@ -1,6 +1,6 @@
 # Support
 
-ExecSurface is currently a **public alpha** for Linux x86_64.
+ExecSurface `v1.0.0` is the current **stable release** for the documented Linux x86_64 + native `ptrace` support boundary.
 
 ## Before opening an issue
 
@@ -55,6 +55,6 @@ For a security vulnerability, follow [SECURITY.md](SECURITY.md) and use private
 
 ## Support expectations
 
-There is no public-alpha SLA.
+There is no fixed calendar maintenance period or response-time SLA.
 
 A PASS verdict is not a safety certification, and support discussions will not reinterpret incomplete evidence as PASS.

docs/MARKETPLACE_LISTING_COPY.md

@@ -24,7 +24,7 @@ ExecSurface learns an accepted runtime execution surface for a command and later
 
 It is designed for software repositories, CI pipelines, dependency updates, developer tools, and AI tooling where source review alone does not show every runtime effect.
 
-The public alpha supports Linux x86_64 and uses the native ptrace observer as its correctness-reference backend.
+Stable `v1.0.0` supports Linux x86_64 and uses the native `ptrace` observer as its correctness-reference backend.
 
 Typical workflow:
 

docs/QUICKSTART_5_MIN.md

@@ -2,7 +2,7 @@
 
 This path is designed to prove the product workflow without requiring a real project or changing system security settings.
 
-Support: **Linux x86_64 public alpha**.
+Support: **Stable `v1.0.0` — Linux x86_64**.
 
 ## 1. Install
 

docs/SELF_SERVICE_START.md

@@ -2,7 +2,7 @@
 
 No signup, meeting, API key, or AETHER X approval is required.
 
-Public Alpha support: **Linux x86_64**.
+Stable `v1.0.0` support: **Linux x86_64**.
 
 ## Install — recommended path (no Rust required)
 

docs/SUPPORT_POLICY.md

@@ -1,13 +1,13 @@
 # ExecSurface Stable Support and Deprecation Policy
 
 Status: **V1 STABLE OPERATING POLICY — ACTIVE**  
-Applies when a stable `v1.x` line is published.
+Applies to the published stable `v1.x` line.
 
-This policy defines the operational lifecycle for the bounded stable surface. It does not claim that v1.0 is already released.
+This policy defines the operational lifecycle for the bounded stable surface. ExecSurface `v1.0.0` is the current published stable release.
 
 ## Supported stable line
 
-After v1.0 exists:
+For the published stable line:
 
 - exact releases such as `v1.0.0`, `v1.0.1` and later `v1.x.y` are immutable release identities;
 - `AETHERXGLOBAL/execsurface@v1` is the moving stable GitHub Action channel;

docs/TECHNICAL_EVALUATION.md

@@ -4,13 +4,13 @@
 
 **Current public release:** `v1.0.0`
 
-**Current boundary:** Linux x86_64 Public Alpha. Native `ptrace` is the public default/reference observer. This evaluation is not a malware test, sandbox, EDR assessment, enforcement-system test, or proof of program safety.
+**Current boundary:** stable `v1.0.0` on Linux x86_64. Native `ptrace` is the public default/reference observer. This evaluation is not a malware test, sandbox, EDR assessment, enforcement-system test, or proof of program safety.
 
 ## What this evaluation demonstrates
 
 The evaluator will:
 
-1. install the exact published alpha.4 binary and verify its checksum;
+1. install the exact published `v1.0.0` binary and verify its checksum;
 2. verify environment readiness;
 3. learn an explicit tiny baseline;
 4. re-run the same command and obtain `PASS`;
@@ -170,7 +170,7 @@ Inspect at least:
 
 ## 8. Current authority and limitation notes
 
-The public alpha.4 reference backend is native `ptrace`.
+The stable `v1.0.0` reference backend is native `ptrace`.
 
 Important boundaries:
 
@@ -189,7 +189,7 @@ See `docs/architecture/PTRACE_VS_LSM_ARCHITECTURE_REVIEW.md` and `docs/releases/
 
 A successful run supports only a bounded statement such as:
 
-> The evaluator installed the exact public ExecSurface alpha.4 release, learned an accepted runtime surface, reproduced an unchanged PASS, introduced controlled runtime drift, and obtained a machine-readable REVIEW under the declared policy in the recorded environment.
+> The evaluator installed the exact public ExecSurface `v1.0.0` release, learned an accepted runtime surface, reproduced an unchanged PASS, introduced controlled runtime drift, and obtained a machine-readable REVIEW under the declared policy in the recorded environment.
 
 It does **not** establish:
 

docs/TROUBLESHOOTING.md

@@ -16,7 +16,7 @@ The doctor is diagnostic only. It never changes privileges, ptrace sysctls or ho
 
 **Action**
 
-Use a Linux x86_64 environment. The public alpha does not claim macOS or Windows support.
+Use a Linux x86_64 environment. Stable `v1.0.0` does not claim macOS or Windows support.
 
 Do not treat a compatibility layer as an officially supported observer unless it has separate evidence.
 
@@ -28,7 +28,7 @@ Do not treat a compatibility layer as an officially supported observer unless it
 
 **Action**
 
-Use a Linux x86_64 runner/host. No arm64 release is claimed in the public alpha.
+Use a Linux x86_64 runner/host. No arm64 release is claimed in stable `v1.0.0`.
 
 ## ptrace restrictions
 
@@ -89,7 +89,7 @@ M6.5 changed execution-surface meaning by adding actual fd-attributed read/write
 
 v1 lockfiles are intentionally **not** reinterpreted as v2.
 
-Relearn with the current public alpha and review the new surface.
+Relearn with the current stable release and review the new surface.
 
 See [M6.5 Schema Migration](milestones/M6_5_SCHEMA_MIGRATION.md).
 
@@ -183,24 +183,24 @@ Do not run the binary.
 
 Delete the downloaded files and download the release again from the official repository.
 
-Verify the current public-alpha asset:
+Verify the current stable release asset:
 
 ```bash
-sha256sum -c execsurface-v0.1.0-alpha.3-x86_64-unknown-linux-gnu.tar.gz.sha256
+sha256sum -c execsurface-v1.0.0-x86_64-unknown-linux-gnu.tar.gz.sha256
 ```
 
 Optionally verify GitHub build provenance:
 
 ```bash
-gh attestation verify execsurface-v0.1.0-alpha.3-x86_64-unknown-linux-gnu.tar.gz \
+gh attestation verify execsurface-v1.0.0-x86_64-unknown-linux-gnu.tar.gz \
   -R AETHERXGLOBAL/execsurface
 ```
 
 An attestation proves provenance, not safety.
 
 ## GitHub Action cannot download the release
 
-The stable Action consumes the immutable public-alpha release asset.
+The stable Action consumes the immutable `v1.0.0` release asset.
 
 Check: