Skip to content

Admit managed continuations against exact Gitoxide heads - #28

Closed
zhiiw wants to merge 5 commits into
codex/m3-workspace-bound-continuation-v1from
codex/m3-managed-continuation-admission-v1
Closed

zhiiw wants to merge 5 commits into
codex/m3-workspace-bound-continuation-v1from
codex/m3-managed-continuation-admission-v1

Conversation

@zhiiw

@zhiiw zhiiw commented Aug 23, 2026

Copy link
Copy Markdown
Owner

Summary

Admit managed-workspace continuations only from a Host-observed, owner-issued accepted Gitoxide head and commit the matching v2 claim/start path without v1 fallback.

Primary invariant

For managed-coding-v1, provider execution may start only when the planned immutable replay cursor and the currently accepted workspace boundary still match the same ContinuationClaimV2.

Scope

  • Host observation of the existing accepted Gitoxide ref (no baseline creation)
  • planner/execution revalidation of the exact workspace boundary
  • v2 claim/start and continuation_source_v3
  • v3 lineage authentication
  • claim-only startup repair through the same v2 authority
  • real-process rollback coverage for a killed workspace-bound start transaction

Verification

  • Core and Storage builds pass
  • Runtime Host build passes
  • SQLite focused suite: 51/51
  • Runtime continuation suite: 21/21
  • SQLite real-process crash suite: 16/16

The local full Runtime/Host suites are currently blocked by the worktree's mismatched https-proxy-agent/Slack dependency installation; no changed-file TypeScript errors were reported. The matching Gitoxide helper is built by the stacked CI source, so this remains Draft until the three-platform Host kill/reopen lane is present.

中文说明

本切片只证明 managed continuation 的生产 admission:Host 从已有 accepted Gitoxide ref 和 SQLite head 重新签发 workspace boundary;planner、执行前重验、v2 claim/start、v3 lineage 与 claim-only startup repair 都消费同一身份。缺少 v2 authority、head 漂移或 ref 不一致时一律 fail closed,不回退 v1。

已通过 Core/Storage/Runtime Host 构建、SQLite 51/51、Runtime continuation 21/21、真实 SQLite crash 16/16。当前本地完整 Runtime/Host 套件受工作树依赖安装中的 https-proxy-agent/Slack 版本错配阻断;stack 对应的 Gitoxide helper 由 CI 构建。因此在三平台 Host kill/reopen lane 补齐前继续保持 Draft。

@zhiiw
zhiiw force-pushed the codex/m3-workspace-bound-continuation-v1 branch from 914339c to 3009d57 Compare August 24, 2026 03:38
@zhiiw
zhiiw force-pushed the codex/m3-managed-continuation-admission-v1 branch from 05db740 to 83d91db Compare August 24, 2026 03:44
@zhiiw
zhiiw force-pushed the codex/m3-workspace-bound-continuation-v1 branch from 1489233 to 035e180 Compare August 24, 2026 04:15
@zhiiw
zhiiw force-pushed the codex/m3-managed-continuation-admission-v1 branch from 0dd3fbb to 2bea7de Compare August 24, 2026 04:15
@zhiiw
zhiiw force-pushed the codex/m3-workspace-bound-continuation-v1 branch from 035e180 to 0824588 Compare August 24, 2026 05:41
@zhiiw
zhiiw force-pushed the codex/m3-managed-continuation-admission-v1 branch from 2bea7de to b2e6f0a Compare August 24, 2026 05:46
@zhiiw
zhiiw force-pushed the codex/m3-workspace-bound-continuation-v1 branch from 0824588 to ed4dd80 Compare August 24, 2026 06:33
@zhiiw
zhiiw force-pushed the codex/m3-managed-continuation-admission-v1 branch from b2e6f0a to 51e4252 Compare August 24, 2026 06:33
@zhiiw
zhiiw force-pushed the codex/m3-workspace-bound-continuation-v1 branch from ed4dd80 to 0688fc2 Compare August 24, 2026 07:41
@zhiiw
zhiiw force-pushed the codex/m3-managed-continuation-admission-v1 branch from 51e4252 to 524459b Compare August 24, 2026 07:41
@zhiiw

zhiiw commented Aug 30, 2026

Copy link
Copy Markdown
Owner Author

Closed as an obsolete extraction/integration slice. The current delivery path is the merged Gitoxide foundation followed by #40 -> #41 -> #42. This PR remains available as design and implementation history.

中文说明

该 PR 属于旧 extraction/integration 栈,现已失去独立合并价值。当前交付路径是已合并的 Gitoxide 基础,然后依次审查 #40#41#42。这里继续保留设计、实现与审查历史。

@zhiiw zhiiw closed this Aug 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant