ARCADIA-Studio/harness/prerelease37-human-checks-20260924

Prerelease 37: quick manual checks

Extract test-models.zip. The allocation and process folders each contain a complete project. Use a fresh writable copy of each supplied test folder and open its project.arcadia; keep the included subfolders together. Use a normal desktop-sized window. These are checks to perform on this prerelease, not a claim that physical Shift+click was covered by earlier automated native trials.

Allocation: select and move the whole group

1. Open Allocation group native, then 01 OA assign. Click X - receive, hold Shift and click Y - assess, then release Shift. Both cards should stay outlined and the selection strip should say 2 selected. Properties should show only the primary card, Y. Shift-click Y again to check removal, then add it again.
2. If Shift selection fails, record that failure. To continue checking movement separately, right-click the second card and choose Add to selection. This fallback does not make the Shift check pass.
3. Drag X (the selected nonprimary card) into C - destination, keeping the group inside C. Both X and Y should move together, their connection should follow, and both should now be assigned to C. Y should remain primary; feedback should describe assigning both work items.
4. Press Save all, then Ctrl+Z once: both cards and their assignments should return together. Press Ctrl+Y once: both should return to C together. Save, go Home, reopen this saved project from recent models, and confirm the saved result. Selection may clear and the view may refit after reopening.
5. Repeat steps 1–4 in 02 SA assign. Click the Function card bodies, avoiding the small ports. This manual SA reopen is a new check; earlier native evidence did not cover it.

Allocation: refuse the whole unsupported set

In a fresh 02 SA assign, select X, then add Y's small input port to the selection. Confirm 2 selected and that Properties identifies a Port, not Y's Function. Attempt to drag X. Nothing should move or become reassigned; feedback should tell you that ports/rows/connections cannot participate in this movement. It must not silently move only X. If the second item is the Function rather than the Port, correct the selection before judging the result.

Allocation: explicit Arrange and ordinary performers

1. Open 03 OA arrange. Select P - team and V - independent work. An ordinary drag should refuse this mixed selection and direct you to Arrange.
2. Choose Arrange (or Alt+A), then drag the selected nonprimary member downward into clear space while keeping the headers visible. P, its unselected child U - contained work, and V should move together. The arm should be consumed; feedback should describe 2 selected / 3 placements. U must remain assigned to P and V must remain unallocated: Arrange changes layout, not responsibility.
3. Check one Undo/Redo and Save/reopen as above. Repeat in 04 SA arrange.
4. In a fresh 01 OA assign, select the A - origin team and B - other team headers. Leave Arrange off. Drag A with B primary. Both performers, their contained X/Y cards and the connecting route should move together; X must stay assigned to A and Y to B. Check one Undo/Redo.

The Allocation fixture starts with 18 advisory model warnings about omitted behavior coverage, unallocated independent leaves and empty port payload contracts. They are expected; a new source error, crash or unexpected additional warning is not.

Process: reorder selected occurrences as one operation

Use the separate Process group native process folder included in test-models.zip.

1. Open its project.arcadia, choose Behavior & scenarios, then 01 OA group order. One column contains Card A, Card B, Card C; the other contains Downstream U/V.
2. Click C, then Shift-click A. Confirm exactly two selected; A is primary. Drag nonprimary C onto the lower half of Card B. The insertion feedback should mean After B.
3. On release, the first column should read B, A, C. A/C keep their original relative order despite reverse selection, and Downstream U/V remain in their column. A singleton move of C would leave A/B/C unchanged, so verify that A actually moved too.
4. Check one Ctrl+Z, one Ctrl+Y, Save, and reopen. Both selected occurrences must undo/redo together; connection guards and reusable Activity details must stay unchanged.
5. On a fresh copy, select a card from each column (for example A and Downstream U) and attempt a reorder. The whole set should refuse; it must not silently move an eligible subset. If desired, repeat the Shift-selection check using Add to selection only as the separately recorded fallback.

For a failure, record the diagram/process, exact selected items, primary item, drag start/drop target, feedback and whether one Undo recovered it. A screenshot before and after helps.

These are test inputs, not an application build. The combined prerelease must still open them and pass these checks. Earlier fixture acceptance does not establish the behavior of the new executable.