4.2 KiB
R6 data contracts — native verification in progress
R6 is not accepted. Main remains at a8f451e. The full first-release goal remains
active and incomplete. User explicitly reauthorized native testing after Escape.
Frozen production and automated evidence
Data integration ab661f2: Windows607 and Linux610 workspace tests pass, one explicit
benchmark ignored each; strict workspace all-target Clippy passes on both.
Windows261 desktop tests include the focused bounded scenario editor; Linux release
desktop/server build passed. Logs under D:/CodexBuilds/Capella2-release1-01a06e2e:
r6-workspace-windows-ab661f2.log and r6-workspace-windows-clippy-ab661f2.log.
Linux logs in Capella2-data-linux-review/target/linux-verification:
workspace-ab661f2.log, workspace-clippy-ab661f2.log, release-ab661f2.log.
Windows frozen executable ui-r6-windows/arcadia-studio.exe SHA256 C3ABD9E550E1AD6824DFE273EB27A3ABB35C5C0DA97C819DCB0AB2586AF5450C. Current native window1835476, process session37598. No output observed; runtime.log has not been created by Tee-Object (do not claim an empty log file).
All4 actual R6 HTTP tests pass with strict server Clippy: published data example, protocol/artifact identity, rejected defaults, qualified reused/inherited/recursive Call/Reply paths, phase/path422 with unchanged ETag/model/source/disk, source edits, hop/terminal/base reidentification, correlation and restart persistence. Source3 coupled/source bundle migrations report correctly and opening alone does not write. Logs: r6-http-paths-final.log, r6-http-all-data.log, r6-http-paths-clippy.log. Initial fixture errors (untyped Port and transaction-error envelope assumption) were corrected before passing. Published example responses from server32033FFE passed served/local OpenAPI validation; obsolete shapes rejected. Strict reST HTML and81 OpenAPI schemas passed. One stale port compatibility paragraph was corrected.
Optimized empty inheritance chains250/500/1000: Windows21.070/89.088/391.590ms; Linux22.381/111.662/408.129ms. Single-run core validation timings, not UI latency.
Personally observed Windows native workflows
Loaded the isolated Engineering data source fixture. Its architecture view shows nested fields, association role/multiplicity labels, self-reference navigation and selectable endpoint labels. No selection-induced dirty state observed.
Voltage maximum48→12 with default24 rejects when navigating; entered12 survives, accepted summary remains0..48/default24, and a located default error is shown. Repair default→12 applies together; Undo restores both old values, Redo restores both new values. Created Cooling water with Material/Flow and contained Mass flow rate Real1..1, unit kg/s, explicit default0.0. Save All wrote an included sa/types.arcadia file with matching typed values, leaving13objects/4links/1 expected missing-System warning. Navigation allocation changed Synchronous→Asynchronous; Monitoring's separate Asynchronous/Read allocation is preserved. Removing Monitoring allocation keeps Navigate; Undo restores the allocation and original checks. Followed inherited Latitude from Located asset to Coordinate. Saved all edits. Data layout inspected at1440x900 and1100x700; no overlapping controls observed.
Separate ui-r6-scenario-windows/model/project.arcadia was constructed with the core API from the saved native data, adding functional ports/exchange, correlated Call/Reply, reused/inherited/recursive records and30 extra fields.53objects/5links validate and source round-trip exactly. fixture-generator.rs retained as evidence; temporary project example removed. Initial generator compile/load errors were fixture-only and fixed using the bundle-aware loader; final build has no warnings. This preparation is not native scenario authoring evidence.
Remaining acceptance gates
Native scenario focused/path/phase/draft behavior and paging; actual saved reopen; source3 migration diagnostics; Linux native data/scenario workflows. Closure of material findings before R6 acceptance. Independent semantic/correctness/spec reviews already drove fixes; final native observations may require further review. The broader release still needs semantic reconciliation, direct scenario/process editing, lifecycle/hosted/help work and fresh cross-disciplinary end-state review.