ARCADIA-Studio/harness/experiments/native-child-continuation-865483b-20260911/README.md

Packaged child-work native continuation — 865483b

This archive preserves the closed OA reopen and SA child-work continuation operated by root in the existing extracted Studio package. Source: 865483b4c66361a01fe0d9e731859220bafb4136; actual GUI SHA256 BF9C2E618D4A4AC55E6A7EBB3738736659FC35A6465522C7B5AB975238938808, PID 8680/window 5702564 in root's immutable record. The GUI remained live after saving; its live stdout/stderr, profile, working directories and binaries are excluded.

This is continued evidence for that old packaged GUI. It is not a new package, issue closure, complete native acceptance, or native evidence for canvas source a57c334. Root owns interpretation and later acceptance. The archiver performed read-only receipt/source inspection and physical-file/hash comparisons, without compiler, oracle, UI, WSL or Git/index actions.

Continuation and recovered attempts

Read child-native-continuation-complete.json for root's final transcription, preserving the earlier continuation-progress-20260911.json and native-open-pending-diagnostic.md as history. Their pending-reopen language describes earlier observation boundaries and is superseded only by the later confirmed actions.

Screenshots 24–30 preserve the first recovered OA picker, accidental unchanged rename selection, pending Working state and eventual Open cancelled. Filename 25-child-oa-reopened.jpg is historically misleading: it does not establish reopening. The two passing child-oa-reopened-1948 receipts and matching source snapshot prove existing saved data only while that picker was pending.

Root then used a fresh picker and observed the exact filename before Return. Screenshot 32 records the reported Source project opened state and screenshot 33 All source files saved after Ctrl+S. Both confirmed OA stage 3 and compare receipts exited 0. The full confirmed two-file snapshot (5,671 bytes) matches the original OA grandchild carrier.

For SA, screenshot 35 records the reported successful source-project open in the System allocated-work view. Root then used actual Create child work for first child, sibling and grandchild, saving each, undoing/saving and redoing/saving. The final reopen had a capture timeout and a filename attempt that did not appear; fresh selection/refocus and inspected retry recovered it. Screenshot 58 shows the entered filename, 59 the reported Source project opened, and 60 All source files saved. Its full two-file snapshot matches the original SA grandchild (3,827 bytes).

The immutable transcription distinguishes failed CacheRequest 0x80070057/set_value, rejected coordinates against stale 16×16 bounds, misleading focused-element metadata, and capture failures from completed App actions. No path was entered by those rejected operations. Cancellation completed the pending Open; these observations do not establish a deadlock or its hypothetical backend cause. No helper teardown or process kill was needed for this continuation. Native-observation claims above belong to root's recorded Computer actions, not a new archiver replay.

Closed receipts and exact source preservation

All 16 selected statuses are terminal exit 0, with nonempty completion times, empty stderr and exact corresponding PASS log text: 4 OA and 12 SA. They comprise seven model/source stage checks and nine checkpoint comparisons. The two OA file-only receipts retain that narrower scope; the later two confirm saved data after the accepted reopen.

SA stage 2 explicitly references the original child-sa-first; stage 3 and reopened stage 3 reference the original first and second checkpoints. Baseline stage 0 points to the then-unmodified working path; this archive does not copy that now-live directory. Instead, its immutable two-file baseline equals the SA entries in the original fixture manifest.

Readback of the actual SA source records confirms:

• Project c1140000-0000-4000-8000-000000000001, performer ...000a, parent work ...000b and original allocation ...0014 remain identified.
• First child e9348d74-3ae1-4bd4-8528-f72741b37031, sibling e2151fb4-287d-452c-995e-c742eff5e9fc, and grandchild ef40c66e-cb3e-4740-a916-d43cb45a1b60 retain their original creation identities through the pinned history.
• The original allocation keeps its ID, name, Unicode rationale, performer source and evidence ownership while its target moves parent → first child → grandchild. The sibling retains allocation 92debc9e-6247-4b0d-8750-ccf93db8bec1. The original evidence artifact still owns a reference to the original allocation.
• Original first/sibling/grandchild carriers contain respectively 2,665 / 3,323 / 3,827 bytes across two physical files. Existing closed oracles report complete valid model, exact source and pinned-history checks; no new parser/oracle execution is claimed.

Nine independent complete-directory comparisons passed, including exact filenames, sizes and SHA256:

Snapshot	Original comparison carrier
SA first Undo	SA baseline
SA first Redo	SA first
SA second Undo	SA first
SA second Redo	SA second
SA grandchild Undo	SA second
SA grandchild Redo	SA grandchild
SA reopened	SA grandchild
OA reopened-confirmed	OA grandchild
Historical OA reopened-1948	OA grandchild; data-only scope

Original OA first/second/grandchild carriers and earlier native/package provenance remain in the prior OA archive, already published with baseline 32334c6. They are linked rather than duplicated. Their current immutable carrier maps were independently compared with that prior archive and matched. The shared native contract remains the original checker; this archival comparison does not replace its model validation.

Frozen inventory and verification

111 byte-exact payloads, 3,762,865 bytes:

• 37 actual JPEG screenshots numbered 24–60, retaining exact filenames/extensions.
• 32 closed log/status files: 16 pairs.
• 12 checkpoint directories: 24 source files, plus all 12 adjacent checkpoint JSON receipts.
• Two SA baseline source files and one original fixture-baseline.json.
• Two immutable continuation records and the historical Open diagnostic.

The baseline manifest also describes other prepared fixtures. Only its SA baseline entries are used here; the other referenced fixture payloads are deliberately absent. All 12 checkpoint receipts match their complete two-file physical maps. No unexpected extra/missing files, failed status, carrier mismatch or copy discrepancy was found.

manifest.json freezes original paths, timestamps, sizes, original SHA256 and copied SHA256. verification.json records every status/argument scope, checkpoint receipt, nine full physical comparisons, original stage-carrier checks and prior OA carrier equality. readback.json independently rereads every original and copied payload against the frozen manifest: 111 matched, zero discrepancies. Relative mappings preserve the distinction between archived checkpoints and excluded original live paths.

Pending work remains as listed in root's completion record: wide/combining/emoji lifecycle headers, staged contextual-source workflows, packaged Home/Guide/normal-close checks and matching new canvas GUI acceptance. Linux/WSL remains user-paused.