ARCADIA-Studio/harness/verification-v2-native.md

Lead native acceptance — 2026-09-05

The lead personally operated the Windows Iced application and three packaged native Linux releases through the Computer Use skill (@oai/sky). This record supplements the independent Windows reports, automated Linux report and API transfer report. It records observed behavior, including unsuccessful attempts, rather than inferring GUI success from tests.

Windows

• Operated repaired Capella 7.0.1 in an isolated imported IFE example: OA/SA nesting, semantic browser/properties and Functional Transition comparison. Cancelled that preview; the original model was not transitioned. Findings informed docs/research-v2-ui.md.
• In Studio, inspected syntax colors, inserted invalid ?, observed located live lint, rejected Apply with draft/model retained, then recovered with Revert. Navigated OA processes, SA chains/scenarios and state views; selected the second repeated message occurrence and confirmed its inspector/highlight.
• Opened the actual REST-exported api-edited-demo.arcadia through the native picker. Project/function name and alias, CAD URI and revision reflected the API edits. Edited CAD revision to CAD-REV-C-native-review, used Ctrl+S and verified persisted source. After an external comment append, Ctrl+S refused overwrite and retained the external bytes.
• New produced an empty model. Created a view and Assess sea conditions OA activity, previewed/created its SA Function, and observed target-view focus and creation-kind normalization. Preview blocked background Text navigation and Ctrl+Z. Explicit reverse creation and single-step Undo preserved the other layer.
• Found and fixed 150% nested-caption overlap and counterpart focus. The fresh reviewer personally reverified rebuilt nested typography, state-transition selection, minimum/default/wide layouts, fragment/branch creation and saved action rendering; see review-v2-final-ui.md.
• Launched the staged Windows release directly and inspected the default 1440×900 zero-check demo, then closed normally. The fresh reviewer subsequently rebuilt the final release, operated that exact packaged executable, created/saved/reopened an Action and confirmed Architecture retained its original three cards. Final binary hashes are in that report.

Native Ubuntu 24.04 / WSLg

Both sessions used the staged Linux executable with WGPU_BACKEND=vulkan and VK_DRIVER_FILES=/usr/share/vulkan/icd.d/lvp_icd.x86_64.json. The client rendered at 1440×900 with Mesa software Vulkan. The remote window's [WARN:COPY MODE] title is a compositor label; application stderr was empty and both processes exited 0 on normal close (sessions 58001 and 57111).

The native Open path dialog loaded the isolated controls-fixture.arcadia used by Windows review. The lead then:

1. Changed Independent energy from OA to SA through its graphical engineering-perspective control. The saved record preserved Energy kind and UUID 20000000-0000-4000-8000-000000000004.
2. Opened Manual trace. Apply remained disabled until explicitly choosing Other operational need; committing created a trace with canonical OA/SA endpoints and did not create another semantic element.
3. Changed a Traceability diagram's layer SA→OA→SA and confirmed that active diagram and editing perspective followed the committed owner.
4. Changed a function placement UUID to 60000000-0000-4000-8000-000000000099 and dragged the placement. The first gesture selected the parent without movement; the subsequent actual function drag succeeded. Saved source confirmed the new UUID and position (90,250), size (224,94). The automated regression separately sends the real SelectNode→MoveNode sequence with the pending UUID draft.
5. Relocated OA work_card into the SA Traceability diagram through Placement properties. The UI selected the destination diagram and SA context; saved source preserved placement identity and its artifact owner.
6. Saved through Ctrl+S, closed, refreshed the executable and reopened the saved fixture. All edits persisted. The artifact card correctly displayed Placement of OA "Rescue" updated · SA existing architecture.
7. Exercised the actual counterpart conflict dialog showing source/target names and current/proposed field values. Initial continuous typing exposed lost input focus during replanning; fixed stable widget grouping/order and rebuilt before repeating.
8. In the rebuilt dialog, typed successive name fragments and punctuation without refocusing; all remained in the same input. Changed counterpart to Other System Service: the previous merged value cleared and Apply became disabled pending review. Returning to the original counterpart did not revive the old decision.
9. Entered Reviewed rescue function, chose Keep target for description, and applied with no unresolved decisions. Saved source confirmed that name and the retained description System design deliberately changed.. Traceability displayed Reviewed. Reverse preview reused the counterpart with no field proposals or conflicts, then was cancelled.
10. Reopened the graphical branching-reviewed.arcadia fixture. Behavior rendered two repeated messages plus an Alternative fragment, a branch with guard sea_state > 4 && operator == "Ready", and its nested validated-report message. The fixture showed 42 elements, 23 relationships and zero checks.

The last fixture also exposed unwanted Architecture placements from Behavior creation. The fix confines automatic placement to the Architecture page; Behavior/Data still create semantic records. A meaningful regression checks Fragment→Branch→Exchange ordering, Data creation and exact preservation of every diagram, plus ordinary Architecture placement. The fresh independent reviewer verified the final Windows packaged Action/create/save/reopen workflow and unchanged architecture.

After Linux compilation/tests/release were refreshed, the lead launched that exact final staged executable (SHA-256 df88c9dd2f4759c95514c32c0c50ad225642fff085b67162e6bebafafad01b04). Ctrl+O opened the Windows-authored packaged-behavior-placement-reviewed.arcadia. SA Architecture showed the three original nested function cards at 150%, with no occurrence placement. Behavior → Repeated distress reports rendered the saved Review response readiness Action on the coordination lifeline after both messages. The model had 40 objects,23 links,zero checks and all changes saved. Normal Alt+F4 closed the process (session74334,exit0,empty stderr); a fresh window inventory confirmed closure. Creation itself was exercised in Windows, with this final Linux pass verifying cross-platform reopening/rendering.

Boundaries

No test server or Studio acceptance window is intentionally left running. Raw fixtures/logs are outside source under D:/CodexBuilds/Capella2-v2-01a06e2e/. Reports retain the evidence needed to understand them without that directory. Native Linux runs cover this Ubuntu/WSLg/Mesa environment, not all graphics drivers. Remote CI, Docker execution/remote installation, actual Rust 1.90, assistive-technology certification and production-scale performance were not exercised.