Explain R6 data authoring and record verification gaps

This commit is contained in:
2026-09-06 03:58:12 +03:00
parent 959b83c78f
commit 7426c03f4e
6 changed files with 63 additions and 28 deletions
+24 -14
View File
@@ -78,9 +78,11 @@ See release-data-implementation.md and release-data-contract.md in that checkout
Core is committed0b58107; source/migration1230ab8. Root API/docs are integrated
on the same working tree; desktop remains in flight and R6 is not accepted.
Core15 R6 +28workflow tests passed (final allocation-arrow suppression arrived
afterward and is queued for rerun). Earlier13ports/14scenarios and115 source/lib
tests passed; strict core Clippy preceded the last geometry/performance fixes.
Core15 R6 +28workflow tests passed again after final allocation-arrow suppression.
Linux0b58107 full core307 tests passed (one explicit probe ignored by default),
with strict all-target core Clippy. Earlier13ports/14scenarios and115 source/lib
tests also passed. Desktop final257 tests and strict all-target Clippy pass;
the optimized Windows desktop build is in progress for native acceptance.
Root41 server tests pass, including3 new actual HTTP workflows for the published
data example, protocol/artifact identity, atomic rejected defaults, query/export,
@@ -95,20 +97,28 @@ Evidence: api-r6-contract and r6-server-tests-after.log under the release direct
Independent core review found association transition closure pulling unrelated
types and missing empty-enum warning; both corrected and focused tests passed.
Repeated per-ancestor full scans were simplified to one scan per helper call.
Explicit debug inheritance timings250/500/1000:147/664/2739ms. Optimized timing is
still required; no optimized performance claim yet.
Explicit optimized inheritance timings250/500/1000: Windows21.070/89.088/391.590ms,
Linux22.381/111.662/408.129ms. These single-run empty-chain fixtures measure core
validation, not general UI latency. A1000-deep chain remains a pathological cost.
Current ownership: drawing_correctness owns desktop except data_view.rs;
state_architecture_review now owns only data_view.rs bounded focused-dictionary
correction. Its independent review found unbounded inherited rows/picklists,
unreachable recursive paths and loss of scenario values on same-phase style or
same-exchange reselection. Drawing worker fixes recursive drill-down/draft retention.
data_core now verifies Linux in a separate data-linux-review checkout/target.
Root owns API/OpenAPI/reST, integration and native input. No concurrent file writers.
Independent desktop review fixes now pass tests: a focused dictionary with24-row
pages replaces unbounded inherited rows; recursive paths support explicit drill-down
and imported finite paths; same-phase styles/same-exchange reselection preserve
valid drafts. Read-only follow-up found no new path/style defect. Paging resets
only on actual layer/document changes; its regression failed before and passes now.
Root found another unresolved scale issue: scenario creation still enumerates every
carried field into both a dropdown and individual input rows. Native reproduction
and a bounded focused value editor remain required before R6 acceptance.
Current ownership: drawing_correctness owns desktop except root-owned guide.rs and
the dedicated Windows Cargo target. state_architecture_review independently reviews
R6 spec/API consistency; its data_view.rs ownership has ended. data_core runs an
isolated R3 typed-baseline experiment; Linux R6 core checkout is idle and verified.
Root owns API/OpenAPI/reST, docs, integration and native input. No concurrent writers.
1. State evidence is committed and main fast-forwarded to a8f451e; DATA received
the same evidence in c5276b1. Finish the3 concrete desktop review fixes and
optimized inheritance measurement, then native data-authoring acceptance.
the same evidence in c5276b1. Finish native data-authoring acceptance and bounded
scenario-value authoring, then full integrated Windows/Linux verification.
2. Finish R6 core/source/desktop, integrate actual REST/schema/reST, independent
semantic/correctness/UX review, Windows/Linux checks and real data authoring.
3. Implement R3 typed semantic drift/reconciliation after R6 freezes. Current