ARCADIA-Studio/harness/release-contextual-source-native-20260911.md

Contextual prerequisite creation — native Windows acceptance

Codex-9e8r6t /root, 2026-09-11. Resumed after the user's reboot. Machine Create/Save, Undo/Save and isolated post-reboot reopen passed; its Redo, broader cancellation/recovery and corrected-layout acceptance remain open.

Artifact and predetermined contract

Native input uses the immutable GUI 52DE82E434B636E18DB02D381842AA6DB84B721CFFD5502063F784F37246ACCE and matching F45604A1… libunwind in .local/native-qa/contextual-source-20260911-v1/bin. Its launch script checked all 238 frozen build inputs and both artifact hashes, created a fresh private profile and copied only the frozen fixture. PID 7212 launched normally; captured Home had no recent models. Actual window resizing produced a 1100×700 client. Open used the real file picker and the copied project. The source was subsequently committed/pushed in df6f595; later layout edits do not change this running artifact. Full earlier 675 versus final focused 23, guide 3, strict Clippy/build/formatting scopes remain in the implementation report.

The independent fixture and steps predate produced output. Unchanged oracle SHA256 967D9BA3C6FB3A7EFB410833903EC94556CA2D48A67D5072C8BB160F40A00F9C compares complete expected Project, reachable SourceBundle and physical files. Each original first-commit checkpoint separately supplies only fresh role UUIDs; prior-stage identities cannot be replaced by later output. The precise known-detached-file rule applies to Undo, without a broad orphan exemption.

Operational lifeline — Save adoption variant

At minimum size with both side panels, the empty Operational assessment scenario showed Add first lifeline. Entered Assessment lifeline, opened Create new source, retained explicit Activity and OA layer root, and entered Assess incident work. Use this new source returned to the parent, preserving the independent lifeline name and displaying the staged Activity. The accepted object count stayed at two at that observation.

Ctrl+S then applied the valid parent and saved the Activity and Lifeline together. The full Lifeline oracle passed all three source/disk files and every expected model field. One Undo/Save restored the exact original two-source model and three physical files, with only the explicitly proven retained activity file. One Redo/Save passed the complete Lifeline prediction using its original first-commit identities. No allocation, occurrence or diagram was created. This establishes the Save-adoption route; the direct Lifeline Create button was not used in this trial. The isolated UI/source histories are preserved under checkpoint-lifeline, checkpoint-lifeline-undo, checkpoint-lifeline-redo.

System chain — direct Create route

Switching to SA selected the empty System assessment chain and showed Add first function contribution. Entered Classify this request, opened source creation, retained Function and SA layer root, and entered Classify request. Child Use returned to the parent. A read-only disk check at that point still matched the original Lifeline stage exactly; no Save was invoked. Scrolling the parent revealed its retained contribution name. Create, then Save, passed the complete Chain prediction, four exact source/disk files, and all original earlier-stage identifiers. There is one Action under the existing chain, no sequence link, implicit allocation or lifeline. checkpoint-chain retains the first accepted result. One Undo/Save exactly restored the Lifeline model and three reachable files with only the proven retained Function file. One Redo/Save passed the complete Chain prediction and original Lifeline/Chain identities. The three chain checkpoints and individual exit/log records are retained.

System machine — direct creation and Undo before reboot

Entered Field team operating modes, opened Create new owner, explicitly chose System actor at the SA root and entered Field rescue team. Escape before Use returned to the unchanged parent machine name. Reopening the child started a fresh blank draft: unadopted child input is discarded, not retained. A read-only disk check still matched the Chain checkpoint. Reentered the explicit kind/name and chose Use; the parent showed the staged owner while accepted source files still matched Chain. Checked Create the first state view, then clicked Create and open and saved. The complete Machine oracle passed all six exact source/disk files and original role UUIDs: owner, machine, requested diagram and root placement, without regions or states. checkpoint-machine is immutable.

