Complete CK-07R1 post-terminal roadmap dependency

AGENTS.md

@@ -33,8 +33,9 @@ corrective proof. CK-08R0 froze `corrective-gates-v1`; CK-08R2 is complete and
 CK-09 remains blocked. CK-08R1A froze corrected answer meaning and recursive
 closure; R1C is accepted at exact main `fb0c578`, and R1B is accepted at exact
 main `9e9332b3`. Final R1 requalification passed hosted CI in PR #439,
-squash-merged, and was exact-main verified at `0832b854`; no packet is Ready
-while CK-07R1 remains conditional.
+squash-merged, and was exact-main verified at `0832b854`. CK-07R1's separate
+post-terminal roadmap completion makes CK-08R4 the sole Ready packet while
+CK-08RG and CK-09 remain blocked.
 CK-QG1A removed the two R2 page-executor complexity findings without changing
 behavior or the frozen baseline and is accepted at exact main `30983d4`;
 QG1 PR #392 passed hosted CI, squash-merged, and was exact-main verified at
@@ -47,27 +48,19 @@ The versioned
 [`shared-successor-overlay-authority-v1`](docs/decisions/evidence/ck07r1a0/shared-successor-overlay-authority-v1.json)
 preserves accepted CK-08R1B, CK-08R1, and CK-QG1 bytes while admitting only
 that complete cohort as CK-07 `worker_prequalification`.
-The existing CK-07R1 worker remains stopped until that authority transition is
-merged and exact-main verified; no launch or token use is authorized. The
-candidate must construct and validate its exact overlay-bound receipt and
-non-null stdout/stderr/output evidence before the first durable `completed`
-finalization; any evidence read/hash/parse/validation/finalization failure is
-terminal `failed_after_launch`. Temporary parent SIGINT/SIGTERM handlers must
-route every wait interruption/error through bounded TERM/KILL/reap before
-terminal failure persistence and remain installed through evidence, receipt,
-and terminal ledger finalization; originals restore only after the terminal
-state attempt. Every terminal fallback persistence call masks SIGINT/SIGTERM
-with the existing ignore guard and restores the prior temporary handlers
-afterward; the outer final restoration of original handlers remains last. The
-fork child ignores SIGINT/SIGTERM while
-waiting for parent release and routes every pre-release failure to
-`os._exit(71)`; parent cleanup rejects nonpositive PIDs. Ledger updates use a
-unique same-directory `mkstemp`, close and unlink every failed or interrupted
-path, and persist durable consumed/no-retry `failed_after_launch` evidence
-without temporary residue. Its interpreter must be the lexical
-repository-worktree `.venv/bin/python` with matching lexical venv `sys.prefix`;
-base interpreters, resolved/symlink equivalence, wrong-worktree venvs, and prefix
-mismatch fail closed. PR #394 remains stale failed read-only.
+The sole CK-07R1 v2 launch is terminal `failed_after_launch`; its token is
+consumed and non-refundable, no planner-valid receipt or output exists, and no
+retry, restart, replacement, or further invocation is permitted. PR #448
+merged the exact deterministic planner-selected small/large correction and
+immutable v1/v2 terminal evidence at exact main `1d0466b1`. The additive
+[`lifecycle-post-terminal-completion-authority-v1`](docs/decisions/evidence/ck07r1a0/lifecycle-post-terminal-completion-authority-v1.json)
+accepts that merged deterministic evidence only for CK-07R1 roadmap dependency
+completion. It permanently records `runtime_acceptance=not_claimed`,
+planner-valid receipt absent, `post_single_run` unavailable, and
+`final_accepted` unavailable. It neither reclassifies the failed run nor
+changes production semantics. CK-08R4 must independently measure current
+merged publication behavior and must not claim the missing CK-07R1 runtime
+acceptance. PR #394 remains stale failed read-only.
 Retained R3 evidence proved the EvidenceService outer query
 physically unbounded; CK-08R3A owns that isolated fix and R3 awaits its
 accepted, merged, exact-main-verified result.

docs/INDEX.md

@@ -30,7 +30,8 @@ CK-08R1's schema-valid
 records 80/80 rows, grades, order, evidence, provenance, null semantics,
 closure, grading isolation, and mutation proof. PR #439 passed hosted CI,
 squash-merged, and was exact-main verified at `0832b854`; CK-08R1 is complete.
