docs(docs): V1-2.6 UX U0, contract amendments, O22 checks, level-1 notes
This commit is contained in:
1 parent
a505b24bfd
commit
d9e3e34aff
11 files changed
+604
-141
No files matched your search
@@ -8,6 +8,16 @@
|
||||
- contract of the step: docs/development/V1-2_ANATOMICAL_SHEETS.md §16.7 and §8.1-§8.4, with §6.2, §6.6, §6.7,
|
||||
§9.2-§9.4, §10, §11.1-§11.2, §17.9, §17.11; design docs/design/v1-2-4 boards 04, 05, 06 A (approved, BDR-096),
|
||||
REVUE.md ratified wordings
|
||||
- [amended 2026-11-05, V1-2.6 UX U0] level 1 as built here is NOT declared validated as a whole (owner T11); the
|
||||
redesign (sub-steps U1 to U8 of `docs/development/V1-2-6_UX_PLAN.md`) follows the 16 boards of
|
||||
`docs/design/v1-2-6` (validated 2026-11-05), which replace v1-2-4 boards 04 and 05 for editing (board 05's
|
||||
narrow-screen read-only mode stays the reference under O14 A, C16); the criteria it changes carry an amendment
|
||||
note below. Precedence for the redesign: where a criterion of this contract, with or without a note, differs
|
||||
from the validated v1-2-6 boards or from the V1-2 contract as amended (§8.2-§8.4, §17.12), the amended contract
|
||||
prevails first, then the boards. Two exceptions: a difference listed in `docs/development/V1-2-6_UX_DECISIONS.md`
|
||||
(« Points from the boards for U1 and later ») is an open owner question, and until the owner answers it the
|
||||
criterion stays as written; a point owned by another step (V1-2.7: preview, withdrawal) stays with that step. The
|
||||
other criteria stay in force
|
||||
|
||||
## REQUEST (verbatim — IMMUTABLE)
|
||||
|
||||
@@ -159,7 +169,9 @@ Q: Which drawing for A2 (« un SVG réel », non-equine, exported then cleaned)
|
||||
committed Inkscape 1.4.3 export (`crates/core/tests/fixtures/svg/exports/inkscape-1.4.3-*.svg`, a real export,
|
||||
cleaning offered) plus a hostile file; the owner may import a drawing of their own at the trial.
|
||||
Q: Undo / redo control (not on board 04) / A: [gated 2026-11-03] two icon buttons « Annuler » and « Rétablir »
|
||||
in the tool column under the zoom, plus Ctrl+Z and Ctrl+Shift+Z.
|
||||
in the tool column under the zoom, plus Ctrl+Z and Ctrl+Shift+Z. [amended 2026-11-05, U0, §17.12: the two buttons
|
||||
move to the editor header on every tab (ARBITRAGES choice 2, built at U1); the history command is named « Annuler la dernière
|
||||
modification » (T15); the shortcuts are unchanged.]
|
||||
Q: Plan approval (8 visible choices, rescue copy) / A: [gated 2026-11-03] owner brief « GO propriétaire V1-2.6 »:
|
||||
plan, lots A-M, C1-C24 and the 8 choices approved; M8 on the throwaway sandbox only; no JSON export button for the
|
||||
recovery copy; local recovery kept with exact messages on its state and limits; a local restore never silently
|
||||
@@ -198,11 +210,22 @@ checked across develop, main, feature/v1-1, feature/v1-2: next free were BDR-099
|
||||
3. Tabs Général, Vues et illustrations, Annotations, Constats, Références, Vertèbres, Vérification (§11.1),
|
||||
ARIA tabs; every change is one core `sheet.edit` command run on commit (blur, confirm, pointer-up), never
|
||||
per keystroke; TypeScript keeps no document schema and no Zod copy (ts-rs types only).
|
||||
[amended 2026-11-05, V1-2.6 UX U0, V1-2 contract §17.12; built at U1] Four tabs: Général, Annotations,
|
||||
Constats, Vérification. Views, drawings, annotation categories and vertebral regions move into Annotations;
|
||||
Références becomes a side panel opened from the header or from a finding; Annuler and Rétablir sit in the
|
||||
header on every tab. The commit rule and the ts-rs-only rule above are unchanged.
|
||||
4. Général: FR/EN name, description, scope disclaimer, attribution (authors, licence, notes); annotation
|
||||
categories (name FR/EN, colour) add, edit, delete.
|
||||
[amended 2026-11-05, U0, §17.12] Categories leave Général for the category panel of Annotations (U3: swatch
|
||||
and name, palette and hex, staged « Appliquer », delete when unused, « Réaffecter à… »). From U6 the three fixed
|
||||
categories Os, Articulations, Vertèbres keep their names and roles (no delete, name read-only), their colour and
|
||||
fill opacity stay adjustable; other categories stay free.
|
||||
5. Références: add, edit, delete; type, citation, URL (http or https only), DOI. Vertèbres: add (code typed at
|
||||
creation, read-only after), edit, reorder ↑/↓, delete. A refused removal (`has_dependents`) lists the
|
||||
dependents from `sheet.dependents`; no cascade deletion.
|
||||
[amended 2026-11-05, U0, §17.12] References move to a side panel (C3). Vertebral regions open from the
|
||||
vertebra-role category at U6 (board 09): reorder by grip handle or Alt+arrows, staged « Appliquer »; the
|
||||
↑/↓ buttons stay until then; whether a region code stays read-only after creation is settled at U6.
|
||||
6. Vues et illustrations: main view and detail views (parent; own drawing or crop entered as numeric
|
||||
`view_box` values over the parent's preview), rename, delete (dependents listed). Drawing upload: the file
|
||||
is read by the core (`clean_svg`); hard rejection and active content refused with the reason in FR/EN, no
|
||||
@@ -211,6 +234,11 @@ checked across develop, main, feature/v1-1, feature/v1-2: next free were BDR-099
|
||||
registered, hashed and uploaded are `SvgCleaning.stored` with the core's sha256; register, upload at
|
||||
`<sha256>.svg` (an existing object, Storage HTTP 400 with body `statusCode` "409", counts as present),
|
||||
confirm; the drawing state (ok, missing, rejected) is shown; the §9.3 closed codes have FR/EN messages.
|
||||
[amended 2026-11-05, U0, §17.12] Views and drawings sit in Annotations. A crop is drawn as a rectangle over
|
||||
the parent's drawing, its handles resizable by keyboard (U4); the numeric `view_box` editor leaves the normal
|
||||
journey; the view's name is proposed from the annotations inside and stays editable (U5); replacing a crop
|
||||
view's drawing opens the three-action dialog of decision T9 before any upload (U5). Upload, cleaning, register,
|
||||
upload and confirm are unchanged.
|
||||
7. Annotations: on the core-composed view (`view.canvas`), tools select, point, zone, detail-view link, zoom;
|
||||
a point by one click with its radius in a field; a zone and a link as polygons by successive clicks,
|
||||
closed, Escape cancels a tracing; a link chooses the view it opens; selection on the drawing or in the
|
||||
@@ -219,8 +247,21 @@ checked across develop, main, feature/v1-1, feature/v1-2: next free were BDR-099
|
||||
moved or edited as path data; zoom and pan; every coordinate (cx, cy, r, each vertex x and y) in numeric
|
||||
fields, vertices added and removed in the list; a keyboard-only path creates and edits points, zones and
|
||||
links (numeric fields).
|
||||
[amended 2026-11-05, U0, §17.12; built at U2 and U4] Direct manipulation replaces the numeric fields in the
|
||||
normal journey: point move and a size slider snapped to the sizes of the view, with the core's minimum mark;
|
||||
vertex drag, « + » on a segment, « − » on the chosen vertex (disabled at 3 vertices with its reason, board 12 B); zone move, directly
|
||||
with the mouse once selected, in an explicit « Déplacer la zone » mode by touch; redraw keeping the old shape
|
||||
until the new one is accepted. The keyboard alternative goes through the handles (Tab, arrows, Shift ×10,
|
||||
Insert or Backspace or Delete, Enter, Escape); no coordinate field. The detail-view link tool leaves the
|
||||
toolbar: an access is placed from the view's menu (« Ajouter un accès »), and created with the view from U6
|
||||
when no annotation overlaps it. Paths are unchanged (C45, T16): displayed, selectable, deletable, never moved
|
||||
or edited; « Remplacer par un polygone » stays their one explicit exit, validated by the core, the old path kept
|
||||
until the polygon is accepted, one undo entry.
|
||||
8. Annotation properties: FR and EN name, category, laterality, finding zone, vertebral region, colour,
|
||||
review marking; « Marquer comme relu » on one element; delete with the dependents shown when refused.
|
||||
[amended 2026-11-05, U0, §17.12; built at U3] The annotation's own colour is shown only when set, with
|
||||
« Revenir à la couleur de la catégorie » (one `update` with `color: null`); a new annotation carries no own
|
||||
colour and inherits its category's. The other properties are unchanged.
|
||||
9. Constats: tree of finding zones, categories (kind) and nodes up to depth 8: add, rename FR/EN, describe
|
||||
FR/EN, vet referral flag, cite references, review marking of one element, « Marquer comme relu » on one
|
||||
category or one zone (never sheet-wide), reorder among siblings with ↑/↓, delete with a confirmation
|
||||
@@ -236,6 +277,14 @@ checked across develop, main, feature/v1-1, feature/v1-2: next free were BDR-099
|
||||
deviation of REVUE.md); header « Révision N · modifications non enregistrées »; every server failure kind
|
||||
mapped to an FR/EN message; « Annuler les modifications » returns to the last saved document after a
|
||||
confirmation; the leave guard (`useLeaveGuard`) is armed while unsaved.
|
||||
[amended 2026-11-05, U0, §17.12; built at U1] The header states follow the validated boards (07, 08, 09,
|
||||
12 A, 13): « n modifications non enregistrées » while unsaved, « Enregistré à hh:mm · révision n » after a
|
||||
save; the exact labels go to the U1 label review.
|
||||
[amended 2026-11-05, U0, owner decision T15, §17.12; built at U1] The command that returns to the last saved
|
||||
document is labelled « Abandonner les modifications » (today `editor.draft.discard` « Annuler les
|
||||
modifications », `apps/app/src/i18n/fr.ts:1238`), so no discard of unsaved changes is called « Annuler »;
|
||||
dialogs that close without effect keep « Annuler » (outside T15, DECISIONS T15); its confirmation and behaviour
|
||||
are unchanged.
|
||||
12. Conflict (§6.2): `draft_conflict` opens a dialog with the server revision (and its author and time if the
|
||||
owner's answer provides them) and « Recharger » or « Garder ma version »; the second saves the local
|
||||
document on the new revision only after an explicit confirmation naming what it replaces; nothing is
|
||||
@@ -245,12 +294,18 @@ checked across develop, main, feature/v1-1, feature/v1-2: next free were BDR-099
|
||||
status bound to the real write (LRN-057), removed after a successful save or an explicit discard; offered
|
||||
back on opening when it differs from the server document, restored through the core, never sent
|
||||
automatically; proven by a restore round trip (LRN-058).
|
||||
[amended 2026-11-05, U0, wording matched to the code] The copy is keyed by account and version
|
||||
(`apps/app/src/editor/state/recovery.ts:47-49`); the revision is a field of the copy (`recovery.ts:25`), used
|
||||
as the expected revision at restore (C27). Behaviour unchanged.
|
||||
14. Undo and redo: a stack bounded by 8 MiB of document strings (UTF-8 bytes).
|
||||
15. Ids generated by the page `<prefix>-<10 characters a-z2-7>` (crypto random), inside the stable-id grammar,
|
||||
never derived from labels, never editable, never reused within the document.
|
||||
16. Below 1 024 px (board 05): read-only, badges « Brouillon » and « Lecture seule », the notice title alone
|
||||
(L15, BDR-099 §17.11), tabs, the whole drawing at opening, zoom and pan, a properties summary, no editing
|
||||
action; unsaved work in memory survives a width change. No horizontal scroll at 320, 375 and 768 px.
|
||||
[amended 2026-11-05, U0] Board 05 is v1-2-4's and stays the reference of this read-only mode under O14 A.
|
||||
Board 15 C of v1-2-6 shows the same rule only as an illustration: its two-sentence notice and the absence of
|
||||
tabs and summary there are not adopted; the notice title alone, the tabs and the summary stay.
|
||||
17. Security: stored drawing bytes are never inserted into the page; only core-composed trees are rendered
|
||||
(DOMParser + importNode); the cleaning preview is composed by the core under a scope unique in the page;
|
||||
the original file is never rendered; no `innerHTML` / `dangerouslySetInnerHTML` carries drawing or
|
||||
@@ -259,6 +314,11 @@ checked across develop, main, feature/v1-1, feature/v1-2: next free were BDR-099
|
||||
core's rules and readers, the readers of user data, the equine legacy sources, seed and oracles, the
|
||||
goldens; the wasm module within its 600 000 B gzip budget; `pnpm r5:import-equine --check` without
|
||||
difference.
|
||||
[amended 2026-11-05, U0, §17.12] This list describes level 1. The redesign changes, each on its own
|
||||
authorisation: one read-only core value (U2), two core queries (U5), and at U6 the category model (core rules
|
||||
and edit refusals, a bounded widening of the snapshot reader, one SQL migration with the declared checks of
|
||||
contract §12.2), under `docs/development/V1-2-6_UX_COMPATIBILITY.md`. The seed, the legacy sources, the
|
||||
oracles, the goldens, the wasm budget rule and `r5:import-equine --check` stay unchanged.
|
||||
19. i18n: FR and EN parity; the ratified wordings (REVUE.md, §17.9, §17.11) used verbatim; the new labels
|
||||
listed for a separate owner review, not declared approved.
|
||||
20. Tests: unit (editor state, ids, undo bound, recovery, conflict, upload steps, issue mapping); `e2e:shell`
|
||||
@@ -267,6 +327,9 @@ checked across develop, main, feature/v1-1, feature/v1-2: next free were BDR-099
|
||||
account without capability refused); read-only at 320, 375 and a width under 1 024 px; axe on the
|
||||
editor and the read-only mode; core-wasm proofs; equine non-regression (catalogue P1, the equine working
|
||||
copy opening in the editor read path, `r5:import-equine --check`).
|
||||
[amended 2026-11-05, U0, §17.12] With the redesign the keyboard path goes through the handles and the
|
||||
rectangle (C7 and C6 as amended), not through numeric fields; the redesign's tests are in
|
||||
`docs/development/V1-2-6_UX_TESTS.md` (U1 to U8). The other tests are unchanged.
|
||||
21. Demonstration on a fresh sandbox of the request's §3 journey (steps 1 to 12) for a non-equine species,
|
||||
built from scratch in the UI, saved, reloaded, conflicted, submitted; the validation panel shows no error
|
||||
while elements are still `to_confirm`; the round reaches `verifying` (no verification worker started).
|
||||
@@ -280,6 +343,14 @@ checked across develop, main, feature/v1-1, feature/v1-2: next free were BDR-099
|
||||
25. [gated 2026-11-03] The plan's eight visible choices are built as approved; no JSON export or import of the
|
||||
recovery copy; every message about the copy says it is temporary, limited to this tab and not saved on the
|
||||
server, and reads the real write flag.
|
||||
[amended 2026-11-05, U0, §17.12] Of the plan's eight choices, the redesign replaces three: categories edited in
|
||||
Général (now in Annotations, C4), keyboard creation through numeric fields (now through handles, C7), the
|
||||
properties card under the canvas from 1 024 to 1 279 px (now beside it, board 13).
|
||||
Plan choice 2 (creation panels ask names and laterality before the element exists, no preselection, no default
|
||||
labels): for detail views it gives way to the validated name proposal (ARBITRAGES choice 6, contract §8.2 as
|
||||
amended, C6); for points and zones it differs from boards 02 and 04 (laterality and other properties set after
|
||||
creation), an open owner question listed in DECISIONS, plan choice 2 in force until it is answered. The other
|
||||
four stay.
|
||||
26. [gated 2026-11-03] Default point: radius `r0 = min(12 + 0.03 × max(w, h), min(w, h) / 2)` in the view's frame
|
||||
as composed by the core (composed root `viewBox`, origin kept); the clicked position is kept with r0 when the
|
||||
circle fits, else with a smaller radius when the core accepts it; otherwise a corrected position is shown
|
||||
@@ -296,7 +367,8 @@ checked across develop, main, feature/v1-1, feature/v1-2: next free were BDR-099
|
||||
the server version; a copy the core refuses is reported, kept, never applied, and editing stays blocked until
|
||||
it is ignored.
|
||||
28. [gated 2026-11-03] A copy is removed only by a successful save leaving nothing unsaved, or a confirmed
|
||||
« Annuler les modifications », « Ignorer la copie », « Recharger » or « Abandonner cette copie »; never on
|
||||
« Annuler les modifications » ([amended 2026-11-05, U0] « Abandonner les modifications » from U1, C11 as amended), « Ignorer la copie »,
|
||||
« Recharger » or « Abandonner cette copie »; never on
|
||||
undo, never by automatic eviction; at most two copies of other versions of the account; when the cap or the
|
||||
storage quota prevents keeping the current copy, the page says so and lists the other copies for an explicit,
|
||||
confirmed abandonment; unit tests for the cap, the quota and pending copies.
|
||||
@@ -317,6 +389,9 @@ checked across develop, main, feature/v1-1, feature/v1-2: next free were BDR-099
|
||||
illustrations »; existing annotations shown and selectable with read-only geometry, no drag; `accept` refuses
|
||||
every creation and geometry commit there (checked on the post-commit state); the fallback frame `0 0 100 100`
|
||||
is never used as a frame; the core stays the authority, no TypeScript frame or size rule.
|
||||
[amended 2026-11-05, U0, §17.12] With direct manipulation the same views disable the handles, the size slider,
|
||||
the keyboard handle moves, the creation tools and the detail-view rectangle, with the same hint naming where the
|
||||
drawing is attached (Annotations after U1); there is no numeric geometry field left to disable.
|
||||
33. [gated 2026-11-04] Geometry commits: accepted only when the changed annotation carries no Error at
|
||||
`annotations[i].geometry` after the commit (new, valid or already invalid before), refused otherwise with the
|
||||
handle rolled back and nothing kept; a typed radius the core reports `too_small` is refused; the geometry
|
||||
@@ -326,6 +401,11 @@ checked across develop, main, feature/v1-1, feature/v1-2: next free were BDR-099
|
||||
annotation without a geometry error gets one, or a measured view holding annotations becomes unmeasured; the
|
||||
save path and the server verdict unchanged; Node-core unit tests for repair, `too_small`, drag rollback and
|
||||
frame changes.
|
||||
[amended 2026-11-05, U0, §17.12] The acceptance rule applies to every handle gesture, slider release and
|
||||
keyboard move: a geometry commit is kept only when the changed annotation carries no Error at
|
||||
`annotations[i].geometry` afterwards; a refused gesture restores the previous shape exactly, with the core's
|
||||
message. The numeric form group leaves the normal journey: an annotation already invalid is repaired through its
|
||||
handles, its error shown until the fix is accepted. The frame-change rule is unchanged.
|
||||
34. [gated 2026-11-04] A drag starts after 4 CSS px (click, keyboard and touch kept); an unreadable copy is kept
|
||||
until « Ignorer la copie » confirmed, its notice names the loss, editing blocked meanwhile; the leave guard is
|
||||
armed only while unsaved or a recovery decision is pending, and its mobile-browser limits are documented; the
|
||||
@@ -344,6 +424,9 @@ checked across develop, main, feature/v1-1, feature/v1-2: next free were BDR-099
|
||||
naming its effect) and non-destructive (undoable; the stored drawing is not deleted).
|
||||
40. [gated 2026-11-04 checkpoint] Default tab at opening: Général for a new, empty sheet; Annotations for an
|
||||
existing sheet with at least one measurable view; read-only modes kept.
|
||||
[amended 2026-11-05, U0, §17.12] Same rule on the four tabs of C3: Annotations now also holds the views and
|
||||
drawings, so a sheet without a measurable view still opens on Général and reaches the drawing upload from
|
||||
Annotations.
|
||||
41. [gated 2026-11-04 checkpoint] Attaching a drawing to an unmeasured view whose annotations would fall out of the
|
||||
new frame no longer forces their deletion: the attachment and the repairs are prepared in a temporary state
|
||||
and validated atomically by the Rust core (one commit, nothing kept on refusal). A new Rust operation, if one
|
||||
|
||||
@@ -0,0 +1,63 @@
|
||||
# CONTRACT: V1-2.6 UX, sub-step U0 (contract, decisions and amendments, docs only) (2026-11-05)
|
||||
|
||||
- REQUEST (owner brief « FAUNOSTEO — V1-2.6 UX — Autorisation U0 uniquement », 2026-11-05): start U0 and U0 only,
|
||||
after the pending doc corrections are verified and committed. The UX choices and the 16 V2 boards are approved
|
||||
for good; no graphic arbitration is reopened. Record the complementary ratification (A), run U0 as defined in
|
||||
`docs/development/V1-2-6_UX_PLAN.md` §3 U0 (docs, contract, preconditions, non-destructive checks), stop at the U0
|
||||
checkpoint. No merge, no deploy, no DEV access or write, no U1, no V1-2.7. Owner brief « FAUNOSTEO — V1-2.6 UX —
|
||||
Finalisation de U0 uniquement » (2026-11-05, after the ratification was verified CONFORME at `a505b24`): finish the
|
||||
uncommitted U0 work without overwriting it (main contract sections, level-1 criteria, five UX docs, BDR-101, TODO),
|
||||
check every cross-reference, independent review, commit and push only the planned docs, stop at the U0 checkpoint.
|
||||
- OWNER ANSWERS (brief A):
|
||||
- T4: both declared SQL checks approved: at save, protect the uniqueness of the fixed categories, their roles and
|
||||
their presence without blocking old drafts that carry none of these keys; at approval and publication,
|
||||
guarantee the model's invariants whatever the worker does. O22 amended strictly for these invariants; the core's
|
||||
validation is not duplicated in SQL.
|
||||
- T5: new-sheet ids `cat-bone`, `cat-joint`, `cat-vertebra`; the validated French names kept; the English names
|
||||
and the exact reference colours documented from the existing data; historical sheets and their fingerprints
|
||||
fully preserved.
|
||||
- T10: option B: internal category `cat-access`, role `navigation`, not visible as an anatomical category;
|
||||
automatic access conditional on U6.
|
||||
- T15: « Annuler la dernière modification » for the history; « Abandonner » or « Abandonner les modifications »
|
||||
for a form.
|
||||
- T16: deferral of curve editing kept; a check of the existing geometries planned before any activation of the
|
||||
new model, with no DEV access during U0.
|
||||
- T12: U7 stays blocked until the source and the legal content are validated.
|
||||
- T17: its exact wording read and presented, no decision invented; stop only if it really blocks U0.
|
||||
- T1/T6: conditions and deadlines already documented kept.
|
||||
- « Remplacer par un polygone »: kept only as an explicit replacement, validated, the old path kept until
|
||||
success, undo and redo supported; no automatic destructive conversion.
|
||||
- ACCEPTANCE CRITERIA:
|
||||
- U1c Each answer above is recorded once (`V1-2-6_UX_DECISIONS.md` and the contract's new §17.12) and cited where
|
||||
it applies; BDR-101 written through `memory.sh`; BDR-100's open items marked answered through `memory.sh status`.
|
||||
- U2c O22 (`V1-2_ANATOMICAL_SHEETS.md` §12.2 and the §17.1 row) amended strictly: the two declared checks hold only
|
||||
the fixed-category invariants (each role `bone`, `joint`, `vertebra` carried by exactly one category with its
|
||||
fixed FR and EN names; at save: no regression of the stored draft's roles, role-less drafts still save); no other
|
||||
rule mirrored; `.claude/rules/sheet-model.md` says the same.
|
||||
- U3c §7.4 records the one-time copy of a versioned common text and the T12 block, with no normative wording.
|
||||
- U4c §8.2, §8.3, §8.4 match the validated UX and the decisions: four tabs, direct manipulation, no coordinate
|
||||
field in the normal journey, crop rectangle drawn, fixed categories and opacity at U6, own colour shown when
|
||||
set, access placed from the view's menu (automatic at U6 with `cat-access`), curves per T16 with the
|
||||
« Remplacer par un polygone » guarantee, O14 A kept, the tablet rule.
|
||||
- U5c §16.7 states the level-1 status (T11, not validated as a whole) and the redesign sub-steps; the withdrawal
|
||||
rule of §6.4 is precise about draft rounds, matching T4 and the code.
|
||||
- U6c Level-1 contract criteria C3, C4, C6, C7, C8, C13, C32, C33, C40 amended in place (original text kept, an
|
||||
amendment note appended), the immutable REQUEST untouched; no contradiction with the boards or the contract.
|
||||
- U7c `docs/design/README.md`: v1-2-6 validated, its boards replace v1-2-4 boards 04 and 05 for the editor
|
||||
(BDR-096 kept for the rest).
|
||||
- U8c `.claude/rules/schemas.md` and `sheet-model.md`: optional category keys under T2 (omitted when absent, never
|
||||
null, no version bump, proof list), rules also in `edit.rs` and `sheet_report`.
|
||||
- U9c The implementer decisions (T7, T8, T13, T18, T19) recorded in the contract.
|
||||
- U10c The five UX docs, RISKS blocking criteria, TODO.md and the journal agree with U1c-U9c; nothing answered is
|
||||
still called open or « to confirm »; T17, T1, T6, T12, T14 stay open with their conditions.
|
||||
- U11c Facts cited for T5 (names, colours) and the « Remplacer par un polygone » guarantee hold in the data and
|
||||
the code (file:line).
|
||||
- U12c Scope: no change under `crates/`, `apps/`, `packages/`, `supabase/`, `scripts/`; no SQL, worker, sandbox or
|
||||
DEV command; no merge.
|
||||
- FILE SCOPE: `docs/development/V1-2_ANATOMICAL_SHEETS.md`, `docs/development/V1-2-6_UX_{DECISIONS,PLAN,COMPATIBILITY,
|
||||
TESTS,RISKS}.md`, `docs/design/README.md`, `.claude/tasks/contracts/2026-11-03-v1-2-6-editor-1509.md`,
|
||||
`.claude/rules/{sheet-model,schemas}.md`, `.claude/tasks/TODO.md`, `.claude/memory/{decisions,journal}.md`
|
||||
(through `memory.sh`), this contract.
|
||||
- OUT OF SCOPE: code, SQL, worker, Supabase DEV, sandbox, `docs/design/v1-2-6/*` (archived boards and their notes),
|
||||
`ANNOTATION-RENDERING.md` and `ANATOMICAL_SHEET_MODEL.md` (U6), U1 and later, V1-2.7.
|
||||
- ABANDON: if a criterion needs a change outside the file scope, stop and report.
|
||||
Reference in new issue
Block a user