One Undo/Save restored the complete Chain model and its four reachable sources; the six physical files matched exactly, including only two proven retained files. checkpoint-machine-undo preserves this result. The user then requested a reboot. The GUI showed All changes saved and was closed normally; refreshed window inventory confirmed its absence at 13:38 UTC. The live work directory is the saved Undo state. In-memory history is no longer available: do not claim or try to infer a Redo pass after relaunch. Preserve the original machine checkpoint for an isolated reopen check and use a separate fresh trial for missing history coverage. Earlier Lifeline and Chain Redo passes remain valid.

The original GUI falsely showed Selected: Missing element in the accepted-owner picker despite the valid staged New owner summary. A reviewed display-only creation.rs correction is frozen with the source-card layout change; its build was interrupted for the reboot, and no corrected native pass is claimed.

Isolated post-reboot machine reopen

After the user resumed, root copied only the immutable first machine checkpoint into a fresh contextual-source-20260911-reopen2/work and used a fresh profile. The unchanged GUI52DE82 and F456 runtime hashes were checked before launch. The preceding reopen attempt reached only the Open picker before another user reboot and supplies no acceptance. Latest actual Windows boot was 13:59:33.500 UTC; the successful new app PID was5804.

The real Open picker loaded the isolated project. Selecting SA displayed the saved machine and first state view, owner and earlier Function/Chain. Ctrl+S reported all source files saved. The unchanged independent evaluator passed the complete Machine prediction using the original first Lifeline/Chain/Machine role carriers, followed by exact same-model/identity/six reachable and physical file comparison with the original machine checkpoint. There were zero retained detached files in this complete accepted state. This is persistence across a fresh process/profile after reboot, not a Redo or a corrected-layout pass.

The file picker returned a16×16 auxiliary screenshot before its actual1108×633 dialog capture. The first coordinate input was refused outside those auxiliary bounds; no model mutation resulted. An attempted UIA value operation was also unsupported. A fresh capture and the actual large screenshot then allowed ordinary filename click/type/Open. Both tool failures precede the successful native path and do not change the oracle expectations.

Raw launch records, screenshot, full/same oracle logs and result are in .local/native-qa/contextual-source-20260911-reopen2; the six saved source bytes are identical to the already archived first machine payloads. Exact preserved output and source mapping are now in postboot reopen evidence. The app closed normally and refreshed window inventory confirmed its absence.

Findings and corrected test assumptions

• The initial OA child form partly clips its focused Name field. Its roughly 130-pixel body places about 118 pixels of introductory content first. One ordinary scroll reveals Name and current semantic parent; both Back/Use stay pinned. The screenshot oa-source-open-clipped-name.png precedes any fix. The bounded layout review assigns an essentials-first correction without changing shared workspace geometry; this artifact is not its acceptance.
• The process parent puts its contribution name below existing-source search and empty paging controls. Ordinary scrolling finds it and its raw value is retained. This flow does not close user issue 2's consistent canvas requirement.
• The optional fixture instruction to Save a staged-only checkpoint was wrong. Existing App Save calls apply_behavior, apply_source, apply before disk save. Source inspection and native behavior agree. The fixture README/report correct the procedure, without changing any oracle model/source expectations.
• The first oracle launch had no sibling runtime DLL and exited before any oracle output. A read-only baseline repetition recorded loader exit -1073741515. The root checker now scopes PATH to the verified native bin and Windows directories and records every exit. The unchanged oracle then passed; no semantic failure was silently retried or relabeled as an environment failure.

Raw launch/check scripts live in .local/native-qa/; all images, checker logs, exit records, source checkpoints and the runtime-failure record are in the v1 directory. They remain distinct from the old scenario v5/D4D9 evidence and later layout artifacts. No Linux or final product acceptance is claimed.

The reboot checkpoint is now archived with exact readback in experiments/contextual-source-native-20260911. Its manifest maps 77 original records to 51 unique payloads, transparently deduplicating 35 physical source files to nine distinct byte sequences. Manifest SHA256 9a2ad6fb186606ef2a4fd1101d68c8e45bc96953093670fe9451ed9fb90a2ea6. Mutable work, profiles and binaries were excluded; original provenance is bound to the previously committed contextual-source archive.