You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(ios): restore two-phase stabilization and the rebased plan-state switch
Takeover of #1573 on top of #1587.
- The rebase onto main merged textually but not semantically: #1587 turned the
plan-state -> pre-seeded first-failure mapping into an exhaustive switch, and
this branch's new `.preferredIndependentBackend` case was never added to it.
Counterfactual: without the added case the runner does not compile
("switch must be exhaustive", RunnerTests+SnapshotCapturePlan.swift:159).
- That switch and `countsAsRecovery` were two independent encodings of the same
question — did this plan state degrade the capture. They had to agree, or the
runner could stamp a `recovered` verdict with no reason to render. Dropped
`countsAsRecovery` and derived the recovered flag from the single mapping, so
a future state cannot satisfy one and not the other.
- Reapplied b113f17's reviewed two-phase stabilization refactor, which the
earlier rebase silently dropped (412 -> 377 LOC, no flag-driven orchestration).
Behavior is unchanged; the two budgets are modeled as the two sequential
phases they actually are.
- Documented the freshness-probe reorder on `effectiveSnapshotCapturePlan`, and
replaced the normal-path comment that contradicted the change under it: the
available-tier filter is not a fallback-attribution change for its own sake,
it stops the all-tiers-failed stamp from naming a simulator-only backend on a
physical device.
0 commit comments