test(e2e): isolate iOS acceptance on a fresh host (experiment concluded) - #103
Closed
leon-zym wants to merge 6 commits into
Closed
test(e2e): isolate iOS acceptance on a fresh host (experiment concluded)#103leon-zym wants to merge 6 commits into
leon-zym wants to merge 6 commits into
Conversation
leon-zym
changed the title
Owner
Author
|
实验结论已写入 PR 描述：fresh-host 隔离未达到采纳门槛，因此此 PR 保持 Draft 且不得合并。可独立合入的探针、失败身份与文本断言修复已提取到 agent/issue-101-e2e-failure-identity，并通过 |
This was referenced Aug 16, 2026
Owner
Author
Closing without mergeThis experiment has concluded and did not meet its adoption threshold. It is closed without merge.
|
leon-zym
added a commit
that referenced
this pull request
Aug 16, 2026
## What changed This PR extracts the independently valid fixes discovered while evaluating #101 / #103: - distinguish bounded Maestro and CocoaPods cold-start timeouts from a missing executable; - preserve the original command timeout as the primary E2E failure when process finalization also fails; - require the text editor panel to close after confirmation, preventing an input-field false positive in the E2E flow; - give a redaction-only orchestration test appropriate scheduling headroom. ## Why The fresh-host experiment in #103 is not being adopted, but these corrections improve the truthfulness and diagnosability of the existing E2E runner without changing its execution plane. ## Scope boundary - No sealed-package or cross-host orchestration from #103. - No production acceptance retry, device rebuild, fixed sleep, or broad timeout expansion. - No change to the current L4 gate policy; #104 owns that future decision. ## Validation ```text pnpm verify - scenario verification: 104 Scenarios, 165 bindings - orchestration: 198 passed, 1 platform skip - app: 412 passed - render: 85 passed ``` Related to #101 and #104.
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
1 participant
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.
Related to #101.
结论
本 PR 检验“把 iOS acceptance 放到全新宿主，能否稳定消除托管环境长尾”的假设。有效配对样本没有达到采纳门槛：
这不是对产品代码的归因，也不应靠 retry、sleep 或放宽生产 acceptance deadline 来掩盖。不要继续扩样或自动补跑；ADR 0042 继续有效。
已独立提取的可合入修复
不依赖本实验的修复已推送到 agent/issue-101-e2e-failure-identity：
与 main 的完整比较 已通过
pnpm verify。后续决策
要提升 iOS L4 的真实稳定性，需要选择更可靠的执行面，例如专用/更大规格 runner 或设备云。若暂时不能提供该执行面，完整 iOS L4 应作为定时或手动证据，而不是不稳定的 PR 硬门禁。