ARCADIA-Studio/harness/release-palette-native-20260910.md

Palette native acceptance — 2026-09-10

Codex-9e8r6t /root, actual Windows Computer Use through the bundled @oai/sky API. This is ongoing acceptance, not a release verdict.

Candidate and isolation

Initial binary SHA256 1B47C096624BB1101BEC8B18E63CD601A259DFF8C1BEC24581C31C6B511F9411, 109,516,288 bytes, staged with the exact LLVM-MinGW libunwind DLL and examples in .local/native-qa/palette-20260910-v1/bin. Process4852 started at 17:42:58UTC with fresh task-local APPDATA/LOCALAPPDATA and a clean Windows PATH. process.json records hashes, paths and process identity; stdout/stderr are retained there. No pre-existing Arcadia GUI was touched. Native window525310 was selected from actual returned windows.

The frozen independent fixture was copied to the run's work directory. Checker self-check and baseline passed before UI work using the local toolchain runtime on PATH. The native Open dialog loaded this copy. UIA value setting in the Windows file dialog was unavailable (CacheRequest,0x80070057); actual focused filename typing succeeded. This was a test-tool issue, not an app error.

Observed and verified

• At1442×932 outer dimensions, expanding the palette reveals Entity/Actor, Activity, compatible connections and Add existing. Incompatible drawing tools explain their missing source. Expansion changes canvas width only.
• Entity tool → point(381,435) → focused inline field → Rescue team → Enter worked. Canvas origin remained at approximately(261,315) throughout all phases; the accepted card appeared at the chosen screen point. No placeholder model element was accepted before Enter. Opening a project had retained a camera pan, so this screen point was not world(120,120).
• Ctrl+S succeeded first submission. The initial fixed-coordinate entity oracle intentionally failed because the operator had not yet set its required world position: saved(90,90.20001220703125), expected(120,120). This is not evidence of a click-transform defect: the observed screen placement matched the click. The complete click-state bundle is preserved in checkpoint-entity-click.
• One Ctrl+Z removed the whole creation. Ctrl+S then passed the complete baseline model and both exact source files. Preserved in checkpoint-entity-undo. Ctrl+Y restored the same Entity/placement identity visually.
• Through the actual node context menu's Placement properties, the operator explicitly set X=120,Y=120 and applied. Ctrl+S passed the independent complete entity model and all three source files. Preserved in checkpoint-entity. The existing oracle was not changed to fit the observed result.
• Native border resizing reached1102×732 outer dimensions, corresponding to the configured1100×700 client minimum. Both expanded156px and compact36px palettes remained usable. The canvas origin stayed stable; the existing entity retained its world coordinates and visible camera position.
• Compact Actor tool → lower-right canvas point(730,673) opened the inline editor clamped wholly within the available canvas. A long Unicode name was horizontally editable without card overflow; Create/Cancel remained visible.

Confirmed defect and next verification

Escape from the focused inline text input does not cancel on the first key. It unfocuses the input while retaining the inline card and pending title state. A separate screenshot observation confirmed the result. app.rs's keyboard subscription discards captured Escape, and Iced's text input captures it. Palette worker is implementing narrowly scoped inline cancellation, preserving other widgets' captured-Escape behavior. This was missed by tests that directly sent the Cancel event. Stale-Submit visibility was independently found in source and is being fixed in the same next candidate.

Explicit Cancel subsequently closed the draft; Ctrl+S then passed the complete entity model and all three exact sources (checkpoint-cancelled). The captured pending recovery snapshot is separately preserved in checkpoint-long-draft-recovery: exact Actor name, point(439,328.2), placing=false. It is a retained checkpoint for a recovery test, not a claimed crash test. The Cancel footer still gave the old positioning instruction; that feedback is also corrected in the next candidate. escape-retains-inline.png records the actual first-Escape failure.

Scenario layout baseline

Opened the staged teaching example from Home at the same1102×732 outer size. Its process view uses most of the center pane for the graph. Selected Scenario Repair request and measured reply: its heading/tools pushed the idle diagram top to approximately483px, leaving only its upper part visible. Choosing + Message shrank its diagram to approximately110px: only the Controller and Technician headings fit; the exchanges were below the viewport. The form also had a small independently scrolling field area. Saved evidence: scenario-minimum-before.png and scenario-minimum-pending-before.png. This confirms the source audit's scenario workspace problem. Explicit Cancel restored the clean teaching model; no semantic edit was committed.

