fix(conformance): isolate post-tap settling from app launch - #2390
Merged
Merged
Conversation
Size Report
Startup median (7 runs, lower is better):
|
Member
Author
|
The visual wait at f80dc2c separates launch stabilization from the measured tap without weakening the settle invariants, and the regression exercises the checked-in flow. No code findings. Exact-head iOS differential and smoke runs are now green; ready for human review. |
thymikee
added
the
ready-for-human
|
thymikee
added a commit
that referenced
this pull request
Sep 8, 2026
…cope-contracts * origin/main: (25 commits) fix(ios): avoid duplicate alert routing queries (#2398) docs(adr): record the #2278 coupling audit and re-trace entry-to-platform hops (#2355) chore(gates): classify #2278 daemon-platform-runtime edges and ratchet handler session authority (#2354) test(capture): shrink the 3x crop fixture to avoid coverage timeouts (#2399) perf(ios): settle the first interaction on a deadline, not a fixed sleep (#2395) feat: support standalone Maestro clearState command (#2366) refactor(capture-kit): complete ADR 0019 end state — relocate snapshot and recording zones (#2385) refactor(ios): delete the unused snapshot plan interface (#2392) fix(conformance): isolate post-tap settling from app launch (#2390) test(remote): assert the proxied snapshot's whole wire conversation (#2387) fix(daemon): stop an attested tenant from downgrading its own isolation (#2386) refactor(ios): prune converged snapshot paths (#2383) refactor(move): move the batch runner and batch policy into @agent-device/command-registry (#2388) fix(remote): let a plain-session client read its own failure record (#2382) refactor(move): move replay divergence vocabulary into @agent-device/ad-replay (#2384) refactor(cli): take the CLI's vocabulary off runtime barrels (#2379) perf(cli): keep scroll vocabulary off gesture runtime (#2378) chore: drop the stale planned-operations closure approval (#2373) fix(gates): stop an eager-closure approval from turning main red on merge (#2375) fix(ios): honor the startup budget through a cold Simulator boot (#2325) ...
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.
Summary
Fix the
settle-after-tapscenario from failed run 34086351141. Both engines passed every flow, but the Settings tap recorded one settle latch and one timeout: per-command metrics also include the deferred launch boundary.Add an explicit visual wait before the measured tap so launch stabilization cannot contaminate its inline-settle counters. Keep the zero-timeout and proof-of-life invariants unchanged. Three files changed: the flow, its semantic guard, and a runtime regression executing that checked-in flow with slow startup snapshots.
Validation
Tested commit:
f80dc2c3e1.pnpm check:affected --run: all runnable checks passed, including typecheck, lint, layering, build, packaging, and Node integration.