Deployment-target performance matrix

• This fold measures product commit e5142fab8ff2d4b5c8ee767e244c495cec3ba8d3, the commit at which all four physical release-gate rows were captured between 2026-09-05 and 2026-09-07 (physical iPad web via issue 1686, physical iPad native and Android web via PR 1689, physical Android native in this fold). The three engine commits main took after e5142fab are not measured here: the strict staleness check reports every captured row STALE against main and current against e5142fab, so this is a coherent single-commit snapshot, not a measurement of current main.
• All four orientation/theme modes were freshly captured for physical iPad web, physical iPad native, physical Android web, and physical Android native. Every drawing, undo, and action section on those four release-gate rows comes from the campaign product commit.
• The physical Android native row is two sequential builds of the same clean commit: a probe-host server.url build carries the ADR-0135 split drawing and undo transport, and a bundled https://localhost build carries the Appium action sweep. Both embed e5142fab8ff2d4b5c8ee767e244c495cec3ba8d3; the split artifacts record pageIdentity unprovable by construction because the fixed server.url carries no per-cell nonce.
• Every physical drawing and undo cell passed its input-fidelity gate. The ten iPad web pen, Magic, and eraser lost-frame-share reds (1.02-1.37% against the 1% budget) are the issue-1693 budget decision; the remaining scoreable reds are three discrete actions tracked by issues 1694 and 1695. The physical Android native row carries no red cell.
• The physical iPad web row is the calibrated Safari approval target. ADR-0156 also requires the physical iPad native and both physical Android rows to be current and scored before campaign completion; every one is current here.
• Simulator, emulator, and Mac rows were not recaptured in this physical release-gate campaign. Every section on those rows is explicitly preserved from the prior published report and makes no claim of currency at the final product commit.
• Action cells are scored under ADR-0156: a post-action max breach counts only when two of the three scored repeats show it; a single breaching repeat is recorded as unconfirmed rather than red. Read each artifact's scoredActionFrameGaps rather than treating the pooled P95/P99/max triple as three repeats.
• Android physical web and native drawing use the ADR-0135 split input/measurement transport. Fresh artifacts record driving cadence, input fidelity, refresh regime, and page identity. Split-native captures also attest that art.splotch.app was the foreground package.
• The ADR-0143 60 Hz refresh-rate override keys were verified absent on the physical Android phone before and after its captures; every Android drawing artifact matched the declared 120 Hz regime.
• The campaign accepted every faithful red drawing or action gate and did not rerun a valid result to turn it green. Retries were reserved for transport, readiness, input-fidelity, and unchanged-canvas failures.
• Physical iPad capture needs a root-owned RemoteXPC tunnel before iOS 26 XCUITest discovery sees the device. See docs/PROFILING-IPAD.md.
• A landscape phone renders the compact Settings shell, which offers quick toggles and a pointer to portrait instead of the section list. Compare action modes against the same recorded settingsShell; a different label set between portrait and landscape is a shell difference, not a regression.
• Firefox is Gecko, which no Splotch deployment target ships; read it as the third desktop browser a parent might open splotch.art in, never as evidence about WebKit or Blink.
• Desktop captures used exact 1366×915 or 915×1366 CSS viewports at DPR 2 — iPad Pro 12.9 geometry, so the canvas area matches the physical-iPad rows. Playwright retains the requested page viewport regardless of the browser window size.
• Raw perf-profiles are local scratch and are mostly untracked. ADR-0138 keeps representative whole captures under perf-profiles/evidence/; every section not promoted from this campaign is marked preserved before the strict regeneration.
• 28 cells carry historical results preserved from data.json rather than re-read raw captures: The 2026-09-05 campaign freshly captured every physical release-gate section and preserves all advisory iPad Simulator, Android Emulator, and Mac desktop rows wholesale. No physical section is preserved. The 28 preserved advisory modes retain their original product commits and do not claim currency. Representative fresh physical evidence is promoted under perf-profiles/evidence/2026-09-05-epic-1567-final-control/. Preserved cells: iPad simulator · web · portrait-light (drawing, undo, actions); iPad simulator · web · portrait-dark (drawing, undo, actions); iPad simulator · web · landscape-light (drawing, undo, actions); iPad simulator · web · landscape-dark (drawing, undo, actions); iPad simulator · native · portrait-light (drawing, undo, actions); iPad simulator · native · portrait-dark (drawing, undo, actions); iPad simulator · native · landscape-light (drawing, undo, actions); iPad simulator · native · landscape-dark (drawing, undo, actions); Android emulator · web · portrait-light (drawing, undo, actions); Android emulator · web · portrait-dark (drawing, undo, actions); Android emulator · web · landscape-light (drawing, undo, actions); Android emulator · web · landscape-dark (drawing, undo, actions); Android emulator · native · portrait-light (drawing, undo, actions); Android emulator · native · portrait-dark (drawing, undo, actions); Android emulator · native · landscape-light (drawing, undo, actions); Android emulator · native · landscape-dark (drawing, undo, actions); Mac · Chrome · portrait-light (drawing, undo, actions); Mac · Chrome · portrait-dark (drawing, undo, actions); Mac · Chrome · landscape-light (drawing, undo, actions); Mac · Chrome · landscape-dark (drawing, undo, actions); Mac · Safari · portrait-light (drawing, undo, actions); Mac · Safari · portrait-dark (drawing, undo, actions); Mac · Safari · landscape-light (drawing, undo, actions); Mac · Safari · landscape-dark (drawing, undo, actions); Mac · Firefox · portrait-light (drawing, undo, actions); Mac · Firefox · portrait-dark (drawing, undo, actions); Mac · Firefox · landscape-light (drawing, undo, actions); Mac · Firefox · landscape-dark (drawing, undo, actions).