The first candidate closed cleanly through its native title-bar button. The subsequent process check found process4852 absent and its stderr log empty. Next: verify corrected first Escape and restored checkpoint focus, then F2, named/existing placement, allocation, connection, transitions and history/reopen. Minimum-size observations alone do not complete those remaining workflows.

Candidate 2: focused Escape and recovery

The isolated palette-20260910-v2 stage contains the rebuilt candidate with SHA-256 E6D6B1D975A11F242D288039E8F07D20E5474EA9C7CFCDE93F1318046EA548D4. Its process.json records process 648, the executable and runtime DLL hashes, and its separate profile/work directories. The candidate 1 stage was preserved.

Home's Recover action restored the retained long Actor-name checkpoint. Both the complete accepted bundle and serialized architecture draft matched the preserved checkpoint; the comparison is retained in checkpoint-restored-recovery. The inline card was visible with its full name and position, but recovery did not automatically focus its name field (recovered-inline-before-focus.png). After clicking that field, one Escape cancelled the draft, returned the palette to Select, and showed Cancelled · Select / move. This verifies the actual captured-key fix, not merely a directly injected Cancel event.

Ctrl+S opened Save As for the recovered copy. Submitting the full path to recovered-work/project.arcadia saved successfully on the first submission. The independent checker passed the complete Entity model and all three exact source files; checkpoint-recovered-save preserves the result. A read-only repeat after the desktop-control stop also passed the same oracle.

The user stopped Computer Use with physical Escape during the next observation. No rename action was performed by that stopped call. Native control is paused; F2 rename, the remaining complete basic-editing sequence, transitions and final reopen/runtime acceptance remain pending. Source integration and packaging continue. Recovery autofocus remains a small confirmed usability follow-up.

Resumed native F2 check

The user subsequently explicitly reauthorized Computer Use. Continued on the same separately staged candidate 2 (E6D6B1D9…), not the newly integrated source. Selecting Rescue team and pressing F2 opened the anchored, focused name editor. Before applying, an independent expected bundle was copied from the already oracle-verified Entity snapshot and changed only the unique quoted name in oa/participants.arcadia to Rescue coordination team; all other bytes and the complete file set were retained. Enter accepted the visible name, retained the same alias/UUID and geometry, and first-submit Ctrl+S saved it. All three saved files matched that expectation byte-for-byte. One Undo followed by Save passed the complete Entity model/three-source oracle. One Redo followed by Save matched the same name-only expectation exactly. Evidence is retained as expected-entity-rename, checkpoint-entity-rename and rename-source-result.json. The last Undo/Save returned the working fixture to the original Entity baseline.

Input limitation observed: after Ctrl+A selected the original name, the first Computer Use type_text call left an empty field. A fresh observation confirmed that state; explicit refocus and a second type_text produced the intended name. The cause is not established, so this is not recorded as a proven application typing defect or as uninterrupted first-attempt typing. Applying, history and source persistence were tested only after the correct text was visible.

Actor continuation and clean close

Continued the ordinary root-creation sequence at 1442×932 outer size. Four minus steps changed the 150% overview to approximately 72%; camera translation and the existing Entity's world placement remained stable. Compact Actor tool, blank point (817,440), Control centre, Enter created the Actor at that point. The actual placement property values were approximately (680.1408,120.8218), consistent with the fractional zoom. As the independent contract requires, the operator explicitly set X=680 and Y=120 in Placement properties and applied. Ctrl+S saved successfully, and checkpoint-actor preserves the complete bundle. Its Actor ID is b3cd865b-b1df-43b4-9396-2e4aaec65367, placement ID ee9a090c-b322-4e37-b6d4-40e2a1af725f. The complete basic oracle is still pending the Activity, existing placement, allocation, Interaction and rename. No complete Actor-only model oracle is claimed from the property inspection.

One attempted Y replacement appended text after a multi-click selection. The operator observed it, explicitly selected all and cleared, then entered 120; only the visibly correct X/Y values were applied. User input interrupted one typing attempt; root reobserved before continuing. These automation observations remain distinct from a demonstrated application defect.

The candidate closed through its title-bar button with all changes saved. The subsequent process query found process 648 absent; stderr was empty. Root transferred the exclusive native-input lease to the independent Capella creation workflow investigator. A future current-build session can resume from the whole checkpoint-actor directory without redoing earlier accepted fixture creation.