ARCADIA-Studio/harness/review-ui.md

Independent UI and runtime review

Reviewed 2026-09-05 using the actual Windows target/debug/arcadia-studio.exe through the Computer Use skill and @oai/sky. This reviewer did not implement the application or modify implementation files. The running executable was the build supplied at review start; concurrent source fixes are not covered here.

Original findings (resolved in final release below)

• P2 — nearby horizontal interaction becomes invisible. In Text, apply the fixture below, open Architecture, and select Observe. At 60% zoom the Report label appears inside Observe's card, while the line and arrow between Observe and Respond disappear. diagram.rs draws a fixed 170-unit opaque label background over the 76-unit gap between the cards. Text layering also makes the label visible over the card. Selecting the relation reproduces the same issue, as does changing it to a Contribution between equally spaced cards. A normal close horizontal arrangement must retain a visible connection and a label that does not impersonate card content.

  arcadia 1;
  project "Review cycle" {
    activity observe "Observe" { position (0, 0); }
    activity respond "Respond" { position (300, 0); }
    capability safe "Safe operation" { position (600, 0); }
    interaction report "Report" from observe to respond;
  }
  

• P2 — inspector preserves an unrelated scroll position. At minimum size, select a process and scroll the inspector to Share & Explore. Load the rescue example, select its process, or create New. The new selection/project's name, kind and description may be above the visible inspector. New from the clean example displayed Stable ID at the top instead of project properties. Reset or intentionally anchor the inspector when its selection/project changes.

• P3 — process continuity warnings omit the offending occurrences. Move the second rescue process step above the first. Model checks displays two identical Process 'Distress to recovery' has disconnected consecutive steps. messages. Include the adjacent step indexes/names so users can identify each gap. Both warnings correctly disappear on Undo.

No crash, data loss, or blocked recovery was observed in the exercised workflows. The three findings above were reported for the initial reviewed debug build. Their resolution was independently verified against the final release below.

Personally exercised behavior

Workflow	Observed result
Launch latest Windows executable	Clean native window, built-in model rendered, 9 elements / 9 relationships / 0 checks.
Open D:/CodexBuilds/Capella2-01a06e2e/harbour-ui.arcadia through native Open dialog	Harbour response loaded with 6 elements / 5 relationships / 0 checks and All changes saved. Triage incoming report, description's two lines, and exact X=350.25 visible.
Invalid source + help navigation	Appended invalid after the project's closing brace. Getting started remained accessible without losing draft. Architecture returned to Text with line 40, column 1 diagnostic and preserved 6-element model. Revert restored clean source and saved status.
Invalid graphical property + help recovery	Replaced activity X with invalid. Getting started stayed on Architecture, with numeric error in footer and inspector still visible. Revert property edits restored 350.25 and clean status.
Window resizing	Inspected 1440x900 content (1442x932 outer) and 1100x700 content (1102x732 outer). Header, sidebar navigation, inspector, footer, text toolbar, source editor, help link and modal actions remained reachable without overlapping controls.
Fit at minimum size	Six harbour cards fit inside canvas at 46%; text is small at that zoom but no cards were clipped.
Process reorder and checks	Moved Incident assessment above Distress signal. Process narrative immediately reflected order, checks count became 2, and Model checks showed continuity warnings. Ctrl+Z restored order and All checks passed.
Process remove / append	Removed Rescue assignment occurrence: narrative became two steps, all 9 relationship records remained. Picked Rescue assignment and Append step: original three-step narrative and clean model state restored.
Empty project states	New produced zero records; diagram was empty with creation toolbar, Process page had Add process, Model checks reported consistent references, Text showed a valid empty project.
Authoring in minimum-size Text view	Entered Review cycle fixture above. Apply generated stable IDs/canonical source, graph showed all three elements and one relation, three expected incompleteness warnings.
Edit existing relation kind and both endpoints	Selected Report via Observe's Relationships list. Changed Interaction to Contribution, chose Respond source and Safe operation target, Apply. Inspector showed Contribution and updated endpoints, graph record counts updated, checks fell from 3 to 2. Text showed contribution report ... from respond to safe_operation; with the existing relation ID retained.
Unsaved-change modal	Loading built-in example from disposable Review cycle displayed Save/Discard/Cancel modal with legible minimum-size layout. Discard replaced only disposable in-memory review model.
Clean exit	After restoring the rescue process to original state, Alt+F4 exited; fresh sky.list_windows() confirmed no Arcadia window remained.

No existing fixture was saved over. Review-created models were disposable in-memory data. The original harbour fixture was opened read-only through UI.

Scope and remaining verification

This pass covers Windows. Linux rendering/runtime, final packaging, full automated checks, and edits to source after review started are outside this review's evidence. Exact-string edge cases were not re-exercised here because the primary independent focus was navigation, source/property failure recovery, relation mutation, process editing, and responsive layout. Accessibility tree for Iced exposed the native window rather than individual application controls; app interaction therefore used inspected screenshots and keyboard input.

Computer Use ownership released to the lead agent after confirmed clean exit.

Final release follow-up — 2026-09-05

Independently launched D:/CodexBuilds/Capella2-01a06e2e/release/arcadia-studio.exe and personally verified the following using Computer Use at the default 1440x900 content size:

• Pending identity + same-card drag regression passed. Selected Report distress (position 360,250), typed stable ID 00000000-0000-4000-8000-000000000123 without Apply, then dragged that same card. The card moved to 390,570 and retained both relationships. Canonical Text displayed the new UUID and position (390, 570);; both the allocation and interaction still referenced report_distress. Counts remained 9 elements / 9 relationships / 0 checks. Undo first restored 360,250 while retaining the new ID; a second Undo restored the original ID and clean state.
• P3 contextual warnings resolved. Moved Incident assessment above Distress signal. The two Model checks messages now separately identified steps 1/2 and 2/3, the interaction names, and the incompatible ending/starting activity names. Undo restored All checks passed.
• P2 inspector scroll issue resolved. Scrolled the process inspector to Share & Explore, then selected Project properties. Inspector reset to its top, with project name and Apply properties immediately visible.
• P2 horizontal connection issue resolved. Re-entered the exact Review cycle fixture from the original finding. At 60%, Observe and Respond were visibly joined by a continuous line and directional arrow; Report appeared above the line in the gap, outside both cards. No background mask obscured the connection.

All temporary changes were undone. Alt+F4 closed the clean release, and a fresh window inventory confirmed it exited. No test fixture was saved or overwritten. No unresolved material UI findings remain from this review. The final follow-up does not replace the initial minimum-size coverage or the lead's Linux checks; it specifically proves the reviewed fixes and pending-ID/drag regression in the actual Windows release. Computer Use ownership released again after exit.