Add named behavior creation and verified textual authoring examples

harness/release-palette-native-20260910.md

@@ -166,3 +166,62 @@ The subsequent process query found process 648 absent; stderr was empty. Root
 transferred the exclusive native-input lease to the independent Capella creation
 workflow investigator. A future current-build session can resume from the whole
 `checkpoint-actor` directory without redoing earlier accepted fixture creation.
+
+## Candidate 3: complete basic model and counterpart persistence
+
+Root resumed on 2026-09-10/11 with the whole Actor checkpoint in
+`.local/native-qa/palette-20260910-v3/resume-actor`. Executable SHA256
+`9BA479FB3B6DF2139E77D992396CEB0108EE039A916F694AB3BD19F54677FBE6`,
+process9312, isolated profile and runtime inputs in the stage's `process.json`.
+This binary includes the earlier scenario workspace but predates its corrected
+Sensor identity; it is not accepted for current scenario behavior or creation.
+
+At 1442×932 outer size, ordinary Activity tool → chosen point → focused name
+`Assess incident` → Enter created the root Activity at the clicked location.
+The canvas origin remained stable through the naming phases. Its independently
+required placement was explicitly set to (160,300), size224×94. The complete
+four-source intermediate bundle is retained as `checkpoint-activity`.
+
+Add existing showed only the compatible unplaced `Report status`; the unrelated
+SA Function and OA Capability were absent. Including already shown elements
+offered three Locate actions and one Add. The existing activity retained its
+seed UUID and was explicitly placed at (680,300). The interrupted earlier click
+had not placed it; a fresh observation established that before root continued.
+
+An explicit relationship form created Allocation `Performs`, Rescue team →
+Assess incident. The diagram then visibly nested the work beneath its performer,
+without changing the activity's semantic parent. The Interaction palette gesture
+connected Assess incident → Report status. F2 changed the activity display name
+to `Assess rescue incident`; its alias and the original authored Interaction
+name remained unchanged. Save passed the unchanged independent checker:
+**complete basic model and all four exact SourceBundle files**. The expected
+model adopted only fresh UUIDs proven through literal roles, never geometry or
+other observed metadata. `checkpoint-basic` and `basic-check.log` retain evidence.
+
+The native transition explicitly selected **System actor**, **Selected only**,
+and **System rescue architecture**. Apply opened that Allocation view, selected
+the new SystemActor, and retained the OA source. Its placement (60,60),224×94,
+typed trace, both decoy views and every source field matched the independent
+transition contract. The incompatible StateMachine destination was absent;
+Capabilities remained a legitimate but unchosen destination, visibly described
+as not an allocation view. **Complete transition model and six exact sources
+passed**, preserved as `checkpoint-transition` and `transition-check.log`.
+
+One Ctrl+Z followed by Save passed the complete four-source basic oracle;
+one Ctrl+Y followed by Save passed the six-source transition oracle. Distinct
+`checkpoint-transition-undo` and `checkpoint-transition-redo` copies and logs
+preserve those boundaries. Reopening the actual entry through the file picker
+succeeded. Reopening counterpart creation then displayed `Rescue team · SA`
+and `Reuse · Rescue team`, with review wording instead of a new counterpart.
+Cancel and Save passed the transition oracle again. All six physical files
+matched the pre-reopen snapshot byte-for-byte, including stable identities;
+`transition-reopen-bytes.json`, `transition-reopen-check.log` and
+`checkpoint-transition-reopen` retain that evidence. A durable wide OA image is
+`basic-reopened-oa.png`.
+
+This closes the declared main model/transition/history/reopen sequence at wide
+size. It does not close the supplementary meaningful-move/pan/zoom, invalid raw
+draft, minimum-size, allocated-work and recovered-focus matrix. An attempted
+border drag and native Size command did not visibly resize candidate3; no new
+minimum-window pass is claimed. Earlier candidate1/2 observations remain scoped
+to those executables. The app remains open pending the next verified GUI stage.