# Contextual source native v2 — 2026-09-11

Codex-9e8r6t /root. Current trial follows the independently reviewed
[native plan](release-contextual-source-native-v2-plan-20260911.md).
The planned GUI5657 source-form cancellation/recovery, direct Lifeline history,
and fresh Machine owner/history/reopen scopes pass. This is one bounded native
slice; broader OA/SA workflow and release acceptance remain unfinished.

Prepared independent Lifeline and Machine work directories under
`.local/native-qa/contextual-source-20260911-v2`. The Lifeline starts from the
frozen two-file baseline; Machine starts from the exact four-file first Chain
Redo, with prior first Lifeline/Chain UUID carriers kept separate. All three
unchanged core-oracle preflight checks passed: self-check, complete baseline and
complete Chain. Preflight manifest SHA256:
`E340D2705D96691109F8CCFDA55AB8B401630558E6F4B5886B3A3CCFBE28A355`.

Private launch and checkpoint helpers refuse overwrite, verify oracle/runtime
and GUI manifest hashes, require successful build gates and scope private
profiles/runtime PATH. They preserve independent first/Undo/Redo/reopen source
directories and actual checker exits. The first preparation attempt stopped
before any oracle execution because Python's environment keys used uppercase
SYSTEMROOT; case-insensitive lookup was corrected and both already-copied
inputs were revalidated before the three successful checks. This was a helper
failure, with no native action or model edit.

The corrected source-layout gate now passes26 affected tests, including actual
Paragraph/content overflow and pinned-footer geometry. Strict Clippy, format and
matching GUI build also passed. Immutable GUI SHA256 is
`5657BAB5C841939B66F901EFE6C0FFB2D7CBBE8CC5F111A0CA3DE8073D3846CE`.
The actual native cancellation/recovery/Create/history trial remains separate.
Earlier GUI52 results are preserved in the
[v1 report](release-contextual-source-native-20260911.md).

## Initial native observations — 15:24 UTC

Initial PID5184 opened the exact Lifeline baseline through the real file picker.
Native window sizing reached1102x732 captured pixels, corresponding to the
1100x700 client minimum. Both normal side panels remained present. Corner drags
did not resize the window; the working native method was Alt+Space, S, Right,
then click the intended right edge, followed by Alt+Space, S, Down and a click
at the intended bottom edge. Each input used fresh observed state.

Add first lifeline retained raw parent `  Retain parent 雨  `. Create new source
opened at zero child scroll with Name, determined Activity, OA layer root and
Back/Use footer visible. Typed raw child `  Retain source Δ  ` remained independent
of the consumer. Maximize to2245x1232 and Restore to1102x732 retained both names;
the accepted status remained2 objects/0 links. Original screenshots are private
under `lifeline/runs/initial/child-minimum.png` and `child-wide.png`.

The completed recovery JSON was read and copied before stopping the isolated
process. Checker exit0 at15:24:08 UTC verifies the entire two-file accepted
baseline, unchanged workspace buffers, exact raw names, Activity/OA/root and
four distinct reserved version4 UUIDs. Snapshot SHA256:
`60f54695e7c16e5e63af7dba4a571dbd401975a65a54219b70e17d24df50f74e`.
No Use, Create or Save occurred. PID5184 was intentionally stopped only after
that proof; the matching binary relaunched as PID7928 with the same private
profile for recovery. Private helper/logs preserve the exact actions and check.

## Recovery and cancellation — completed

The real Home recovery entry restored an unsaved local copy with the child Name
focused. Completed post-restore JSON passed exit0 at15:27:13 UTC: the entire
accepted baseline and authored behavior payload exactly match the pre-stop
record, including both raw names and all four reserved identities. Its origin
is null; only the recovery envelope differs. Post-restore snapshot SHA256:
`a139c5783012efa8af61bb2f61dba33c2278f2d847855cc12e32ccd4df8fb1ca`.
The original recovery record remained separately present until later Save, so
the checker identifies the recovered local copy by null origin before comparing
the complete authored payload; it does not mistake timestamps for identity.

