docs(e2): record container fault acceptance and consolidate current state

[mirror29]

Changes

Record two fault-injection checks using the built Evolver business image: recovery reuses saved responses after a container exit, while unconfirmed responses retain unknown-cost reserves and prevent redispatch across two restarts. Preserve partial setup failures and distinguish local HTTP/provider fixtures and AMD64 emulation from production evidence.

Consolidate the current-state page around current conclusions, evidence levels, and remaining work. Preserve the previous complete page in a linked historical archive, including non-E2 backlog items.

Validation

• Same-image recovery: five generations, 120 fallback implementations, ten offline provider calls, research rejection for insufficient FDR evidence.
• Unknown response: two offline calls; reserve retained; no redispatch across two restarts.
• Consistency: 19 passed, 0 failed, 12 existing warnings; local documentation links and diff whitespace checks passed.
• Independent evidence and documentation review: no confirmed new P1/P2 findings.

These are full Evolver container checks with fixture peripheral services, not normal-owner production acceptance or strategy improvement. Real E2 input coverage and long-term Forward/holdout acceptance remain incomplete. No production model calls were added. Documentation changes do not require a deployment.

[github-actions]

Reviewed PR head: 7e03007b8e9e

🤖 DeepSeek Code Review

Docs-only PR that consolidates docs/04-current-state.md into current conclusions + an evidence-tier table, moves the prior verbose state into a new frozen history archive (docs/validation/current-state-history-through-2026-10-14.md), and adds two Evolver same-image isolation receipts (known-response recovery, unknown-response blocking).

Critical	Major	Medium
0	0	0

Findings

No medium-or-higher issues found in the supplied diff.

Review scope and limitations

Reviewed the supplied diff and project rules. No tests were executed by this reviewer.

• Diff only adds two JSON receipts; existence of the many other referenced validation/*.json link targets could not be verified from the supplied diff.
• Relative-link depth in the new archive (../../ for repo-root, ../ for docs/) appears correct on inspection, but no tooling was available to confirm link targets or the scripts/check-consistency.sh rules.
• Numeric claims in 04-current-state.md were cross-checked against the two new receipts and the archive and are consistent; assertions about earlier receipts/PRs (e.g. fix(evolver): preserve campaign usage identity and verify response recovery #242, e2-campaign-identity-release) rely on pre-existing files not shown in this diff.

[cloudflare-workers-and-pages]

Deploying inalpha-web with    Cloudflare Pages

Latest commit:	7e03007
Status:	✅  Deploy successful!
Preview URL:	https://e2bb6c14.inalpha-web.pages.dev
Branch Preview URL:	https://codex-e2-identity-runtime-an.inalpha-web.pages.dev

View logs

[mirror29]

Both findings have been addressed in 7e03007.

1. The frozen archive now demotes the copied page heading, labels its date as historical, removes the copied sole-priority-list claim, and explicitly directs all current updates to docs/04-current-state.md. It includes the evidence bullets committed immediately before consolidation; it is a snapshot of that stage, not the pre-evidence file.
2. The original probe counted all response checkpoint rows, so adding a pre-crash non-null count retrospectively would invent an observation. The receipt now explicitly defines that count, marks the non-null count as not directly sampled before SIGKILL, and describes the indirect recovery evidence and its limits. Original sampled fields remain unchanged.

No production model calls or service replacement were performed for these documentation corrections.