Files
ARCADIA-Studio/harness/experiments/drag-out-20260925/README.md
T

75 lines
4.4 KiB
Markdown

# Outgoing allocation drag evidence
Contribution source: `1a669130fb6d2b65279aab3847e966a1a282c191`, based on
published preview `715036e132677dd2bc2fb37ed316d93dc9987aec`.
This is branch-specific Windows evidence for [issue 40](http://217.177.34.108:3000/sorokin.oleg.edu/ARCADIA-Studio/issues/40).
It is not acceptance of an integrated release or the complete application.
The [decision and native baseline](../../drag-out-20260925.md) explain the repair.
## Environment and commands
Windows 10.0.26200, Rust/Cargo 1.98.1, host/target
`x86_64-pc-windows-gnullvm`, LLVM 22.1.8, LLVM-MinGW 20260908 UCRT linker
`clang.exe`, `CARGO_BUILD_JOBS=1`, `CARGO_INCREMENTAL=0`, default development
profile. Run at the identified source with the Windows GNU LLVM toolchain and
its linker/runtime available on PATH. A sparse checkout must include `build`
and `harness/fixtures` as well as crates. The actual commands were:
```powershell
cargo test --locked --offline -p oa-desktop allocation_drag -- --test-threads=1
cargo clippy --locked --offline -p oa-desktop --all-targets -- -D warnings
cargo build --locked --offline -p oa-desktop --bin arcadia-studio
```
Offline commands require dependencies already cached. A fresh environment must
fetch the locked dependencies first. Raw logs retain original absolute paths;
these paths identify this run, not required directories on another machine.
## Results and boundaries
- Test-only successor `24b1eab07d306d8cb091bb46f7daf9f027a8f1c0` adds two
OA/SA App regressions: a clearance proposal blocked by unrelated work and an
outgoing move with a retained sibling enlarging the source enclosure.
`tests-04.log` passes all 123 allocation-drag tests (zero failed/ignored,
1,424 filtered) in 54.86s; `clippy-02.log` passes the same strict command in
1m27s. Production inputs are unchanged from `1a669130`; its normal binary
remains the native candidate. [Independent review](independent-review.md)
covers the source, new test design and evidence limits.
- `tests-03.log`: 121 passed, zero failed/ignored, 1,424 filtered; 35.33 seconds
test execution. This is the allocation-drag subset, not the full desktop suite.
- `clippy-01.log`: strict desktop all-target Clippy passed in 4m30s.
- `build-01.log`: normal GUI build passed in 5m16s. The resulting local executable
SHA256 is `9bda1a6a1d24fdc98c7a8822400c12fea9afe1de828a82ba9273f03b99e47c07`.
It was staged with the published preview's `libunwind.dll` and started, but
Computer Use was stopped before any changed-binary native observation.
- `context.json`: recorded source/toolchain, passing test-log and baseline-image
hashes, and clean source after the test run.
- `tests-01.log`: compilation failed before tests because `build/windows_manifest.rs`
was excluded from the initial sparse checkout.
- `tests-02.log`: compilation failed before tests because harness fixture files
were excluded and a standalone test helper used `Self` instead of `Fixture`.
The compiler was terminated after reporting errors; its interrupted exit is
preserved. The missing tracked files and typo were repaired before run 03.
The tests exercise source-clearance proposals, OA/SA App event sequences,
preview/release agreement, exact source/history, cancellation, and retained
preview without commit authority on refused release. Existing collision and
semantic checks still govern all proposals. Independent source review found the
whole-header viewport restriction and obsolete preview assertion; both were
corrected before the passing run. This is source/test review, not native review.
`baseline-left-refusal.png` is an unmodified actual native capture from the
published preview executable, SHA256
`2c03bd6cc3f1110c219e4f57ab94874a121590f83779239a93289b7170664399`.
In the copied Allocation companion fixture, OA assign view at 1440x900 content
and Fit 72%, dragging X from window (486,546) to (365,546) leaves allocation and
placement unchanged and reports overlap. A control drag to (625,572) removes
allocation, and Undo restores it. Intermediate jitter was diagnosed from source;
this image is end-state evidence only.
Changed-binary native acceptance is still required: repeat the short fitted-view
drag, identify and regrab the partially clipped card, check refused-motion
feedback, Cancel and Undo/Redo, save the full bundle, close and reopen in a fresh
process, and verify identity/allocation/placement and unchanged sibling data for
OA and SA. Linux/WSL remains deferred by the user. No published package changed.