-CK-08R4 remains blocked on CK-07R1. Independent
+CK-08R4 is Ready through CK-07R1's post-terminal roadmap dependency
+completion. Independent
 truth now consumes [`answer-semantics.v1`](../config/agent-kernel/answer-semantics-v1.json);
 The linked [CK-08R3A schema/publication requalification authority](decisions/evidence/ck08r3a/schema-publication-requalification-authority.json)
 binds the resulting 57-index schema digest, synthetic publication fixture
@@ -224,7 +225,23 @@ missing, extra, partial, wrong-workflow, wrong-lineage, and wrong-candidate
 states fail closed. It adds no network install, qualification invocation,
 launch, refund, retry, receipt, runtime acceptance, or downstream authority.
 
-The V11 candidate must construct and validate the exact overlay/cohort-bound
+PR #448 subsequently passed hosted Console and Python 3.10/3.14, squash-merged
+the exact seven-path correction/evidence cohort, and was fresh exact-main
+verified at `1d0466b1b2992b48c5272dc4598606eeaea4dae2`. The additive
+[`lifecycle-post-terminal-completion-authority-v1`](decisions/evidence/ck07r1a0/lifecycle-post-terminal-completion-authority-v1.json)
+is the separate roadmap decision reserved by the terminal-failure authority.
+It accepts the merged deterministic small/large planner, publication,
+recovery, full/package, review, hosted, and exact-main evidence only as
+CK-07R1 dependency completion. The immutable v2 run remains
+`failed_after_launch`, the token remains consumed/non-refundable,
+`runtime_acceptance=not_claimed`, planner-valid receipt/output remain absent,
+and `post_single_run` and `final_accepted` remain unavailable. No command,
+artifact mutation, receipt fabrication, refund, retry, restart, replacement,
+or production-semantic change is authorized. After this authority transition
+is hosted-green, squash-merged, and fresh exact-main verified, CK-08R4 is the
+sole Ready successor; CK-08RG and CK-09 remain blocked.
+
+The historical V11 launcher contract required construction and validation of the exact overlay/cohort-bound
 receipt and non-null stdout/stderr/output evidence before its first durable
 `completed` finalization. Evidence read/hash/parse/validation/finalization
 failures are terminal `failed_after_launch`. Temporary parent SIGINT/SIGTERM
@@ -242,15 +259,15 @@ write/fsync/replace/post-replace paths and retain durable consumed/no-retry
 `failed_after_launch` evidence without temporary residue. Interpreter identity
 is the lexical repository-worktree `.venv/bin/python` plus the matching lexical venv
 `sys.prefix`; base interpreters, symlink/resolved equivalence, wrong-worktree
-venvs, and prefix mismatch are rejected.
+venvs, and prefix mismatch are rejected. That contract cannot authorize
+another invocation after the consumed terminal v2 run.
 
-The finite source/runtime state machine is currently `authority_main`: the live
-predecessor may remain on authority main, while only the exact selected
-successor may enter worker prequalification. `post_single_run` is unavailable
-without a complete planner-valid receipt bound to its exact dynamic receipt and
-evidence identity, and `final_accepted` additionally requires the worker PR to
-be squash-merged and exact-main verified. No state transition claims runtime
-qualification in this authority.
+The finite source/runtime state machine remains terminal at
+`failed_after_launch`: `post_single_run` is unavailable without a complete
+planner-valid receipt bound to its exact dynamic evidence identity, and
+`final_accepted` remains unavailable. The separate roadmap dependency state is
+`completed_post_terminal_deterministic_evidence`; it does not claim or imply
+runtime qualification.
 
 ## Authority set
 

docs/architecture/QUERY_EVIDENCE_PROJECTION_CONTRACTS.md

@@ -115,8 +115,11 @@ consumer is accepted at exact main
 [R1B join authority](../decisions/evidence/ck08r1b/answer-semantics-join-authority.json)
 bound the shared query/evidence/grading seams accepted through PR #430 and
 exact-main `9e9332b3`. Final R1 replayed both accepted consumers, passed hosted
-CI in PR #439, squash-merged, and was exact-main verified at `0832b854`; no
-packet is Ready while CK-07R1 remains conditional. Cursor serialization still
+CI in PR #439, squash-merged, and was exact-main verified at `0832b854`.
+CK-07R1's post-terminal deterministic-evidence roadmap completion makes
+CK-08R4 the sole Ready packet; CK-08R4 must preserve
+`runtime_acceptance=not_claimed` and independently measure current merged
+publication behavior. Cursor serialization still
 binds its version, request digest,
 plan, publication, and order; malformed, tampered, stale, replacement, and
 mismatched bindings fail closed.