test(runtime-host): prove managed lifecycle response loss - #79
Draft
zhiiw wants to merge 1 commit into
Draft
Conversation
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.
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
Boundaries covered
refs/maka/published/<id>compare-and-swap.refs/heads/maka/<id>deterministic commit + compare-and-swap without modifying the source checkout.Failure and rollback
Verification
中文说明
本切片为 M4 的交付/恢复动作补齐统一的真实进程“动作已持久化、响应丢失、重新打开并精确重试”证据:
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 并运行该测试。