ARCADIA-Studio/harness/multiselect-process-evidence-20260923/reviews/run-3-observations.md

Process native run 3 — parent observations

Root operated the Windows app through Computer Use on 2026-09-23. Source b743a10d51032dc1655b94fed5e49fbbbcee83f4; matching captured GUI/checker builds windows-build-2/native-build-2. Production is unchanged from ff712b2419. This run followed a preparation-only run-2 failure; no GUI launched in run 2. Review screenshots with the same-numbered accessibility/time JSON, prepared/start/finish records, and snapshots. Native acceptance below is the parent's observed workflow judgment, separate from automated receipt consistency.

Observed actions and outcomes

• 01–11: launched, opened the generated run-3 working source, selected Behavior, saved baseline. The Open dialog's accessibility click did not dismiss it; fresh window selection and screenshot-grounded coordinate Open did. UIA reports Search Box focus although the visible filename caret/text is correct. No app failure is inferred from that automation mismatch.
• 12–16: selected first invocation's Shared detail; right-clicked second invocation's tile and explicitly opened its definition while it was nonprimary. Actual defining leaf became editable. Back restored the second qualified tile alone, Shared detail read-only Properties, exact Second use → Shared detail breadcrumb, and caller camera. Outer card was not primary/highlighted. This corrects run-1 frame 26.
• 17–18: Explorer selection of the outer Second use changed to its local editable inspector and outer-card highlight; the qualified leaf was no longer primary.
• 19–21: selected the second leaf and used inspector Open referenced definition, then Back. Current-primary return again restored exact second leaf and read-only Properties.
• 22–23: Explorer selection of the same-ID Shared detail while in preview navigated to its defining owner and editable local inspector. Saved complete Project remained unchanged.
• 24–27: returned to OA group order, selected Card A. Frame 26 tool output was truncated; frame 27 reobserved before further input.
• 28–31: context Add included A-to-U link with Card A, count 2, link primary. Drag A after B was refused with the explicit local-cards-only explanation. Membership, primary, camera and order remained unchanged. Saved Project unchanged.
• 32–36: clicked C, context Add A, then context Inspect this element on C. Count stayed 2; A secondary blue and C primary teal, Properties Card C. Selection order was C then A, contrary to source A then C.
• 37–38: dragged C onto selected A's lower half. Order, count and primary remained unchanged; saved Project unchanged.
• 39–40: dragged C from (420,620) after B at (420,529). Left column became B,A,C; right column U,V unchanged. Count 2, C primary and A secondary persisted; camera stayed 100%. Status reported two contributions reordered. This discriminates against singleton pressed/primary C, whose valid same-column move after B would leave the original order. Saved complete Project matches literal [B,U,A,V,C], with all other model records identical.
• 41–42: exactly one Ctrl+Z restored A,B,C and original complete Project; selection and primary stayed stable. Saved Undo snapshot.
• 43–44: exactly one Ctrl+Y restored B,A,C and the reordered complete Project. Saved Redo snapshot.
• 45–52: opened the exact run-3 working project again in the same process, returned to Behavior/OA group owner, observed B,A,C and U,V, and saved. Transient selection cleared on reopening. Reopened complete Project matches reordered.
• Closed via Alt+F4; launch wrapper finished 13:43:54.209222Z, exit 0, empty stdout/stderr, binaries and immutable fixture unchanged.

Independent saved-model and byte checks

Eight complete-Project checks passed: baseline, qualified-navigation, mixed-refusal, anchor-noop and undo equal the immutable baseline; reordered, redo and reopened equal the literal expected Project. history-bytes.json passes ten files per snapshot: fixture/baseline/undo/three unchanged extras are byte-identical; reordered/redo/reopened are byte-identical. Only oa/behavior/process_oa_process.arcadia changes across the two groups. These checks do not infer gestures, focus, selection, read-only state or one-step history; the observed actions above supply that evidence.

Scope and limitations

Accepted for the observed Windows OA workflow at 1442×932 and 100% zoom. Context Add/Inspect was used; native held Shift was not exercised. Drag API executes a whole gesture, so held-motion line readability comes from the separate actual-WGPU mounted OA/SA capture. Native SA reorder, alternate DPI/minimum window, full accessibility, aggregate deletion, Allocation/Scenario adapters and Linux are not established. Run 1's qualified drag/Delete refusal is historical b153 evidence, supported by final focused/full tests; it was not repeated here. Existing crossing/routing appearance after reordered rows is visible and is not claimed repaired by this change (routing tracked separately in issue 32). This is branch-specific verification, not combined integration or release acceptance.