2.6 KiB
Native renderer observation
Candidate Project generator: 3e21c1bca245944ae0ec7bb02aaa920f45f2cc30.
Reused native executable: d6f45a13a7b8ab8dc9b84ee432a832609f5af6ed,
SHA256 133375d57bdecf3f3effe5ecc13ec121e1257b90838f2cdb64fb91aa9a530d1b.
This observes saved experimental Projects in the existing renderer. It does not
exercise the experimental planner through a native Arrange command.
The parent used the Computer skill and native Open dialog to import four exact Project extractions, without editing or saving. Five screenshots record:
01-two-container-boundary: Fit102%, Left A→Right B and Left B→Right A appear as separate straight horizontal connections. Both labels are readable between containers, with no shared route or apparent endpoint ambiguity.02-two-container-scc: same viewport/scale, prior SCC ordering. Routes visually meet at the right container boundary and run alongside its border; the apparent straight rows misleadingly suggest the opposite endpoint pairing. This is a concrete improvement from the first image's reordered children.03-anchored-boundary: authored anchors retain bent routes. The two label backgrounds interrupt the right parent border; the label text remains readable and does not obscure child names. The emitted two label/node intersections should not be described as two unreadable labels or child-name occlusions.04-local-scc-boundary: Fit55%, intact Y1/Y2 block above X1/X2, Z later. Small text and multiple adjoining/reused strokes make tracing harder than the simple two-edge example. A structurally correct block order is insufficient to establish native usability for this case.05-local-scc-selected-lower-boundary: selecting the lower source connection highlights its path to X1 and displays Source B / X1 in Properties. Selection helps resolve the route among neighboring strokes. No endpoint edit occurred.
The process was closed by Alt+F4. The immediate window list briefly retained the closing window; a subsequent capture reported no foreground process. The owned observer then returned exit0, empty stdout/stderr, unchanged immutable inputs, and no running process. All six staged working JSONs remain unchanged (only four were opened). No save, undo/redo, new planner invocation, API integration, general accessibility acceptance, or whole-application acceptance is inferred.
Evidence includes stage/source extraction receipts, per-run process records, five screenshot/metadata pairs, and the launcher. Package binaries are hash-bound in the manifest rather than duplicated in the research archive. Windows native inspection only; Linux remains excluded.