12 lines
2.6 KiB
Markdown
12 lines
2.6 KiB
Markdown
# Native multi-source semantic fixture
|
|
|
|
Validated source6 fixture: `semantic-batch.arcadia` and `.json`. Copy the source to a separate native working location before saving. Initial model: three DataTypes, two traces, no relationships. The first line is an exact source-comment preservation sentinel.
|
|
|
|
1. Open the fixture, choose Traceability, select **Normal range rationale**, then **Review semantics**. Normal operation limits maps to Controller admitted range. Select Integer Minimum, choose Set final value, enter `120`. Initial maximum100 makes this single-row proposal invalid; Apply must be disabled.
|
|
2. In **Choose another trace to add or reopen**, choose **Emergency range rationale**, then **Open row**. There must be two included rows, both targeting Controller admitted range. Select Integer Maximum, choose Set final value and enter `-`. The raw invalid input must remain visible and Apply disabled.
|
|
3. Optional exclusion/recovery falsifier before final repair: uncheck Include this row, switch to Normal via the retained-row picker and temporarily change minimum to `5`. One included row is now valid. Open the already retained Emergency row again; its `-` must remain and it must remain excluded, while the valid included preview remains available. Checkpoint/recover if exercising workflow recovery. Do not Apply this intermediate state. Return Normal minimum to `120`, reopen Emergency, include it and repair maximum to `150`.
|
|
4. With Normal minimum120 and Emergency maximum150 included, the single combined preview must become valid although Normal's independent raw group still retains base maximum100. Apply once. The shared target is exactly120..150 degrees; each trace records its own one-bound observation. Both source records stay0..100. One Undo restores all initial model/history/source; one Redo restores the exact after oracle.
|
|
5. Save/reopen and compare parsed Project with `semantic-batch.after.json`; compare exact saved source with `semantic-batch.after.arcadia`. The after-source file was produced by core `source_project::update_bundle` on the original source, not by reformatting the final Project. Check 1100x700 and1440x900 for retained-row picker, inclusion, property controls, error text and Apply visibility; right-side scrollers have18px gutters.
|
|
|
|
Exact trace IDs and target are in `semantic-batch.manifest.json`. `semantic-batch.request.json` is an independently constructed core request with two source reviews, one complete target candidate and zero additional impacts. `semantic-batch.hashes.json` records initial/after golden hashes. No native acceptance is claimed by fixture generation.
|