ARCADIA-Studio/harness/release-artifacts-native-20260906.md

Artifact lifecycle native evidence — 2026-09-06

Move, optional metadata, conflict and crash recovery

Actual Iced Windows GUI SHA256 AB6ECD62DB02FF3D81E2421EE1DDC926AEF72C65784DD288EAFA281836EC0597 ran from .local/native-qa/bin-source6-artifacts, with isolated appdata and system-only PATH. This executable predates the later conflict-message wording correction and Linux journal helper.

Opened semantic-artifacts-move.arcadia, reviewed Interlock requirement rationale, and explicitly paired the OA and SA Interlock requirement links. Both pickers displayed the actual link names, stable aliases and current Startup owners. Set final Owner to SA Safety coordination; independently set Revision to Present with empty text and Fragment to absent while retaining section-4 in its draft. Preview distinguished Empty text from Not set.

Keep System on Presence conflicted with the Owner move and disabled Apply. Leaving Presence unselected restored the valid preview. The initial error explained a conflict but exposed JSON UUIDs and inaccurately implied different review rows; this prompted a diagnostic-only correction and three passing focused tests in release-semantic-conflict-diagnostics-20260906.md. That wording is not yet native verified. No model was applied during the conflict.

At 1440×900 and minimum 1100×700, facet decisions, named owner picker, raw identity and optional toggles remained usable through normal detail-pane scrolling; action buttons remained outside the right scrollbar. Replaced Owner identity with -: the draft remained visible, the message requested a valid explicit owner and Apply was disabled.

Checkpoint 69352f76-e6ca-4e09-aaa7-7b4d94c5dccc was preserved as .local/native-qa/artifacts-move-before-crash.json, then process9060 was stopped. New process10192 Home Recover produced checkpoint 0b1898f0-4e64-4bec-b26d-c05697435a2b, copied to artifacts-move-after-recovery.json. Complete structural comparisons of accepted source and workflow were both equal, covering all three decisions, exact pairs, invalid Owner and retained optional text. Native inspection showed - still present and Apply blocked. Choosing SA Safety coordination repaired it.

Apply was clicked once; Save As to .local/native-qa/source6-artifacts-move-result.arcadia matched the complete independent after-source oracle exactly: 20BB30473830E44228958E78FB7480269CDCC0580C6C90C718DA75F34CA5A43F. One Undo and Save matched the pristine complete source: B0FD031671C9F755756922EC5C40A0CE3F40164D22C3C389AEC9FD0705344DA7. One Redo and Save matched the after hash again. All three saves succeeded first attempt, no recovery JSON remained and recovered-run stderr was empty.

Scope still outstanding

Creation with reserved identity and source-absence deletion have preserved fixtures and automated exact-oracle evidence, but are not yet native accepted. This report does not claim every artifact owner/type, large-list ergonomics, Linux application acceptance or post-correction diagnostic rendering.

Creation, exclusion, recovery and exact history

The same AB6ECD62 GUI reserved destination artifact a6f66451-0763-4e4d-a48a-7ee02aac71d1 from OA link f3635689-622e-4e71-849a-ec332f8931f3 under trace f27b20ea-1a66-4a91-87d6-79b7bda09a13. Presence alone blocked Apply until all seven metadata candidates were explicitly reviewed: Name, Description, Owner, Relation, URI, Revision and Fragment. Description retained CRLF; Revision was absent and Fragment was section-4. Eight decisions enabled Apply; excluding the only row retained the draft and disabled Apply.

Checkpoint450603eb-0275-416d-879d-4faaca089c8b was copied to .local/native-qa/artifacts-create-before-crash.json before controlled stop of process10192. An initial test relaunch mistakenly pointed LOCALAPPDATA at an empty sibling profile; no model input occurred there. After correcting both APPDATA and LOCALAPPDATA to .local/native-qa/appdata, process2540 Home Recover restored the review. New checkpoint07019cff-80f7-42e4-9081-bfae0f05c136 was copied to artifacts-create-after-recovery.json. Complete accepted and workflow structural comparisons were exact, including included=false, all eight decisions, seven drafts and the original reserved UUID. The UI visibly retained exclusion and disabled Apply.

Including the recovered row enabled Apply. One Apply followed by Save As .local/native-qa/source6-artifacts-create-result.arcadia matched the complete direct-core source oracle regenerated with the reserved UUID. One Undo/Save matched the complete initial source; one Redo/Save matched the complete after source. All three saves succeeded first attempt; zero recovery JSON files remained and stderr was empty.

• Initial/Undo SHA256: 1E0D662BA33071B122AD9206D2D559A8E748C9431EB3AC1B759BDE3760CA877C.
• Applied/Redo SHA256: 778C099F7CF3187B294E91F1717AB9836656DEEDB09AB6EF01DAEAC55CCD577E.

The full source equality covers model, artifact identity, metadata and review history; artifact count changes from one to two. The old binary still labels a reserved identity as Deleted reference in facet headings. Row-aware display corrections and independent review are recorded separately; they are not covered by this binary. Native deletion remains pending.

Source attachment absence and destination removal

Process2540 on the same AB6ECD62 binary opened semantic-artifacts-delete.arcadia. Traceability showed the OA link now under OA Safety coordination and the SA link still under SA Startup coordination. The explicit OA picker offered its existing identity with the current owner and wrapped 'not attached to reviewed owner' label after selection. The SA picker offered the exact existing destination identity. Staging the pair showed OA Presence No / SA Presence Yes. Take Operational changed the validated destination preview to No; one Apply removed only the destination link, leaving the OA card and its Safety owner visible.

Save As .local/native-qa/source6-artifacts-delete-result.arcadia matched the complete direct-core after source exactly. One Undo restored both cards and unreviewed trace, and Save matched the exact original. One Redo restored the removal/reviewed linked state and Save matched the exact after source. All three saves succeeded first attempt; recovery JSON count zero and stderr zero bytes.

• Applied/Redo SHA256: E50FC462EC22DBF98011929931DD2489430001C3E6433608685B9D88BCEB9ACB.
• Initial/Undo SHA256: EBA2AEC39E6EFB405EACE4BC8AB0C5563907C26D449E71A4AA750DF9F73233B4.

This closes the actual moved-source-attachment removal fixture, including all eight acknowledged facts in the exact history oracle. A no-source-identity destination-only row was not separately applied natively in this run; its retention remains covered by the automated artifact absence cases. Across MOVE/CREATE/DELETE, nine native saves passed first attempt. Earlier pending wording above is historical.