27 lines
3.8 KiB
Markdown
27 lines
3.8 KiB
Markdown
# Historical source checkpoint — 2026-09-12
|
|
|
|
Superseded historical record: its stop interpretation does not apply. The user's current instruction is to continue. See [saved verification checkpoint](handoff-usage-pause-20260912-final.md) for preserved evidence and Gitea for current coordination. Do not infer a live pause from the historical text below.
|
|
|
|
This record describes the earlier saved allocation source before its subsequent toolbar correction and combined verification. It does not impose a stop or resume condition. The separate Linux/WSL networking deferral remains applicable.
|
|
|
|
This is a saved handoff, not a replacement for live coordination in Gitea issue #3. Branch: `codex/behavior-authoring-20260910`; publication branch: `codex/release1-956atf`.
|
|
|
|
## Verified baseline
|
|
|
|
- `f52d81c1b96a34bb78b8ada27b7761dc0b009f5d` integrated allocation drag with guarded input and atomic history. The Windows focused run passed 54/54 tests, with all 525 build inputs matching Git before the run and unchanged afterward. Evidence remains in `.local/allocation-union-20260912/focused-f52d81c.{log,result.json,inputs.json}`. No combined full-suite, strict Clippy, GUI or native acceptance is claimed for that revision.
|
|
- `bc8bc4f5a1bf4a8cd53ad1829becd559ea536657` archived the older exact a31b40d Windows and bounded OA native evidence. See `release-behavior-canvas-a31b40d-native-20260911.md` and its linked archive. Those results apply to a31b40d, not the subsequent allocation changes.
|
|
|
|
## Work saved in this checkpoint — unverified
|
|
|
|
- Adapted the peer's saved-destination repair correction from `33c6d83e9ba9a5b1310b1b627d7c40affcbcf15c` into `document.rs`, the existing App paths, and five regression tests in `app/repair_save_state_tests.rs`. This binds or invalidates the saved baseline when an invalid destination is opened/recovered, preserving the accepted model and history. Tests have not run in this checkout.
|
|
- Updated the embedded guide, scope and language specification for allocation work dragging, atomic assignment and placement, draft preservation, and the one-gesture Arrange/Alt+A mode. `PROJECT_GOAL.md` was not changed.
|
|
- Interrupted the allocation worker during its correction for frozen performer labels covering the moving work's name/header. Its current changes in `allocation_drag.rs`, `allocation_drag/tests.rs`, and `app/allocation_drag_tests.rs` are saved as incomplete and unverified. Do not infer that requested full-tree coverage was completed.
|
|
|
|
The source review remains locally at `.local/allocation-repair-review-20260912.md`. Its remaining P2 reproducer places a work rectangle at approximately (120,110) under a frozen Receiver label at (110,131), 88 by 22: each fits the viewport, but the label obscures the work name. Resume by reviewing the interrupted admission rule and refusal feedback, then covering refusal plus a nearby usable drop under representative transforms. Refusal/release must preserve source, IDs and history exactly.
|
|
|
|
After reviewing the saved changes, run the combined Windows suite and strict Clippy against an identified commit, using `.local/run-allocation-gate.py` and the existing `.local/toolchain/env.ps1`. Serialize compiler work and record exact inputs. Resolve failures before claiming acceptance or publishing a release. Keep native usability gaps explicit. The source checkpoint is not a tested deliverable.
|
|
|
|
At the stop check, no `cargo`, `rustc`, or `arcadia-studio` process was running. All three delegated agents are stopped or completed.
|
|
|
|
Publication of this checkpoint was rejected because the remote publication branch contains newer work. A read-only verification found `codex/release1-956atf` at `97c91cc06c9a4880eeb5868b83973b6b983bff19`. The local checkpoint is preserved; no force push or integration was attempted during the requested stop. Inspect remote changes and ownership before reconciling on resume.
|