Prove workspace-bound continuation crash convergence - #29
Closed
zhiiw wants to merge 19 commits into
Closed
Conversation
zhiiw
force-pushed
the
codex/m3-managed-continuation-admission-v1
branch
from
August 24, 2026 03:44
05db740 to
83d91db
Compare
zhiiw
force-pushed
the
codex/m3-managed-continuation-crash-v1
branch
2 times, most recently
from
August 24, 2026 04:02
ff1052b to
0c43680
Compare
zhiiw
force-pushed
the
codex/m3-managed-continuation-admission-v1
branch
from
August 24, 2026 04:15
0dd3fbb to
2bea7de
Compare
zhiiw
force-pushed
the
codex/m3-managed-continuation-crash-v1
branch
from
August 24, 2026 04:15
0c43680 to
95e184a
Compare
zhiiw
force-pushed
the
codex/m3-managed-continuation-admission-v1
branch
from
August 24, 2026 05:46
2bea7de to
b2e6f0a
Compare
zhiiw
force-pushed
the
codex/m3-managed-continuation-crash-v1
branch
from
August 24, 2026 05:49
95e184a to
83f3d3e
Compare
zhiiw
force-pushed
the
codex/m3-managed-continuation-admission-v1
branch
from
August 24, 2026 06:33
b2e6f0a to
51e4252
Compare
zhiiw
force-pushed
the
codex/m3-managed-continuation-crash-v1
branch
2 times, most recently
from
August 24, 2026 06:47
9874078 to
1f9faca
Compare
zhiiw
force-pushed
the
codex/m3-managed-continuation-admission-v1
branch
from
August 24, 2026 07:41
51e4252 to
524459b
Compare
zhiiw
force-pushed
the
codex/m3-managed-continuation-crash-v1
branch
from
August 24, 2026 07:41
1f9faca to
db5a9d4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the production-shaped crash proof for workspace-bound managed continuations and closes four durable seams exposed by that proof.
A real Runtime Host now starts a
ContinuationClaimV2against a real Gitoxide accepted head, is killed immediately after the durable continuation start, and is reopened against the same storage root and helper. Recovery closes the local Run asfailed/app_restartedbut keeps provider state parked ascontinuation_started_indeterminate; a new Turn retry does not invoke the provider.Primary invariant
After a workspace-bound continuation start is durable, Host restart may only converge from the same v2 claim and exact accepted Gitoxide head. A local restart closure is not evidence that the provider never received the request. Recovery must not replay the provider and must not fall back to the v1 continuation authority.
commitWorkspaceBoundContinuationStart()transactionChanges
replayManifestDigestwhile retaining the legacy descriptor shape.runtime_admission + app_restartedprovider state indeterminate; claim-repair and real terminal outcomes retain their existing classification.Verification
32682738656: Linux, macOS, and Windows all pass the real Runtime Host crash/restart proof.Stack
Depends on #28. This remains a stacked Draft and does not enable Desktop/CLI automatic continuation.
中文说明
摘要
本 PR 为 workspace-bound managed continuation 增加 production-shaped crash proof,并关闭该测试暴露出的四处 durable seam。
真实 Runtime Host 会针对真实 Gitoxide accepted head 提交
ContinuationClaimV2,在 durable continuation start 后立即被杀死,再使用同一个 storage root 和 helper 重启。Host 会把本地 Run 关闭为failed/app_restarted,但这不能证明 provider 未收到请求,因此恢复仍停在continuation_started_indeterminate;使用新的 Turn identity 重试也不会调用 provider。主要不变量
workspace-bound continuation start 一旦持久化,Host 重启只能基于同一条 v2 claim 和同一个 accepted Gitoxide head 收敛;禁止重放 provider,也禁止回退 v1 continuation authority。
commitWorkspaceBoundContinuationStart()transaction三平台真实 crash gate 已通过:Linux、macOS、Windows 均验证 Host kill/reopen、exact Gitoxide head、
app_restarted本地关闭、continuation_started_indeterminateprovider 状态以及零次 provider replay。本 PR 仍是依赖 #28 的 stacked Draft,不会开启 Desktop/CLI 自动续跑。