ARCADIA-Studio/harness/experiments/boundary-order-20260925/native-review.md

Boundary-order native evidence review

Independent review, 2026-09-25. Inspected all five archived PNGs with view_image, their capture metadata, the staging/launch/close records, package and source attribution, and the private profile's recent-model list. No new GUI session, import, build, experimental Arrange invocation or source change. This review stops at the existing evidence as requested by the user.

The simple boundary case is visibly easier to trace than its SCC control. Authored anchors retain a small label-background/container-border conflict, while the local-SCC overview still needs selection to disambiguate a boundary route. This is limited native observation of imported geometry, not acceptance of a production Arrange replacement.

Attribution and integrity

• Reused GUI source: d6f45a13a7b8ab8dc9b84ee432a832609f5af6ed; executable SHA256 133375d57bdecf3f3effe5ecc13ec121e1257b90838f2cdb64fb91aa9a530d1b; DLL SHA256 aa282fa47bb2c4e210cea5e470cdbdca58568f0be0bc73e404d86ab9cd95ef6a.
• Imported candidate and paired SCC Projects were generated at 3e21c1bca245944ae0ec7bb02aaa920f45f2cc30. The existing native renderer displays those raw Projects. The experimental boundary planner was not executed through the GUI's Auto-layout control.
• Independently rehashed 21 referenced records covering the manifest, launcher, source-run/child receipts and stdout, reused attribution, staged executable/DLL, six input Projects, launch preflight and native logs: no mismatch. All six working Project hashes agree between the recorded preflight and close inventories; no working-file change was recorded.
• Manifest SHA256 is 940a7605b5a83308261e1fde0ecd7291cc855614a515e87e084823c8fc4e9016. Private LOCALAPPDATA and unrelated working directory are under boundary-native-20260925/run01.
• Start/close records identify PID 5492, observed exit code 0, no observer failure, unchanged immutable inputs and empty stdout/stderr. The parent reports closing with Alt+F4. The receipts independently establish observed clean process exit; they do not by themselves establish the particular close gesture or GUI quality.
• The private recent-model list corroborates four imports: simple boundary, simple SCC control, anchored boundary and local-SCC boundary. Two additional staged SCC controls were not observed natively and are not claimed here.
• Several capture JSON window-title fields lag the actual screenshot title, including the first capture's Untitled mission and the fourth capture's old two-container title. These fields alone do not identify the loaded Project. The image's visible title/status path and the recent-model entries provide consistent attribution. All capture metadata names the staged executable and the same window ID.

Visual findings

01 — Simple boundary, 102% zoom. Left A and Left B remain in their canonical upper/lower order. The right children are Right B above Right A. Each connection is a separate horizontal line into its matching child. Both route labels are readable between the containers, and their association with the two separate lines is visually clear. This screenshot supports the intended local ordering improvement without a selection aid.

02 — Paired simple SCC control, 102%. Right A is above Right B, so the two connections take opposing vertical travel beside the right children. Their vertical portions occupy the same visible corridor near the right-container boundary; direction and connection identity are substantially harder to follow than in 01. The labels remain legible, so the defect should be described as route association/shared travel, not unreadable label text. No native selection trace of this control is archived; exact endpoints continue to be established by the input model and routed evidence.

03 — Anchored boundary, 102%. The improved child order remains, but the authored source/target port fractions produce short downward bends at the right side instead of straight connections. Both label strings remain readable. The white label backgrounds reach and interrupt the Right group's left border near the route corridors. This is a real local visual conflict, but describing it as text obscuring the Right child name, an unreadable label, or a blocked arrowhead would overstate what the image shows. The artifact is principally label-background occlusion of the parent outline. The screenshot supports retaining that limitation rather than promoting the metric's label/node count into an unqualified severe text-collision claim.

04 — Local SCC boundary, Fit 55%. The Y1/Y2 pair is grouped above the X1/X2 pair, with Z to the right. The grouping and rank structure are visible, but labels are small at this fitted scale and several routes run close together or merge visually. In particular, the unselected Lower boundary approaches the Y2 region before continuing down toward X1; an unaided quick reading could assign it to the wrong nearby node. Whole-diagram fit therefore preserves overview at a readability cost. This image does not support a general claim that coherent SCC blocks make all individual routes easy to trace.

05 — Selected Lower boundary, 55%. The highlighted route visibly runs from Source B, turns downward beside Y2 and ends at X1. The properties pane independently names Lower boundary, source Source B · @source_b, and target X1 · @x1. This confirms that the selected relation has the correct endpoint and that selection supplies a useful tracing aid for this witness. It does not eliminate the ambiguity of the unselected overview or establish the readability of every other local route.

Scope of the result

The existing five observations support a narrow positive result for the simple two-container case, a modest remaining border/label-background conflict with authored anchors, and an unresolved overview/tracing cost for the local-SCC case. They do not test experimental command integration, Undo/Redo, routing edits, repeated Arrange in the GUI, automatic-side capacity cases, all frozen cases, or general accessibility/responsiveness. Existing numerical and conservation reviews remain separate evidence. No further native investigation is proposed as part of this completed checkpoint.

Screenshot SHA256:

File	SHA256
01-two-container-boundary.png	bc4e28a0fcc37cdc4c904993b67e5b018c66a3a0a2ff7c2511fec324e03d5cd7
02-two-container-scc.png	e1c68d66a4eae12c2e2c056858a1d4fc6b5eec8c387ee39b19337abbce7f49cf
03-anchored-boundary.png	8038656c660d826426c36e059997eb955ef8e84db4bdc2d23bcc214f64580c1d
04-local-scc-boundary.png	677057c6870103daeeb31d48a11a5f9b8b8ebb604a7864e71a541a28d6024342
05-local-scc-selected-lower-boundary.png	732cc188a8e8fbe3632d3bd824f218560c5a40afac053d5f8936e62be2699861