# Current Windows scenario acceptance — 2026-09-11

Codex-956atf `/root`. Source `3c9e6eeb64ce3efc03b29890b82199a42c21f335`
passes720/720 desktop tests and strict Clippy. The matching GUI built warning-free
in7m00s. **Native SA State, Reuse and Fragment creation, exact Undo/Redo and final
native reopen/Save pass.** Earlier completed
OA and SA Action evidence remains scoped to [immutable80cf197](release-scenario-native-20260911.md).

## Preserved entry state

The actual saved SA entry remains
`.local/native-qa/scenario-20260911/sa/project.arcadia`, SHA256
`3715C2511C79E2EED9609DE851105A5501439FF8A402B008FA282BAE260C1EA9`.
Root reran the unchanged independent checker in its Windows runtime environment:
`scenario-authoring-contract.exe check sa-action ENTRY`, exit0. The result covers
the entire model and two exact reachable source files. Checker SHA256 remains
`407318D5C7CAE6B237F261A21B0FDA55F6FEF655CB9DFCFA3153A7E372638498`.

Current private recovery id `30511014-b831-47e3-afd2-6c4e44835a8f` has64,935 bytes,
SHA256 `7282C424A13AF6553717450ABAA54E0E7C7CE3A6470638D0BCB650217ED9D43D`.
Its last write13:56:57 UTC precedes the13:57:52.500 boot. Recursive JSON comparison
with the earlier private reboot backup (SHA256
`5C7B90BE613AF35463C563B9AA85A7AB1F8D48561EA935ABC6FC1E79549DF0E8`)
finds exactly one changed path: `/modified`. All raw project/workspace/draft values
are identical. The different file hashes are not treated as an exact-byte match.

The Scenario Observation draft retains literal name **SA native state**, owner
SA A caller, Inner chosen operand and before-SA-Inner-anchor destination,
preselected inspector lifeline, and no selected State target. Before launching
the new GUI, root copied the
entire current recovery and SA directory into private
`.local/native-qa/sa-resumption-3c9e6ee/`; its `pre-launch-record.json` records the
comparison. Original files and the earlier reboot backup were preserved.

## Actual native contract

Root followed the [fixed fixture procedure](fixtures/scenario-authoring/README.md)
without changing its checker, expected literal fields or insertion points. The
immutable executable has112,892,928 bytes and SHA256
`B69C840A019A9480DDB8D8BA50AB226BB2D80AE2EFE0BF92370DACD5DB1B31EA`.
Its adjacent190,464-byte runtime DLL has SHA256
`AA282FA47BB2C4E210CEA5E470CDBDCA58568F0BE0BC73E404D86AB9CD95EF6A`.
All513 recorded GUI inputs match Git3c9e6ee; the archived original GUI manifest
has SHA256 `A7D6B48D5F0F8AA4E64A3CEF614AD2E89C075491D32C135E934160A15EB36A2D`.

Studio's Home Recover action restored the raw name, destination and inspector
lifeline. Root observed the Name field visible and focused before and after
resizing to the1100x700 client minimum (1102x732 captured window). The retained
recovery screenshot itself is1442x932; the six later retained JPEGs are1102x732.
Automatic Name focus at minimum and on fresh Reuse/Fragment forms is a session
observation, not independently established by those seven stills alone.
Create remained disabled until **SA Ready** was selected.
Recovery starts an unsaved local copy with no old undo history; this is distinct
from the new creations' tested one-step history. Save As wrote a fresh `work`
directory, retaining the included rationale source and preserving the original SA
entry and private recovery backup.

| Creation | Native gesture and resulting contract | Saved/history result |
| --- | --- | --- |
| State | Recovered **SA native state**, **SA Ready**, **SA A inspector**, Inner chosen operand before Inner anchor |64 objects; check sa-state, Undo to exact pre-launch SA Action, Redo to exact saved State all PASS |
| Reuse | Clicked same inner operand before Inner anchor; **SA native reuse**, **SA B verification**, explicit B inspector to A inspector and B recorder to A recorder |65 objects; check sa-reuse, exact Undo to State and exact Redo to saved Reuse all PASS |
| Fragment | Clicked root gap before **SA Root exit**; **SA native alternative**, **ALT · alternatives**, guards `ticket.priority > 2` and `ticket.priority <= 2` |68 objects; fragment and two empty operands created atomically; check sa-fragment and exact one-step Undo/Redo all PASS |

Each checkpoint was checked against the entire Project and both reachable source
files, then preserved in its own directory. Every Undo was compared with the
previous verified snapshot; every Redo was compared with the original creation
snapshot, including all UUIDs and source bytes. The final project was reopened
through Studio's native Open dialog and saved again: check sa-fragment and exact
same against the original fragment checkpoint both pass. Final entry SHA256:
`9A547D958107C14F3A32FC4FFBF035CD8366F3CFAEEBA3232333A387FC68B486`.
The reopened UI showed68 objects and all changes saved. Root used the ordinary
window Close control; no matching Studio process remained on subsequent inspection.
Numeric GUI exit status was not captured.

## Observed UI behavior and limits

New Reuse and Fragment forms reset to a visible, automatically focused Name field
after the previous form had been scrolled to its bottom. The pending insertion
marker and root-before-exit destination were visible for Fragment. State's pending
marker required ordinary canvas scrolling after window resize; automatic reveal
under resize is not claimed. Controls and guard fields were reachable at minimum
size using Focus canvas, the Tools toggle and form scrolling. I1/I2 nested child
focus/return and the remaining broader canvas manipulation matrix have not been
accepted by this native sequence.

The first Save As accessibility set_value attempt failed with a cache-property
error; refreshed coordinate/focus input completed it. An initial select-all chord
did not select the path; the appended draft path was corrected and visually
verified before saving. At final Open, screenshot index0 was a16x16 transient;
the coordinate input was rejected before dispatch. A fresh capture identified the
1108x633 dialog at index1, and its visible project row was opened successfully.
These failed automation attempts were not counted as successful application steps.

## Durable evidence

[Archive manifest](experiments/scenario-native-3c9e6ee-20260911/manifest.json)
records50 payloads /999,009 bytes: seven original JPEGs,17 oracle/history logs,
23 fixture/checkpoint files and three GUI build/provenance files. Original and
copied hashes/sizes matched, then every archived file and the exact inventory
were independently read back. Manifest SHA256:
`D283F240FF685AF66E76B3264081995400CFC07CDB8C1639B467CBAC8D9BABE8`.
The archived GUI build manifest retains its original pre-launch `Pending` label;
the later native results in this report supersede that historical status.
Executables and raw recovery remain private under `.local`; the archived synthetic
model/checkpoints retain their original bytes. This is scoped native GUI-to-model
and source/history evidence, not independent proof of the shared language engine
or full release/product acceptance.

All Linux/WSL builds and checks remain deferred until the user explicitly resumes
them. The isolated canvas and codec candidates are outside this native build.