Gates. Drawing passes when blank-paper paint P95 ≤ 20 ms, P99 ≤ 33 ms, max ≤ 50 ms, and lost frame time stays under 1% of in-contact time. Undo passes at engine P95 ≤ 20 ms, next-frame P95 ≤ 33 ms, and next-frame max ≤ 50 ms. An action passes at first-frame P95 ≤ 33.5 ms, post-action frame P95 ≤ 20 ms, and post-action frame max ≤ 33.5 ms. A post-action max over its gate counts only when 2 of the three scored repeats show it (ADR-0156); one breaching repeat renders as a warning, not a failure. Ready P95 appears in tooltips but is not gated: its completion semantics differ per action, so a frame-gate pass says nothing about end-to-end response time.

Lost-frame budget exceptions (ADR-0137). Cells held to a different lost-frame budget, and why:

• Crayon on ipad-device-web — 1.5%. Crayon deposits wax through pattern-filled strokes that Safari prices per path-length, so the web build cannot merge them across pointermoves (the native WKWebView prices per op and merges per frame instead — ADR-0137 as amended), so it pays a per-move cost every other brush coalesces away, and mirror-by-blit already took it from 2.11%. Across all four orientation/theme modes its median is 1.11-1.17%, but a single capture of landscape-light measured 1.40% and re-measured to 1.17% over three samples. A matrix cell IS a single capture, so this is set above the observed single-sample excursion rather than above the median.
• Crayon on ipad-device-native — 1.5%. Per-frame crayon op merging (ADR-0137 as amended, issue 1236) brought the native WKWebView from a 2.14% published cell to Safari parity: three same-session samples on 2026-08-25 measured 0.96/1.11/1.44%, median 1.11% — inside the web cell's own 1.11-1.17% median band with the same shape of single-sample excursion. The same residual per-move wax cost now binds both runtimes, so the same 1.5% single-capture budget applies, set by the same above-the-excursion rule.

Action allowances on ipad-device-web (ADR-0090, ADR-0160). Actions held to a measured allowance instead of the base post-action gates, and why; every target without a ledger scores them at the base gates:

• open Settings — post-action P95 ≤ 29 ms. Worst committed P95 28 ms (perf-profiles/evidence/2026-09-05-epic-1567-advanced-controls-certification, landscape/dark at ebc7673b), 27 ms in six further September 2026 captures across three modes at 3c017796, 9af487b3 and e5142fab, 20-26 ms in eleven more. The pane is prewarmed (ADR-0049 amendment) and its open still carries the showModal flip and the heaviest section reveal; Instruments aligns the remaining slow frames with animation completion, compositing-hierarchy changes, layer removal and paint, and the bounded `contain: layout paint` candidate measured negative. Raised from the 26 ms of ADR-0090 under ADR-0160.
• close Settings — post-action P95 ≤ 22 ms. Worst committed P95 21 ms in three captures (perf-profiles/evidence/2026-09-05-epic-1567-ipad-e514-control landscape/light and landscape/dark; 2026-09-05-epic-1567-ipad-paper-control portrait/light), 17-20 ms in fifteen others. The same dialog retirement over a full-screen paper layer as the coloring picker; it carries no dedicated trace, so ADR-0160 records the attribution as shared and the reopen condition as its own.
• select coloring page — post-action P95 ≤ 30 ms. Worst committed P95 29 ms (perf-profiles/evidence/2026-09-05-epic-1567-landscape-retirement-controls, landscape/dark at e5142fab), 26-28 ms in eight further captures, portrait/light green at 17. The 29 ms frame sampled in Instruments is GPU-process IOSurface pool eviction, surface creation and Metal submission with no app evaluation in-frame; seven bounded product mechanisms measured negative or insufficient (issue 1569, 2026-09-06 disposition).
• switch light theme to dark — post-action P95 ≤ 23 ms. Worst committed P95 22 ms (perf-profiles/evidence/2026-09-05-epic-1567-ipad-e514-control, portrait/light), 17 ms in fifteen other captures. A single-capture excursion sized by ADR-0137 worst-single-capture rule: the full-document restyle recomposites every layer in one frame (ADR-0087).
• with ink: PORTRAIT to LANDSCAPE rotation — post-action P95 ≤ 26 ms. Worst committed P95 25 ms in two captures (perf-profiles/evidence/2026-09-05-epic-1567-ipad-paper-control, portrait/light at 141288da), 22-24 ms in four others; the landscape-origin direction reads 17-18. The slow frame is the first full post-resize interval of the OS rotation; the aligned trace holds GPU surface-pool eviction and command submission beside WebContent layout, and paper-sheet compositor pre-promotion measured negative. Supersedes ADR-0156 decision 5 for this direction only; the 33.5 ms max gate stays.
• open Settings — post-action max ≤ 56 ms. Capture-environment allowance (issue 1130, ADR-0090 2026-08-26 amendment): every hitch under the 44-55 ms open-Settings frame lands on the automation overlay stack with zero WebContent hitches, but the trace attributes per layer and the real-finger control was confounded by the persistent AutomationModeUI overlay. Covers the observed three-beat frame plus jitter; a clean-device control that still shows the frame retires it.

