Update final candidate status

ROADMAP.md

@@ -9,10 +9,10 @@ Grain Timers, State failure recovery, bounded Reminder delivery, the Silo
 Activation admission limit, and bounded resource tests are complete for 0.1.0.
 Portable benchmark probes are also complete. The fail-closed local release
 gate and fuzz checks are also complete. The external restart proof and public
-document cleanup are complete. The exact tagged-module command is ready. A
-release-gate follow-up invalidated the earlier candidate proof. The hosted
-supported-system run, final same-commit candidate proof, and successful
-tagged-module proof remain open. Action recovery
+document cleanup are complete. The exact tagged-module command is ready. The
+fixed fuzz-budget candidate passes `make ci`, `make external`, and the hosted
+supported-system run. The final same-commit candidate proof is complete. The
+successful tagged-module proof remains open. Action recovery
 confirms Grain State before it commits an Application
 receipt. Pending actions recover in save order. An Invalid Reminder now gets
 one Terminal Result. Direct lifecycle proof for a mutable State alias and a
@@ -190,14 +190,14 @@ The implementation batches are:
    Invalid Reminder one Terminal Result. A fifth follow-up proves the direct
    State failure lifecycle. A sixth follow-up migrates the exact `v0.0.5`
    schema and proves the external upgrade path. A seventh follow-up gives
-   each fuzz target a fixed iteration budget. The hosted platform run, final
-   same-commit candidate proof, and successful tagged-module run are open for
-   the new candidate.
+   each fuzz target a fixed iteration budget. The hosted platform run and final
+   same-commit candidate proof are complete. The successful tagged-module run
+   remains open.
 
 The exact scope and proof for each batch are in
 [design/release-0.1.0.md](design/release-0.1.0.md). Batches 1 through 7 and
-Batch 8a through 8d are complete. Batch 8e candidate and exact tagged-module
-proofs remain open.
+Batch 8a through 8d are complete. Batch 8e candidate proof is complete; its
+exact tagged-module proof remains open.
 
 ## Cluster preview
 

design/release-0.1.0.md

@@ -484,9 +484,8 @@ Proof:
 
 #### Batch 8e: Final candidate proof
 
-**Status: In progress.** A release-gate change invalidated the earlier final
-candidate proof. The new final `master` candidate commands, hosted platform
-jobs, and exact tagged-module proof remain pending.
+**Status: In progress.** The final `master` candidate commands and hosted
+platform jobs are complete. The exact tagged-module proof remains pending.
 
 Before the final proof, complete the release audit for the upgrade from
 `v0.0.5`. That version stores Reminder identity in the `entity_type` and
@@ -579,15 +578,15 @@ Batch 7 hardens generation and moves implementation code under `internal/`.
 Batch 8a adds Activation admission. Batch 8b adds bounded resource proof and
 portable benchmark probes. Batch 8c implements fail-closed local release
 checks, fixed tools, fuzz checks, and the hosted platform workflow. The hosted
-workflow passed before the fixed fuzz-budget follow-up. Batch 8d implements the
+workflow has passed on the fixed fuzz-budget candidate. Batch 8d implements the
 external restart proof and public document cleanup. A release audit follow-up
 passes dynamic Reminder names to typed methods. A second follow-up prevents a
 caller-provided Make variable from replacing the internal test command. A
 third follow-up restores Grain State before it commits an Application receipt.
 An Invalid Reminder now gets one Terminal Result. A fifth follow-up proves
 the mutable State alias and Reminder-turn State failure lifecycle. Batch 8e's
-candidate commands, hosted proof, final same-commit proof, and exact
-tagged-module proof are pending for the new candidate. A sixth release audit
-follow-up migrates the exact `v0.0.5` Reminder schema and adds the external
-upgrade proof. A seventh follow-up gives every fuzz target a fixed iteration
-budget above the earlier successful work count.
+candidate commands, hosted proof, and final same-commit proof are complete. Its
+exact tagged-module proof remains pending. A sixth release audit follow-up
+migrates the exact `v0.0.5` Reminder schema and adds the external upgrade proof.
+A seventh follow-up gives every fuzz target a fixed iteration budget above the
+earlier successful work count.

design/release.md

@@ -90,10 +90,9 @@ The 0.0.x release-note question has a zero-maintenance answer: none is written.
 The earlier functional readiness work is complete. It includes public API
 comments, Runtime shutdown, errors, lifecycle, the example, observability, and
 benchmarks. The 0.1.0 contract adds composition and release evidence gates.
