ARCADIA-Studio/harness/fixtures/release1-native/semantic-ordered.steps.md

Ordered semantic native fixtures

Open semantic-ordered.arcadia for the main OA→SA case. One trace is ready: "Startup sequence order review" (alias startup_order_review). Other validated variants use the same instructions:

• semantic-ordered-reverse.arcadia: "Reverse startup sequence order review", SA→OA.
• semantic-ordered-scenario.arcadia: "Startup scenario order review".
• semantic-ordered-branch-steps.arcadia: "Startup branch steps order review".
• semantic-ordered-fragment.arcadia: "Startup fragment branches order review". The fragment variant uses Fragment branches in Members / rows; all others use Ordered steps. In reverse, substitute Operational for destination/System for source.

Exact main flow

1. Open the trace from Traceability with Review semantics. Direction Operational to System. Reference pairs should include these three explicit OA→SA rows: OA Request start → SA Request start OA Energize → SA Energize OA Verify interlock → SA Verify interlock The trace endpoints are already paired; names do not infer the three step pairs. Use Reference pairs to add them by their named picker choices.
2. In Properties select the paired Steps member for Verify interlock (enable Show unchanged if necessary). It has pre-recorded exact paired history. Alternatively choose Members / rows → Ordered steps, choose OA Verify interlock and SA Verify interlock, then Use these addresses and review row. Click Take Operational.
3. Expect "Ordered member insertion has no unique unchanged anchor" and disabled Apply. Source order is Request start, Verify interlock, Energize. Destination order is Request start, Local self-test, Energize. The local step prevents a uniquely anchored insertion; accepted source/project/history stay initial.
4. In Members / rows choose Review final order… (or select the Order Steps fact), then Set final value. Initial draft: Request start, Local self-test, Energize, Verify interlock. Press Up on Verify interlock once. Final draft: Request start, Local self-test, Verify interlock, Energize.
5. Preview must succeed with zero Additional changes. Apply once. Compare accepted project with semantic-ordered.after-order.json and single-file source with semantic-ordered.after-order.arcadia. Only selected membership/order and its typed review history change. One Undo restores the initial project/source; Redo restores after-order. Save/reopen preserves the exact leading comment.

Rejected retained-draft/recovery check

Before Apply, keep the explicit order Candidate selected but leave the Verify member decision unselected. The saved order still contains Verify, which is no longer in the proposed membership. Expect an exact-survivor error; the authored order must remain visible. Changing tabs and recovering the workflow must retain that rejected order. Re-select Take Operational for Verify: the original final order becomes valid again without editing it. Reconcile with selected membership is the explicit alternative that removes excluded entries and appends newly included entries; it must never happen merely on Refresh or leaving a tab.

At 1100x700 inspect the full scrollable order list and Up/Down controls, error, Apply/Cancel and exact preview observations. Repeat at 1440x900, then reverse and at least the Fragment branches variant.

Artifacts and validation

Each stem has initial .arcadia/.json, .after-order.arcadia/.json, ambiguous request and error, final request and plan, plus a manifest with exact IDs. Source oracles use production source_project::update_bundle so the leading comment and unchanged declarations retain exact bytes. semantic-ordered.validation.txt records all five fixtures: both initial and final models validate, production source/JSON decode round trips are exact, ambiguous Take rejects, successful final plan has 0 impacts. Generator output and binaries stay under this ignored directory; no Cargo or shared target output was used.

Minimum-width application navigation recheck

The previous top page row hid Model checks and Engineering guide behind horizontal scrolling at 1100x700. The source now wraps the existing page buttons. In a newly built binary, resize 1440x900→1100x700: all nine labels/actions must stay visible, with a second row as needed. Select Model checks and Engineering guide; ensure content remains usable below the taller header. Resize back to 1440x900 and verify buttons return to available space while selected-page styling remains correct.