docs(docs): V1-2.6 UX U0, contract amendments, O22 checks, level-1 notes

This commit is contained in:
bchanot committed 2026-11-06 11:06:10 +01:00
1 parent a505b24bfd
commit d9e3e34aff
11 files changed
+604 -141

No files matched your search

+4 -1
View File
@@ -8,7 +8,10 @@ paths: ["crates/core/src/domain/**", "packages/core-wasm/tests/n-1/**"]
`packages/domain` was deleted at R5.7; its byte-identical Zod copy under `packages/core-wasm/tests/n-1` is the
permanent N-1 reader. Never change a contract
without bumping the version on a breaking change (additive optional fields keep it); a change touches the
Rust struct, the regenerated ts-rs types and the N-1 test
Rust struct, the regenerated ts-rs types and the N-1 test. A new optional field of the sheet document is omitted when
absent and refuses `null` (`skip_serializing_if`, `js::present`, `ts(optional)`), so existing fingerprints stay
equal and the ts-rs type stays assignable to N-1; the V1-2.6 category keys also need the proofs of
`docs/development/V1-2-6_UX_COMPATIBILITY.md` §8 (T2)
- Every report entering the store comes from the core (new report, draft restore, import, reducer outputs);
form values are plain assignments (D-R7)
- Report version 3: zones by `(annotationId, viewId)`, findings by `(findingZoneId, path)`, severities
+13 -4
View File
@@ -12,10 +12,18 @@ paths: ["crates/core/src/domain/sheet/**", "docs/development/ANATOMICAL_SHEET_MO
draft (`create_sheet_draft`) then publication; from V1-2, publication only from an approved round on a server
verdict of the core.
- The Rust core is the only authority on document rules (O22): add a rule to `validate_sheet_document` and to the spec
table only. V1-2 (M5) dropped the SQL mirror (`private.sheet_document_issues`); SQL keeps the structural and
relational guards and the one declared status check (contract §12.2). Never add a business rule in SQL.
table only. A rule that must not strip existing fingerprints or reject old snapshots lives in `edit.rs` (editor
refusals) and in the verdict-only tier of `sheet_report`, never as a `validate.rs` error (V1-2.6 fixed categories,
T4). V1-2 (M5) dropped the SQL mirror (`private.sheet_document_issues`); SQL keeps the structural and relational
guards, the declared status check and, from V1-2.6 U6, the two declared fixed-category checks (save
non-regression; approval and publication), which hold the fixed-category invariants only (contract §12.2,
§17.12). Never add any other business rule in SQL.
- Document schema change → bump `SHEET_DOCUMENT_SCHEMA_VERSION`, extend the SQL CHECK on `document_schema_version`.
No bump during V1-2 (BLK-008).
No bump during V1-2 (BLK-008). Ratified exception (V1-2.6 T2, BDR-100, BDR-101): an optional key omitted when
absent (`skip_serializing_if`, `js::present`, `ts(optional)`, an explicit `null` refused, never defaulted in the
fingerprinted document) is not a version change; it ships only with the proofs of
`docs/development/V1-2-6_UX_COMPATIBILITY.md` §8, and its first write is a point of no return (one-way
compatibility, never called full backward compatibility).
- Historical equine sheet `503dc301…` = generated seed `draft/` (`pnpm import:equine --out` into an empty folder, then
reviewed and copied; never edit `legacy-import/` or `draft/` by hand; `curation_draft` / `curation_review` fail on
drift, `pnpm import:equine --check` lists it). Its content changes only through `curation/changes.json` (traced in
@@ -31,4 +39,5 @@ paths: ["crates/core/src/domain/sheet/**", "docs/development/ANATOMICAL_SHEET_MO
review screen), the document measure (`size.rs`:
PostgreSQL's `jsonb` text, never `JSON.stringify`), `PreviewSheet` and the editor's commands (`edit.rs`, the §6.6
marking rules). A change to the SVG reader, the rules, the caps, the fingerprint or the digests is a core change
(contract §6.4: the release withdraws open rounds). RUST.md §12.
(contract §6.4: the release withdraws the rounds of drafts in flight; a published version's round stays approved).
RUST.md §12.