Record user pause and exact Windows acceptance handoff

harness/release-user-pause-20260911.md

@@ -0,0 +1,39 @@
+# User-requested pause — 2026-09-11
+
+Codex-956atf `/root`. The user requested: “Save your work and stop. The usage limit approaching.” Work is paused, not complete. Resume only when the user requests it. Linux/WSL setup, networking, builds and checks remain paused separately; do not inspect or change the VPN.
+
+## Verified source and Windows gates
+
+Root branch `codex/behavior-authoring-20260910`, source `a31b40d0f8551ed87c8cd66250b9afb4809b3a79`, already normal-pushed with exact readback to `codex/release1-956atf`. This source removes obsolete behavior-canvas paths after the canvas union. Independent exact-file review found no actionable cleanup regression.
+
+Actual Windows gates passed: all 729 desktop tests, strict all-target desktop Clippy with `-D warnings`, and the GUI build. All 518 build/test inputs matched the source commit before and remained unchanged after each gate. Exact local receipts are `.local/canvas-union-20260911/{full,clippy,gui}-a31b40d.{log,result.json,inputs.json}`. These newer receipts have not yet been archived into versioned harness evidence; the older published report is historical evidence for earlier source.
+
+The pinned GUI is `.local/native-qa/studio-a31b40d/arcadia-studio.exe`, 113005056 bytes, SHA256 `89F9746C42888E189EA58723A0E64C8AF610D97C6E73D1F31828FCD94DAE8023`. Its adjacent manifest preserves the source, gate results and DLL identity. Do not rebuild over this artifact.
+
+## Native acceptance actually completed
+
+Private trial `.local/native-qa/canvas-20260911`, working scenario directory `scenario`. Native screenshots and observations are under `evidence`; preserve them and the entire `checkpoints` directory. The independent checker is `.local/native-qa/scenario-authoring-contract.exe`, SHA256 `407318D5C7CAE6B237F261A21B0FDA55F6FEF655CB9DFCFA3153A7E372638498`. `.local/canvas-checkpoint.py` preserves complete source directories and records oracle commands/results, refusing snapshot overwrites.
+
+At the enforced 1100×700 client minimum, the actual GUI completed all four prescribed OA creations: action before Root entry, state before Inner anchor in the nested chosen operand, reuse at that same operand with both explicit lifeline bindings, and an ALT fragment before Root exit with both specified guards. For each creation, Save and the full-model/two-source checkpoint passed. One Undo/Save restored the exact preceding verified Project and SourceBundle; one Redo/Save restored the exact original created identities and source bytes. The fragment and its two operands were one history step.
+
+Preserved checkpoint names are `oa-{action,state,reuse,fragment}-{saved,undone,redone}`. Each matching `evidence/*-check.json` contains actual results. The final fragment source SHA256 is `335347B279FA8CBD1BC74B0DB83644C47F05B47547E508A80412D4430EF21A7C`; the unchanged included rationale SHA256 is `82DF210F22F6AA336A3E7E00240977D671C7C3923DB7BC58FB29E6D98B67EF49`.
+
+Observed native camera/control behavior includes Fit, Tab after Fit, F6 and arrow panning, blank-area drag panning, and all 13 palette tools fitting the actual minimum window. Forms kept their clicked destination and initially focused Name. The completed fragment draft survived Escape with both guards and destination intact. Clicking Details while a pending action form was open preserved that form and did not open Details. Do not claim that unfocused wheel input panned; it did not, and focused wheel zoom still needs native verification. Do not claim palette overflow below the actual supported minimum or physical held-middle/Space gestures.
+
+**Reopen remains unverified.** The user stopped Computer Use with the physical Escape key during the final Open-dialog double-click. The input outcome is unknown. No further Computer Use was attempted. Last known pinned process was PID 8476, main window 12977206 and Open dialog 75760724; these are historical identifiers, not proof of current liveness. Re-observe if native work is explicitly resumed. Source-child recovery/cancel, process editing, caller return, reorder refusal, and current SA native acceptance also remain unfinished. Earlier SA native results apply only to their earlier identified build.
+
+## Isolated allocation-drag contribution
+
+Worktree `.local/allocation-drag-worktree-20260911`, branch `codex/allocation-drag-956atf-20260911`, base `abffa4b3f0a859d7439103100f59805804d46e55`. Root saved all 19 changed files in local WIP commit `81a879d72b087040ca69f24a170329f929385745`; the worktree is clean. This isolated WIP commit is not integrated or remotely published. Integrate shared-file changes as focused hunks, not whole-file replacements over newer root/peer code.
+
+Pure planner SHA256 `761921A1DD608873DDECFBC138685D40A1F557BC3B619E02D90231E13814B433`, 29-test source SHA256 `8910C8F0867734C1C615E799352515020D1AE5C62181184B7410BCAFC0094BE7`. Root's warnings-denied direct-rustc probe compiled and all 29 planner tests passed; 17 unrelated Document tests were filtered. Exact frozen inputs/dependencies, compile/test logs and results are `.local/allocation-drag-probe-20260911/reviewed-29`. This is component evidence, not UI integration acceptance.
+
+The initial UI handoff is the isolated `harness/release-allocation-drag-ui-source-20260911.md` (initial hash `44EF55FB0603FBEF792AB78589E84BD44ADD015C4BB4BFC209DF555A6D574F61`, 13 Rust files and 19 unexecuted tests). Independent review `.local/allocation-drag-ui-review-20260911.md` found three P2 issues: dirty work presses still unfocus real inspector widgets through Iced sibling dispatch; Arrange next drag lacks keyboard activation; the feedback band can obscure candidate headers or overlap target labels. Root assigned repairs in the isolated worktree, then instructed the worker to stop and preserve partial work when the user requested this pause. The worker has stopped. No allocation UI compiler/native pass is claimed.
+
+Worker's final partial-repair report: `allocation_input.rs` wraps the actual views root to reject dirty Allocation object presses before sibling dispatch, using the measured canvas container ID; it also handles discoverable Alt+A and armed Escape. Status feedback moved into the existing clipped toolbar hint row outside the canvas, removing the 42-pixel hit exclusion. There are now 21 packet/App test sources plus 4 actual-App-tree tests for Name/Description continued typing, keyboard arming/cancellation/refusal and canvas pixel independence from toolbar feedback. Latest test additions are unformatted and unexecuted. Production repair files passed scoped rustfmt parsing before those test additions, according to the worker; root has not verified the repairs. Original reviewed sources and handoff are retained in the isolated `.local/allocation-drag-ui-before-review-20260911/` directory. Re-review the actual WIP diff and run the required checks on resume; the original handoff hashes describe pre-repair sources.
+
+## Continuation
+
+The previous goal turn made concrete progress through native acceptance and independent review. The full user goal remains open. Focused Gitea issues are authoritative for live coordination: #2 canvas, #3 allocation drag, #4 peer child-work, #5 peer integration/release, #6 source navigation, #7 analysis/source/API and #8 maintained libraries. Read newer issue comments, relevant Wiki pages and actual default-branch instructions before resuming. Peer #5 owns the pending lifecycle/child-work preview release; avoid duplicate release ownership.
+
+First preserve/publish the exact newer gate and native evidence, reconcile the isolated repair handoff, then continue review/integration and appropriate Windows verification. Current native acceptance and broader Capella semantics/ergonomics, persistent process/scenario layout, analysis/source/API parity, libraries and full release verification are not complete. Preserve user-owned `PROJECT_GOAL.md` exactly.