Escape dismissed only the child and retained the parent name. Reopening the
child showed a blank Name with Activity/OA root. Typed `Temporary cancelled activity`,
clicked Use, observed the staged New source and still2 accepted objects, then
explicitly cancelled the parent. Ctrl+Z reported **Nothing to undo**. Save As
wrote only afterward to a fresh `lifeline/cancelled-copy/project.arcadia`.
The unchanged independent oracle returned exit0: exact model/identity,
two reachable sources and exactly two disk files, with no retained extras.
PID7928 was then closed normally through Alt+F4 and confirmed absent. Its close
record makes no process-exit-code claim. Direct Lifeline creation/history and
fresh Machine acceptance remained subsequent independent trials at that point.

## Direct Lifeline creation and history — completed

Fresh PID9792 opened the untouched `lifeline/work` baseline from its explicit
Recent models entry, with clean history. At1440x900 client size, Add first
lifeline retained `Assessment lifeline`; Create new source staged root Activity
`Assess incident work`. Before Save the parent showed both independent names,
New Activity and2 accepted objects. Root clicked the actual parent **Create**;
the selected Lifeline, new Activity and4 accepted objects appeared before Save.

Save then passed the unchanged full Lifeline oracle with exactly three source
and disk files. One Ctrl+Z followed by Save passed exact baseline identity and
two reachable/three physical files, with only the proven original generated
file retained. One Ctrl+Y in that same live session followed by Save passed the
complete Lifeline oracle again using the immutable first commit's UUIDs. Each
checkpoint has its own copied source, actual log and exit0 result record. PID9792
then closed normally through Alt+F4; no native crash or process-exit-code claim.
This closes direct Create/Undo/Redo on GUI5657. Minimum-size source visibility
is the separate cancellation/recovery observation above; fresh Machine owner
visibility, Create/Undo/Redo and reopen were the remaining scope at that point.

## Machine owner, complete history and reopen — completed

Fresh PID1136 opened the independently checked old Chain input through the real
file picker. At1100x700 client size with both panels, SA New → State machine
retained `Field team operating modes`. Create new owner showed Name, explicit
**System** and **System actor** choices, SA root and Back/Use without scrolling.
Root typed `Field rescue team`, selected System actor and clicked Use. The
parent showed `New · System actor · Field rescue team`, both independent names
and6 accepted objects, without the former false Missing element caption.

Root opted into Create the first state view and clicked **Create and open**
before Save. The new owner, owned state machine and requested root view appeared;
no region or state was implicitly added. Save passed the unchanged complete
Machine oracle with six exact source/disk files. One Undo/Save passed the exact
old Chain model with four reachable/six physical files and only two proven
retained generated files. One Redo/Save in that same live session passed the
complete Machine oracle using the first commit's IDs. PID1136 closed normally.

Fresh PID3324 then opened `machine/work/project.arcadia` through the actual
file picker. Selecting SA displayed the saved machine and its state view.
Save passed both the complete Machine contract and exact equality to the Redo
checkpoint: six reachable files, six exact disk files, all original identities,
no unexplained retained file. This reopen ran at1440x900 client size; the owner
form and creation/history trial above used minimum size. PID3324 closed normally
and was observed absent. Logs, sources, screenshots and close records remain
separate from the old GUI52 trials and from the new Lifeline identity carriers.

## Full desktop regression gate

The same frozen source's immutable test executable
`75AB0E151D85473631D5A145527F3F6B9768A3CD61CE66A0603A574E09557017`
passed all679 tests, zero failed/ignored/filtered, exit0 at15:47:53 UTC. It used
one test thread, isolated profile/temp and the ordinary Windows stack. Execution
took576.67 seconds; no Cargo or native automation ran in that worker. The exact
[full-suite archive](experiments/contextual-source-layout-full-20260911/README.md)
is distinct from the native evidence above. Broader scenario canvas, SA B2,
peer integration and full-release acceptance remain separate; Linux is paused
until the user reports WSL networking resolved.