Files
ARCADIA-Studio/harness/release-attachments-native-20260906.md

42 lines
2.5 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Recovered Child/Incident review — native Windows, 2026-09-06
The real Iced app at `.local/native-qa/bin-source6-recovery/arcadia-studio.exe`
(SHA256 `DD5D01FA07B921F1A7B365C33867876A7AE1BCBD01815B4BB4206408D2012F95`)
ran with isolated appdata and a system-only PATH. This executable includes
source-6 attachment review and checkpoint upgrade, but predates artifact lifecycle
controls and the later diagram-inspector selection correction.
Using the tracked `fixtures/release1-native/semantic-attachments.arcadia` fixture,
the Startup ownership rationale row paired the two Verify interlock children and
set the SA child's Parent to SA Safety coordination. A second included row,
Navigation endpoint rationale, paired the OA/SA Request response associations and
set only the SA association's Source to SA Validated navigation request. The
preview had two candidates and no impact approvals. The actual named pickers,
pair actions and candidate controls were usable at 1440×900 and 1100×700; the
detail pane scrolls normally. This is scoped evidence, not exhaustive layout QA.
The process was stopped with this unapplied two-row draft. Before/after snapshots
are `.local/native-qa/attachments-before-crash.json` and
`attachments-after-recovery.json`. Home Recover restored both included rows and
all four explicit reference identities. Structural comparisons found both the
raw workflow and accepted project unchanged. The recovered active trace picker
showed the actual Navigation endpoint rationale name and alias, verifying the
previous stale/deleted-label correction.
Apply reviewed changes was clicked once. The visible tree placed SA Verify
interlock below SA Safety coordination; checks decreased from 17 to 15. Save As
to `.local/native-qa/source6-attachments-result.arcadia` succeeded first attempt
and matched the complete independent `.after.arcadia` oracle byte for byte:
`9D084DD75A0251D349CC31F9EE98DF58D0BC76859DC3CB1503F242E2F759888A`.
One Ctrl+Z and Save restored the entire original source exactly:
`8740F27BE99624013D9BE876639C0411E1B8C14F0F9A843F43DC71D769EFD79A`.
One Ctrl+Shift+Z and Save restored the exact after hash above. All three saves
succeeded on the first attempt. No recovery JSON remained (only recent-models
metadata), and the saved app then closed cleanly.
Invalid raw attachment identities and competing direct Keep decisions are covered
by automated tests; they were not entered during this native run. Artifact
creation/deletion/move, other semantic facet families and Linux acceptance remain
separate gates.