Action allowances on android-device-web (ADR-0162). Actions held to a measured allowance instead of the base post-action gates, and why; every target without a ledger scores them at the base gates:

• disable Night Mode in the compact shell — post-action P95 ≤ 33.5 ms. Worst committed P95 33.4 ms (perf-profiles/evidence/2026-09-06-issue-1696-android-night-toggle, landscape/dark full-plan control at f42d0994, two beats in all three scored repeats), 33.3 ms in the e5142fab row capture (perf-profiles/evidence/2026-09-06-epic-1567-android-device-web-e514, landscape/dark) and once in landscape/light (perf-profiles/evidence/2026-09-05-epic-1567-night-mode-control-trace at a9438fc7); 16.7-17.1 ms in ten other captures of the same cell. The paired Chrome trace (issue 1696) puts the click's input task at 26-39 ms on CrRendererMain in every repeat — 9-12 ms of dispatch and a 9.5-14.7 ms whole-document style recalc for the theme token flip that the bounded closed-dialog treatment (PR 1702) did not move — with a DroppedFrame at the first BeginFrame after every click. One 0.1 ms clock quantum above the worst reading and equal to the max gate, so a P95 past it needs three over-gate gaps: spread across repeats the max gate confirms them, concentrated in one repeat this allowance alone fails them.

Release roles (ADR-0156). Release gate · physical iPad and Android: These rows gate a release: a scoreable red cell needs a recorded product outcome, and a cell an uncalibrated instrument cannot score counts as red here, not as absent. Regression tripwire · Mac: A Mac cell that turns red on a change that was green on main is a finding to attribute before shipping; a cell that was already red is not a remainder. Advisory · simulators and emulators: These rows narrow or reject a hypothesis but never fail or approve a release; their red stays visible so a systemic regression still shows. A row’s role follows the hardware it ran on, not its fidelity class; the chip on a release-gate row says whether its drawing instrument is calibrated or the row is a gate-in-waiting.

Empty cells. A cell without a product verdict renders one of three ways. A single struck stroke is N/A by design: the check does not apply to that runtime. A diagonal hatch is unavailable: the capture exists but cannot be scored, because it failed an input-fidelity check, was measured at a refresh rate this target is not scored against, has a failed idle control, or is preserved evidence with no current verdict. A dashed, empty outline is missing: nothing valid was captured, so it is a gap to close. Every tooltip names the reason.

The idle-frame control. Every action sweep includes a control sample that performs no interaction, proving the target can hold frames at rest. When the control fails its own gate the host was dropping frames on its own, so none of that mode’s action scores can be attributed to the app: the mode is marked “no control” and left out of the failure ranking.

One capture per cell. Most drawing cells have one capture behind them; each tooltip states the count. A result close to a limit needs repeat captures before it is trusted either way (ADR-0136).

Focused action captures. Sources are applied in their listed order within each mode. A focused capture replaces only its named actions and requires a full sweep from the same product commit; anything else is refused. Raw drawing tables and action samples are re-scored with the current metric definitions whenever this report is regenerated — stored verdicts are not trusted. A struck action cell is N/A under the action plan that mode’s product surface declared; a dashed one is missing, and both tooltips keep the reason.

Rotation first frames on iPad Safari are N/A rather than gated: under ADR-0142’s resize anchor the value reads 0–2 ms by construction, so rotation there is scored by the post-action frame gates alone.

Additional scenarios and their remaining coverage.

Engine time is the state rollback alone; next-frame adds the following rendered frame. Gates: engine P95 ≤ 20 ms, next-frame P95 ≤ 33 ms, next-frame max ≤ 50 ms.

The product commit each cell’s evidence was captured at. “Actions at final commit” counts the action rows measured at this campaign’s final product commit.