Skip to content

test(runtime-host): prove managed lifecycle response loss - #79

Draft
zhiiw wants to merge 1 commit into
codex/m5-managed-profile-negotiation-v1from
codex/m4-lifecycle-crash-convergence-v1
Draft

test(runtime-host): prove managed lifecycle response loss#79
zhiiw wants to merge 1 commit into
codex/m5-managed-profile-negotiation-v1from
codex/m4-lifecycle-crash-convergence-v1

Conversation

@zhiiw

@zhiiw zhiiw commented Aug 31, 2026

Copy link
Copy Markdown
Owner

Outcome

The M4 lifecycle now has one real-process response-loss matrix for immutable Publish, source-branch Publish, and isolated Restore. Existing crash tests already cover Undo-as-successor, Rebaseline activation, and restore-orphan maintenance.

Primary invariant

Once an M4 lifecycle action reaches its durable publication point, losing the owner process before its response cannot create a second result or replay an accepted mutation. The same operation identity must adopt the exact durable evidence.

Boundaries covered

  • refs/maka/published/<id> compare-and-swap.
  • refs/heads/maka/<id> deterministic commit + compare-and-swap without modifying the source checkout.
  • Restore destination publication and exact accepted-tree reconstruction.
  • Existing SQLite successor, active-epoch, and GC tombstone crash points.

Failure and rollback

  • Before publication: exact retry; at most unreachable content-addressed objects or staging artifacts remain.
  • After publication / response loss: exact evidence is adopted.
  • Conflicting ref or identity: fail closed.
  • Restore residue is rotated to an orphan instead of being overwritten.
  • Windows open-handle deletion failure retains a retryable tombstone.

Verification

  • Runtime Host TypeScript build passes.
  • The new test compiles and is selected by the existing three-platform real-helper workflow.
  • Local real-helper execution is blocked because this shell lacks the MSVC linker and the only cached helper implements an older managed-tree policy; CI builds the exact helper source before running the suite.
中文说明

本切片为 M4 的交付/恢复动作补齐统一的真实进程“动作已持久化、响应丢失、重新打开并精确重试”证据:

  • immutable accepted-ref Publish;
  • source-branch Publish;
  • isolated Restore。

Undo-as-successor、Rebaseline 和 restore-orphan maintenance 已有各自的 child-process crash test。所有动作都绑定稳定 ID;响应丢失后只能采用同一 ref/receipt/successor/epoch/tombstone,不会重跑 Write/Edit,也不会覆盖用户 checkout。

本机缺少 MSVC link.exe,缓存 helper 又是旧 policy,因此本地只能完成 TypeScript 构建和测试选择验证;现有三平台 Gitoxide workflow 会从当前源码构建真实 helper 并运行该测试。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant