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
{{ message }}
Repository navigation
Commit c2677fd
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: apple/runner/AgentDeviceRunner/AgentDeviceRunnerUITests/UnitTests/RunnerTests+SnapshotCapturePlanTests.swift
Copy file name to clipboardExpand all lines: apple/runner/RUNNER_PROTOCOL.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -166,6 +166,12 @@ Successful and failed responses use the same top-level envelope:
166
166
167
167
`data` is command-specific. Common fields include snapshot nodes, text lookup results, gesture timing, visibility metadata, and screenshot or recording output details.
168
168
169
+
Capture-plan snapshots carry `snapshotViewport`, the acquisition's declared viewport evidence.
170
+
Its shape is `{kind: "reported" | "derived", rect: {x, y, width, height}}` or
Copy file name to clipboardExpand all lines: docs/adr/0004-ios-snapshot-backend-strategy.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,8 +51,13 @@ The fold cuts screens under a modal only where the producer states containment.
51
51
**Geometry.** One published capture publishes one space: the app's orientation space.
52
52
The producer settles it in one pass after acquisition, because a merged tree carries no axis that a downstream reader could use.
53
53
A window declares its subtree's space from its own box. Other nodes inherit it from the window above them.
54
-
If no space can be named, the capture publishes reported geometry, and consumers fail open.
54
+
If no rotation can be named, the capture publishes reported geometry, and consumers fail open on rotation.
55
55
A placed iPad window publishes screen space in points, because its viewport, its screenshot, and the digitizer use that space.
56
+
The acquisition's `reported`, `derived`, or `missing` viewport evidence survives the runner boundary and capture transformations.
57
+
Only `reported` establishes the screen origin for capture-derived input.
58
+
A root-derived validation box preserves readable fallback trees but cannot upgrade unknown origin evidence.
59
+
Element mutations, mutating find, Maestro selector geometry, and snapshot-derived gesture bounds refuse an unknown origin with `window-origin-unknown` and `dispatched: no` before input.
60
+
Independent native queries and authored screen coordinates retain their own authorities.
56
61
57
62
**System surfaces.**`contracts/fixtures/ios-system-surface-hosts.json` is the closed registry of system hosts that present UI out of the app's process.
58
63
Observe and operate a registered host in place. Never activate it. `open` refuses to launch it.
Copy file name to clipboardExpand all lines: docs/adr/0011-interaction-guarantee-contract.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,7 @@ Completed process history is in git history.
14
14
- Prove every non-waived cell through a tagged contract scenario.
15
15
- Delegation-on-error does not prove success-path parity.
16
16
- On the native-ref path, before `tapTarget`/`fillTarget`, check offscreen, occlusion, and non-hittable against the node from the daemon snapshot.
17
+
- Explicitly unanchored capture geometry cannot authorize input. Check its viewport authority before point resolution, visibility rescue, or native-ref dispatch. Mutating find, Maestro selector coordinates, and snapshot-derived gesture bounds use the same check.
17
18
- The Apple runner does not resend a mutating command whose first send may have run.
18
19
- Multiple mutating selector matches collapse only if they form one ancestor–descendant chain and every member resolves to the same actionable node. Otherwise, the mutation fails with `AMBIGUOUS_MATCH`. Maestro's explicit expected-point/non-hittable compatibility path stays separate.
19
20
- Keep synthesized iOS gesture policy outside the element dispatch-path matrix.
0 commit comments