Scenario native Details trial 1 at b10
This is a partial native checkpoint, not full native-plan acceptance. Root directly operated the staged Windows GUI at b10b28cefd1d0794073ba241a0c8de9a83e85f68. The bound Run1 process (PID3232) ran2026-09-13T14:42:08.4399536Z–14:59:08.2082309Z and closed0; root reports normal Alt+F4. Both logs are empty, immutable inputs stayed unchanged, and both working fixtures finished byte-identical to baseline. See the complete root observation and correction, launch and normal close. The archive worker performed no native input or execution.
Capture defect and evidence distinction
All24 archived image files are the same146733-byte JPEG, SHA256 016c58199383a7b0280ab848673c8622dc56acd6d8338c4151db1a6cd1eb9da3, despite their original .png names. Inspection shows only the first Saved A/Initial/Details state. Files02–24 and their image associations do not corroborate the later states described in metadata. Exact bytes, names and metadata are preserved as failed capture evidence; they have not been repaired, transcoded or relabeled. Root identified a likely persistent closure retaining the initial state and appended a correction before publication. Any Run2 captures are separate new evidence and are excluded here.
The single unique valid image shows Saved A at74%, Initial selected, Details open and the initial_report inspector. Later UI results below are root's direct live observations, not independent visual conclusions from these duplicated files. Saved-source comparator results provide separate machine-checked model evidence.
Observed and independently checked scope
Root reports distinct Initial/Updated occurrence selection; B Fit below5% and incremental zoom; Focus→Details→Properties restoring the correct editable inspector; Name draft/Revert and one accepted Name edit with model Undo/Redo; the actual Text Diagram A→Whole→Scenario arrangement picker B→Details Properties route following the selected Saved record; independent semantic selection staying selected across arrangements; and source/tree/keyboard exact occurrence navigation. The report preserves a failed first file-dialog UIA input and an ambiguous tiny2% header hit. It does not silently turn those attempts into successes.
Five immutable source checkpoints and four complete comparator outputs are preserved:
| Comparison | Independently checked result |
|---|---|
| Name accepted | Complete Project differs only in occurrence70200000-0000-4000-8000-000000000020 Name: Initial incident report→Initial incident report [Details trial]. |
| Undo | Complete Project equals pre-Name checkpoint. |
| Redo | Complete Project equals accepted Name checkpoint. |
| Restored | Complete Project equals pre-Name checkpoint again. |
All four comparator processes exited0 with semantic_pass and unchanged inputs. Actual and independently expected Project JSON files are byte-identical for each comparison. Archive review additionally compared the entire baseline/accepted JSON structure and found exactly the Name path above. Source checkpoint bytes01=03=05 and02=04 also match. These comparisons do not inspect the live editor buffer, camera or history stack; root's observed actions provide that separate context.
Portable provenance
Manifest binds129 exact copied originals totaling4325969 bytes: the closed run and24 metadata/image pairs, five checkpoints, four comparator output sets, stage/launch/verifier/recovery checks, input/staging manifests, immutable fixtures/plans and restored Run1 working snapshots. It also includes the failed original stage predicate. Recovery documents its string-versus-parsed-DateTime failure and the exact UTC-tick correction; no tolerance or relaxed binary hash check was introduced. The verifier remains SHA8306f4d4a1dde1c075a47994cd9d92738803c8b3b255b3e9907f0cb24749d91d.
All53 already-published staged gate files are linked by exact SHA256/size/Git blob rather than recopied. One unarchived immutable preparation-handoff record is included locally to complete the staged manifest mapping. Dependencies are available at these exact commits:
- GUI build and both comparator recipes, build/self-check evidence.
- Strict preflight,1095-name LIST and301 focused passes.
- 1091 full passes/four ignored and regular strict pass.
The omitted GUI is116721152 bytes, SHA7ece85c6012ae0ae75fc56ed3c3aadb8bc116448ad1782be422ef34a629dc3ce; runtime190464 bytes, SHAaa282fa47bb2c4e210cea5e470cdbdca58568f0be0bc73e404d86ab9cd95ef6a. Binary payloads, private profile, unrelated working directory, dependency caches and every Run2 artifact are excluded. Historical absolute paths are provenance, not portable execution paths. New execution on another machine needs fresh reviewed local paths, builds and receipts; do not launch or write inside this archive.
Remaining work
The reviewed native plan remains incomplete: narrower-window B/self-Call inspection, additional Text/exchange/definition membership, opaque Use/Open definition/Back camera and Details, drag refusal/cancellation and exact-coordinate spacing/history, C fallback/repair/reopen, typed service cumulative edits/refusal/history/reopen, broader lifecycle and measured-label usability. Service fixture admission is not a native typed-edit pass. Existing short32 label truncation remains. No issue closure, Linux result or feature-complete OA/SA release is claimed.