-Public document cleanup is complete. A fixed fuzz-budget follow-up invalidated
-the earlier candidate proof. Hosted jobs, the final same-commit candidate
-proof, and the final tagged-module proof remain open. See
-[ROADMAP.md](../ROADMAP.md).
+Public document cleanup, hosted jobs, and the final same-commit candidate proof
+are complete for the fixed fuzz-budget candidate. The final tagged-module proof
+remains open. See [ROADMAP.md](../ROADMAP.md).
 
 Cluster support remains a preview. A partition can misjudge healthy Silos.
 

design/testing.md

@@ -178,8 +178,8 @@ It also checks generated files and module tidy state without changing them.
 The release command contract test prevents a caller-provided Make variable
 from replacing the internal test command.
 
-The CI workflow has jobs for Linux amd64, macOS arm64, and Windows amd64. The
-hosted jobs have not run on this change. `make external` passes locally on
-Linux with empty Go caches and separate restart processes. Hosted external
-proof and the final same-commit proof remain open. Batch 8 in
-[release-0.1.0.md](release-0.1.0.md) owns these gaps.
+The CI workflow has passed for Linux amd64, macOS arm64, and Windows amd64 on
+the fixed fuzz-budget candidate. `make external` also passes on the exact
+candidate with empty Go caches and separate restart processes. The final
+same-commit candidate proof is complete. The exact tagged-module proof remains
+open. Batch 8 in [release-0.1.0.md](release-0.1.0.md) owns this gap.

docs/compatibility.md

@@ -82,5 +82,6 @@ If this v1 promise must ever be broken, gor will release a new major version wit
 ## Gap
 
 The pre-announcement checklist is complete. The 0.1.0 composition, failure,
-platform, and release evidence gates remain open. The v0 rules start with the
-first announced release.
+platform, and final candidate evidence gates are complete. The exact
+tagged-module proof and release boundary remain open. The v0 rules start with
+the first announced release.

docs/release-0.1.0.md

@@ -308,7 +308,7 @@ internal test command. Action recovery confirms requested State before it
 commits the Application receipt. The clean external-module restart proof
 passes locally on Linux. The exact `v0.0.5` migration and external upgrade
 proof also pass locally on Linux. An Invalid Reminder now gets one Terminal
-Result. Public document cleanup is complete. A fixed fuzz-budget follow-up
-invalidated the earlier candidate proof. Hosted supported-system proof, the
-final same-commit candidate proof, and the exact tagged-module run remain open.
-ROADMAP.md tracks the batches.
+Result. Public document cleanup is complete. Hosted supported-system proof and
+the final same-commit candidate proof are complete for the fixed fuzz-budget
+candidate. The exact tagged-module run remains open. ROADMAP.md tracks the
+batches.

research/release-0.1.0-issue-118-fuzz-budget.md

@@ -81,5 +81,24 @@ correction:
 - `make external` passed with exit 0 in 34.81 seconds with a cold test cache,
   including 20 external tests and the exact `v0.0.5` upgrade.
 
-The mutation was restored. Exact-commit local proof and hosted proof remain
-pending.
+The mutation was restored. Exact-commit proof then passed:
+
+- candidate commit `ffbf26e2e94ac82d702bcf2995671073d9caa119` passed
+  `make external` in 213.97 seconds and `make ci` in 116.30 seconds with cold
+  test caches;
+- hosted pull request workflow
+  [31503688931](https://github.com/suraciii/gor/actions/runs/31503688931)
+  passed Go 1.25.12, Go 1.26.5 with no known vulnerabilities, macOS, Windows,
+  and aggregate CI;
+- squash commit `0c41f9f644905183d7d4fd8f7efed24e4396bf0d` passed
+  `make external` in 34.15 seconds and `make ci` in 73.37 seconds with cold test
+  caches in a clean detached worktree;
+- hosted `master` workflow
+  [31504300130](https://github.com/suraciii/gor/actions/runs/31504300130)
+  passed Go 1.25.12, Go 1.26.5 with no known vulnerabilities, macOS, Windows,
+  and aggregate CI;
+- both hosted Linux jobs completed 1,600,000, 225,000, and 2,250,000
+  executions; and
+- final independent review found no P0, P1, or P2 issue.
+
+The exact `v0.1.0` tagged-module proof remains part of the release boundary.