Native navigation, definition/back and narrow Fit
Closed Windows Run 9 on 2026-09-22 exercised the frozen product at b10b28cefd1d0794073ba241a0c8de9a83e85f68. Root operated the native GUI; this archive preparation performed read-only integrity verification. The original operator record, 14 current-state captures and unchanged saved bytes support the bounded findings below. No new compiler, semantic comparator, accepted model edit or source rewrite was used.
Observed workflows
| Workflow | Native observation | Captures |
|---|---|---|
Steps reference @updated_report → Show in diagrams |
A/B/C/caller Automatic destinations; choose B and exact Updated occurrence, revealing Saved B and selected second green arrow at displayed 125% | 01–02 |
Exchange @incident_report → Show in diagrams |
Five destinations/nine representations; A distinguishes Initial and Updated caller occurrences; Reporting procedure detail opens the Check occurrence in its Automatic definition | 03–05 |
Definition occurrence @review_delivery → Show in diagrams |
Exactly one destination/representation, Reporting procedure detail; no caller arrow through the opaque use | 06 |
| Saved A selected opaque use → Open definition → Back | Caller at displayed 59% after pan; Automatic definition has one Check arrow and Back; returning restores Saved A, same selected use, displayed 59%, visibly matching pan and open Details panel | 07–09 |
| Narrow Saved B Fit, plus, minus | Actual window shrinks from 1442×932 to 1192×932; Fit displays rounded 1%, plus expands geometry beyond canvas while still displaying 1%, minus approximately restores Fit extent | 10–12 |
| Selected use → Delete from model warning → Cancel | Warning names the use and owned/reference/view effects; cancellation retains it; final destructive confirmation never clicked | 13 |
| Return to A and Save all | Under changed viewport A now fits at displayed 62%; clean saved header/footer and exact original incident source bytes | 14 |
The caller camera roundtrip held the viewport unchanged; matching images establish visual restoration, not exact internal camera bits. The requested background pan was approximately (+29, −32) screen pixels; no independent logical-coordinate precision is asserted. The Details panel exposed Scenario order arrows and explained semantic order versus saved positions; no reorder was performed.
The first right-border drag failed to resize and remains recorded. The actual narrow window was obtained separately via Alt+Space → Size → Right → click. At narrow Fit, approximate horizontal geometry x278…813 lies within approximate canvas x269…823, but individual tiny headers and the self-call cannot be distinguished. Their complete containment and tiny-hit usability remain unproven. Rounded 1% labels conceal small zoom changes; no jump to 5% was observed, and neither exact scale nor OS logical input bits are claimed.
The deletion warning advises Hide for diagram-only removal. This trial does not establish whether that advice applies correctly to Scenario; that requires separate review. Warning/cancellation is not deletion or lifecycle acceptance.
Independent review inspected all 14 images and checked process, capture and source bindings. It found no material inconsistency in these bounded claims while retaining the stated limits on tiny geometry, camera precision, deletion and broader acceptance.
Process and source integrity
Run 9 PID 1224 started at 22:22:25.704686 UTC. Root recorded Alt+F4 at 22:39:52.270; the bound observer recorded exit 0 at 22:39:54.367065. Launch and close agree on PID/start time, source pin and launch hash. The launch binds the exact Run 8 close. Native stdout/stderr are empty, and all bound immutable manifest files were rechecked. Process-exit records alone do not establish the close cause; Alt+F4 is the operator's observation.
The final incident checkpoint is 6,217 bytes, SHA-256 b746965f034a4befb449d17e568dd5ae0b2ee81b3c34f82883e48e0c54833b25: exactly the launch input, final working incident source and published spacing result. Service source remains 6,278 bytes, SHA-256 92723225deb64884d7cd01e3bf50f24620fbdd583e8bab7bd3f391fb22a46f5d. Both complete pre/post working-file records match. These byte equalities establish saved-source preservation; they do not inspect every editor, scheduler or history state.
archive-manifest.json binds 37 originals, 1,831,644 bytes: every Run 9 file, prior close and input manifest. All original copies are byte exact with length/SHA-256 verification; original JSON is never rewritten. The 14 JPEGs have 14 distinct hashes matching capture metadata and JPEG signatures/MIME. This archiver did not independently repeat visual inspection; original capture notes and workflow descriptions remain operator observations. Two intentional empty .log files need explicit forced Git addition.
Pinned prerequisites and peer reproduction
- Service archive at 7dbf7ea contains the exact staging, launch, verification and native-plan recipe, Run 8 close and transitive build/gate prerequisites. Recipe Git blobs were checked against the local files used by Run 9.
- Spacing archive at 65f7302 supplies the incident checkpoint; the archived Run 5 reopened bytes were compared directly with this Run 9 final checkpoint.
GUI SHA-256 remains 7ece85c6012ae0ae75fc56ed3c3aadb8bc116448ad1782be422ef34a629dc3ce. EXE/DLL payloads and private profile are excluded. Original absolute paths describe the recording machine; peers must fetch the pinned commits, verify the manifest and referenced blobs, then reconstruct the admitted Windows package using their own paths and the published build/staging recipe. Repeating native workflows requires a fresh run directory/profile and new observations; prior local services, files and GUI state are not shared across machines. No new comparator is needed to audit this archive's exact saved-byte preservation.
Friction and exclusions
Destination rows and diagram captions truncate; the operator observed hover tooltips on some rows. The extreme horizontal model becomes a thin band at narrow Fit, making exact reveal materially more usable than tiny pointer targets. Existing inspector scrolling and feedback findings remain in the preceding service archive. These observations do not establish broad accessibility, continuous interaction performance, exact tiny-geometry containment, expression evaluation, other lifecycle cases, Linux or full native-plan/release acceptance.