Document integrated prerelease source handoff and human checks

docs/preview-human-checks.md

@@ -0,0 +1,55 @@
+# Testing the integrated Windows preview
+
+Extract the complete published ZIP and run `arcadia-studio.exe`, keeping its DLL
+beside it. Copy a complete example folder before editing, including all source
+includes and evidence files. When reporting a problem, include the preview
+version, example and steps that reproduce it. These checks describe expected
+behavior; the release's VALIDATION document records what was actually verified.
+
+1. **Text and diagrams together.** Select a source block and use Tab/Shift+Tab,
+   then source Undo/Redo. Apply, return to a saved graphical view, move a
+   placement, Save all and reopen. Both accepted edits should persist. In a
+   Scenario view, choose S/Select and 100% before dragging a lifeline header.
+2. **Scenario arrangements.** Rename one saved arrangement in Properties,
+   switch to another, and check that its name and layout remain independent.
+   Select a call and switch arrangements: that call should remain selected when
+   both contain it. Return through Details to the intended editable properties.
+3. **Draft recovery.** Change a service-call value without applying it, switch
+   Properties to Connections and back, and confirm the draft remains. Revert
+   should restore the accepted value. Incompatible operation/field choices
+   should explain the problem and retain the draft. Check that Apply/Revert
+   remain reachable after resizing the window.
+4. **Attachments, bends and ports.** Move an ordinary edge attachment, add and
+   move a State bend, and move an SA semantic port. Check Undo/Redo and reopen.
+   A second saved view should remain independent, and endpoint identities should
+   not change merely because their presentation moved.
+5. **Multiple selection.** In ordinary and State diagrams select a group, move
+   it, and use Undo/Redo. In Process views reorder supported sibling cards and
+   inspect exact reused occurrences with Open/Back. In Allocation views exercise
+   group assignment and explicit Arrange; an unsupported mixed selection should
+   be refused as a whole. Aggregate semantic deletion remains unavailable.
+6. **Direct Allocation drawing.** Choose Allocation, click a performer and a
+   highlighted unallocated leaf activity/function. Check the intended relation
+   and nesting, then Undo/Redo. An occupied or incompatible target should be
+   refused; Escape should cancel the pending drawing action.
+7. **Traceability.** Open a mixed OA/SA Traceability view, use Add existing
+   elements and place both ends of a correspondence. The selected mixed view
+   should remain active. Review layer traces for correspondences whose endpoints
+   are not represented as cards in that view.
+8. **Counterpart review.** Explicitly choose an existing counterpart and inspect
+   its Name/Description conflicts. Keep target should preserve the target's
+   engineering text. Scroll the review in a shorter window: counts, unresolved
+   guidance and Apply/Cancel should remain reachable. Cancel once, repeat and
+   Apply, then Save/reopen. An unchanged subsequent Apply should not duplicate
+   the target or its trace.
+9. **Picker Escape and Text navigation.** Open a picker inside a pending form:
+   the first Escape should close the picker and retain the form. A subsequent
+   Escape should follow the form's ordinary cancellation behavior. Also exercise
+   source declaration/reference navigation, Back, Find and alias-rename preview;
+   cancel once before confirming a rename on the copied example.
+
+Inspect the known limitations in the release notes. In particular, crossed
+Process routes and multiline State labels can be crowded. Report these as visual
+readability problems even if the saved connection records remain correct. This
+preview does not imply complete OA/SA, source8 or accessibility acceptance.
+Linux builds remain deferred at the user's request.

docs/windows-packaging.md

@@ -2,6 +2,10 @@
 
 The standard build target is x86_64 MSVC. The optional gnullvm build uses LLVM-MinGW UCRT and currently needs `libunwind.dll` alongside both executables. Packaging is a separate operation on already-built inputs; it neither builds nor launches applications and does not confer release acceptance.
 
+For feature checks after extracting the integrated preview, use the
+[human testing checklist](preview-human-checks.md) alongside the release's exact
+validation record and known limitations.
+
 Run from a Git checkout with Windows PowerShell 5.1 or PowerShell 7 and Python 3.11+ (standard library only). Build and test first using the [README](../README.md). Select the actual output directory explicitly; a native-host Cargo build normally uses `target/release`, while an explicit `--target` uses `target/<target>/release`. `-Python <executable>` selects Python when it is not named `python` on PATH; it collects/checks the package-local documentation closure without running binaries.
 
 Packaging also needs the build's matching `cargo` and `rustc` on the packaging process PATH, the locked dependency sources/archive cache, and installed Rust target libraries and copyright reports. The script invokes only read-only `cargo metadata --locked --offline --filter-platform <target>` and Rust version/sysroot queries. It does not download dependencies or build. These tools are packaging prerequisites; the extracted application does not require them.