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
@@ -1,30 +1,32 @@
|
||||
# V1-2.6 UX redesign: technical decisions
|
||||
|
||||
Status: OWNER ANSWERS RECORDED, 2026-11-05 (brief « FAUNOSTEO — V1-2.6 UX — Ratification des décisions
|
||||
techniques »). Companion of `V1-2-6_UX_PLAN.md`; this is the single table of what blocks what. The 11 UX choices and
|
||||
the direct SVG interactions validated by the owner on 2026-11-05 are not reopened. Nothing here authorises code: U0
|
||||
(docs) and every later sub-step start only on a new explicit authorisation.
|
||||
Status: OWNER ANSWERS RECORDED, 2026-11-05: brief « FAUNOSTEO — V1-2.6 UX — Ratification des décisions
|
||||
techniques » (BDR-100), then brief « V1-2.6 UX — Autorisation U0 uniquement » (BDR-101; T4 checks, T5 defaults, T10
|
||||
option B, T15, T16 count, « Remplacer par un polygone »). Companion of `V1-2-6_UX_PLAN.md`; this is the single
|
||||
table of what blocks what; the contract records the same decisions in `V1-2_ANATOMICAL_SHEETS.md` §17.12. The 11 UX
|
||||
choices and the 16 boards are approved for good and not reopened. Nothing here authorises code: U0 (documents only)
|
||||
was authorised on 2026-11-05; every later sub-step starts only on a new explicit authorisation.
|
||||
|
||||
## Owner decisions
|
||||
|
||||
| Id | Question | Owner answer (2026-11-05) | State | Blocks |
|
||||
|---|---|---|---|---|
|
||||
| T1 | Fallback if the wasm budget is exceeded | not asked this round; measuring rule recorded (LRN-118) | open, used only if a measure exceeds 600 000 B | U5, U6 if a measure exceeds |
|
||||
| T1 | Fallback if the wasm budget is exceeded | not asked; conditions kept (brief U0); measuring rule recorded (LRN-118) | open, used only if a measure exceeds 600 000 B | U5, U6 if a measure exceeds |
|
||||
| T2 | Optional category keys; widening of the snapshot reader | agreement in principle, conditional on the proofs | ratified with conditions (§ T2 and T3) | writing the keys (U6 write lock) |
|
||||
| T3 | Opacity semantics | integer percent from 10 to 100 | ratified with T2's conditions | U6 |
|
||||
| T4 | Fixed-category checks | no residual gap; checks in the core and at the server boundaries of save and publication; nothing written before they are live | ratified; design below; the two declared SQL checks (save non-regression, publication) to confirm | U6 |
|
||||
| T5 | Equine history; categories of a new sheet | historical preservation mandatory; roles on a working copy only; conversion tested without mutating the originals | ratified for the history; new-sheet ids, EN names and colours still to ratify | U6 (defaults), V1-2.8 |
|
||||
| T6 | Equine working copy conversion | not asked | open, decided at V1-2.8 under T4 and T5 | V1-2.8 |
|
||||
| T4 | Fixed-category checks | no residual gap; checks in the core and at the server boundaries of save and publication; nothing written before they are live; brief U0: both declared SQL checks approved (save, approval and publication), O22 amended strictly for these invariants | ratified; design below; O22 amended at U0 (contract §12.2) | none left to decide; U6 builds them |
|
||||
| T5 | Equine history; categories of a new sheet | historical preservation mandatory; roles on a working copy only; conversion tested without mutating the originals; brief U0: ids `cat-bone`, `cat-joint`, `cat-vertebra`, French names kept, EN names and colours from the existing data | ratified | none left to decide; V1-2.8 (T6) |
|
||||
| T6 | Equine working copy conversion | not asked; conditions and deadline kept (brief U0) | open, decided at V1-2.8 under T4 and T5 | V1-2.8 |
|
||||
| T9 | Replacing a crop view's drawing | explicit choice: keep positions, reposition, cancel; no approximate automatic transformation | ratified; design below | U5 |
|
||||
| T10 | Automatic access to a detail view | system navigation type distinct from the visible taxonomy; schema checked first; never Os, Articulations or Vertèbres | principle ratified; internal category to confirm | automatic access (moved to U6) |
|
||||
| T10 | Automatic access to a detail view | system navigation type distinct from the visible taxonomy; schema checked first; never Os, Articulations or Vertèbres; brief U0: option B (`cat-access`, role `navigation`, not visible as an anatomical category, automatic access at U6) | ratified | automatic access waits for U6 |
|
||||
| T11 | Fate of the level-1 owner trial | approved: old-UX trials stopped; anomalies and untested items tracked; level 1 not declared validated | ratified | none |
|
||||
| T12 | Common text | principle of one versioned copy kept; legal text, source and validation to be supplied | principle ratified; text missing | U7 |
|
||||
| T12 | Common text | principle of one versioned copy kept; legal text, source and validation to be supplied; brief U0: U7 stays blocked until they are validated | principle ratified; text missing | U7 |
|
||||
| T14 | Multi-tab notice | not asked | open, follow-up | none |
|
||||
| T15 | Header « Annuler » wording | not asked | open | U1 (accessible name and tooltip) |
|
||||
| T16 | Curve handle editing | deferral only if the audit confirms it; exact geometry; no destructive conversion; identified future lot | ratified: deferred to the curves lot | none in V1-2.6; the database count before U6 or U8 reaches any environment beyond the throwaway sandbox |
|
||||
| T17 | Vertebral regions entry without a vertebra role | not asked | open | U6 |
|
||||
| T15 | « Annuler » wording | brief U0: « Annuler la dernière modification » for the history; « Abandonner » or « Abandonner les modifications » for a form | ratified | none left to decide; U1 applies it |
|
||||
| T16 | Curve handle editing | deferral only if the audit confirms it; exact geometry; no destructive conversion; identified future lot; brief U0: deferral kept, existing geometries checked before any activation of the new model, no DEV access during U0; « Remplacer par un polygone » explicit, validated, old path kept until success, undoable | ratified: deferred to the curves lot | none in V1-2.6; the path count before the new model is activated on an environment and before U6 or U8 reaches any environment beyond the throwaway sandbox |
|
||||
| T17 | Vertebral regions entry without a vertebra role | not asked; wording presented at the U0 checkpoint, no answer invented | open | U6 (not U0) |
|
||||
|
||||
## Implementer decisions (recorded at U0, no owner question)
|
||||
## Implementer decisions (recorded at U0 in contract §17.12, no owner question)
|
||||
|
||||
| Id | Decision | Reason |
|
||||
|---|---|---|
|
||||
@@ -90,8 +92,8 @@ the direct SVG interactions validated by the owner on 2026-11-05 are not reopene
|
||||
invisible while the 4 px rules assume it visible. Detail triggers keep 0.06; the selected state keeps its accent
|
||||
at 0.85 (`apps/app/src/styles/index.css:14`). Written first in `docs/ANNOTATION-RENDERING.md`. The layer writes it
|
||||
as `fill-opacity`, which the PDF highlight overwrites: no PDF effect.
|
||||
- Doctrine: `.claude/rules/sheet-model.md` amended at U0 (an optional key omitted when absent is not a version
|
||||
change, with this proof list). Route B (schema v3, excluded by contract §12.3, `V1-2_ANATOMICAL_SHEETS.md:1779-1781`)
|
||||
- Doctrine: `.claude/rules/sheet-model.md` and `schemas.md` amended at U0 (an optional key omitted when absent is
|
||||
not a version change, with this proof list). Route B (schema v3, excluded by contract §12.3, BLK-008 paragraph)
|
||||
and route C (reserved ids without opacity, contradicts choice 5) stay excluded.
|
||||
|
||||
## T4 · Fixed-category checks (ratified: no residual gap)
|
||||
@@ -100,27 +102,33 @@ the direct SVG interactions validated by the owner on 2026-11-05 are not reopene
|
||||
server boundaries for save and publication; the new model is not written before the necessary checks are live;
|
||||
a progressive rollout or a functional lock is used if needed. The earlier recommendation (issues relative to the
|
||||
base, residual first-version gap accepted) is withdrawn.
|
||||
- Owner answer, brief U0 (BDR-101): both declared SQL checks approved. At save: protect the uniqueness of the fixed
|
||||
categories, their roles and their presence without blocking the old drafts that carry none of these keys. At
|
||||
approval and publication: guarantee the model's invariants whatever the worker does. O22 is amended strictly for
|
||||
these invariants (contract §12.2, §17.12); the rest of the core's validation is not duplicated in SQL. Both checks
|
||||
are planned at U6 and not built.
|
||||
- Property guaranteed: no review round opens and no version is published on a draft whose categories break the
|
||||
fixed model, whoever wrote the draft (the editor, a direct `save_sheet_draft`, « Garder ma version », a tab
|
||||
running an older bundle). Fixed model: each role `bone`, `joint`, `vertebra` carried by exactly one category,
|
||||
and that category carries its fixed FR and EN names (T5).
|
||||
and that category carries its fixed FR and EN names (T5); the role `navigation` (T10) carried by at most one
|
||||
category, with its fixed names.
|
||||
|
||||
| Tier | Check | Where | New code |
|
||||
|---|---|---|---|
|
||||
| Core, verdict | absolute rule on the draft, no base needed: missing role, duplicate role, wrong name on a role-bearing category; error issues of their own code family `category.fixed.*`, mapped to the existing `verification.validation.rules` | `sheet_report` on the draft (`verdict.rs:188`), mapping `verdict.rs:277-296` | Rust; no verdict code, no `validate.rs` error |
|
||||
| Core, editor | giving a role writes the fixed FR and EN names in the same update; renaming a role-bearing category is allowed only to its fixed names; removing it, changing or clearing its role and a duplicate role are refused; `navigation` (T10 B) is never assignable by an edit; repair commands insert a missing fixed category, restore the fixed names and clear a duplicate role, so every state a direct save can write is repairable | `edit.rs` | Rust |
|
||||
| Server, save | non-regression check (recommended): a save that removes or duplicates a role present in the stored draft, or renames its category away from the fixed names, is refused; drafts without roles (pre-U6, equine working copy) still save | U6 migration, `save_sheet_draft`, a second declared SQL check under O22 | SQL, pgTAP; owner confirmation |
|
||||
| Core, editor | giving a role writes the fixed FR and EN names in the same update; renaming a role-bearing category is allowed only to its fixed names; removing it, changing or clearing its role and a duplicate role are refused; `navigation` (T10 B) is never given to, changed on or cleared from a category by an edit: the only way it enters a document is the insertion of the canonical `cat-access` (its id, fixed names, role, no colour) inside the core-built automatic-access batch, accepted only while no navigation category exists; repair commands insert a missing fixed category, restore the fixed names and clear a duplicate role, so every state a direct save can write is repairable | `edit.rs` | Rust |
|
||||
| Server, save | declared check (approved, brief U0): refused when a role is carried by two categories, when a category carrying a role does not carry that role's fixed names, or when a role of the stored draft is lost; a document without roles saves when the stored draft has none (pre-U6 drafts, equine working copy); every state a save can reach stays repairable | U6 migration, `save_sheet_draft`, a second declared SQL check under O22 (contract §12.2) | SQL, pgTAP |
|
||||
| Server, verification | the worker computes the verdict with the core above; a round opens only on a passed verdict | `complete_sheet_verification` (`20261101100000_sheet_verification_jobs.sql:300-345`) | none |
|
||||
| Server, core gate | a passed verdict computed by a core older than the U6 core is refused at completion, so an old worker (rollback, stale image, second instance) never opens a round | U6 migration, keyed on `verified_with` | SQL, pgTAP |
|
||||
| Server, publication | a declared SQL check `private.sheet_fixed_categories_ok(content)` (each role once, fixed names) at approval and at publication, beside the existing status checks, so a worker defect cannot publish a draft outside the fixed model (the reason O22 keeps declared SQL checks, contract `V1-2_ANATOMICAL_SHEETS.md:1705-1711`, `20261028110000:146-149`); the existing preconditions stay (`verdict.missing`, `verdict.stale`, `:984-990`; approved round on the current revision, `:1028-1072`) | U6 migration, `decide_sheet_review`, `publish_sheet_version` | SQL, pgTAP; O22 amended at U0 |
|
||||
| Server, rounds in flight | rounds in `verifying`, `open`, `approved` of draft versions withdrawn with the reason; the approved round linked to each published version stays approved | U6 migration (contract `V1-2_ANATOMICAL_SHEETS.md:945-949`) | SQL, pgTAP |
|
||||
| Server, publication | a declared SQL check `private.sheet_fixed_categories_ok(content)` (name provisional: each of `bone`, `joint`, `vertebra` once, `navigation` at most once, fixed names) at approval and at publication, beside the existing status checks, so a worker defect cannot publish a draft outside the fixed model (the reason O22 keeps declared SQL checks, contract §12.2, `20261028110000:146-149`); the existing preconditions stay (`verdict.missing`, `verdict.stale`, `:984-990`; approved round on the current revision, `:1028-1072`) | U6 migration, `decide_sheet_review`, `publish_sheet_version` | SQL, pgTAP; O22 amended at U0 |
|
||||
| Server, rounds in flight | rounds in `verifying`, `open`, `approved` of draft versions withdrawn with the reason; the approved round linked to each published version stays approved | U6 migration (contract §6.4, worded at U0) | SQL, pgTAP |
|
||||
|
||||
- Save boundary: the earlier text left save fully permissive and cited BDR-043; the governing rule is O22 (contract
|
||||
`V1-2_ANATOMICAL_SHEETS.md:1683-1711`), which allows a declared SQL check. An absolute check at save would lock the
|
||||
equine working copy and every pre-U6 draft; the non-regression check above locks none of them and stops stripping
|
||||
by a direct save, « Garder ma version » or an older tab at the source. Recommended; owner confirmation requested
|
||||
for both declared SQL checks: the contract says today « No other rule is mirrored »
|
||||
(`V1-2_ANATOMICAL_SHEETS.md:1711`), so O22 is amended at U0 only on that confirmation.
|
||||
§12.2), which allows a declared SQL check. A check requiring the three fixed categories at save would lock the
|
||||
equine working copy and every pre-U6 draft; the approved check requires nothing of a document without roles and
|
||||
stops stripping, duplicating or renaming by a direct save, « Garder ma version » or an older tab at the source.
|
||||
The owner approved both declared SQL checks (brief U0); O22 is amended in contract §12.2 (two table rows and the
|
||||
bullet that replaces « No other rule is mirrored »), and the contract §6.2 and §6.7 cite them.
|
||||
- Core gate detail: every core so far reports `faunosteo-core 0.1.0` (`verdict.rs:164-166`, workspace version
|
||||
`Cargo.toml:10`), so the gate needs a marker that tells the U6 core apart: a core version bump (owner's call) or a
|
||||
rules epoch added to `verified_with` (free text of at most 100 characters for SQL today). Chosen at U6, pinned by
|
||||
@@ -151,12 +159,20 @@ the direct SVG interactions validated by the owner on 2026-11-05 are not reopene
|
||||
- Test: a conversion of an in-memory copy of the seed draft document (roles on the T6 categories) asserts before and
|
||||
after that the seed bytes, the fingerprint, the alias and every review digest are unchanged, and that the copy
|
||||
differs only in the converted categories (`V1-2-6_UX_TESTS.md` U6).
|
||||
- New-sheet defaults, still to ratify (blocks U6): ids `cat-bone`, `cat-joint`, `cat-vertebra`, chosen by the core
|
||||
- New-sheet defaults, ratified (brief U0, BDR-101): ids `cat-bone`, `cat-joint`, `cat-vertebra`, chosen by the core
|
||||
(suffixes of 4 to 8 characters, so never a page id `cat-<10 chars a-z2-7>`, `apps/app/src/editor/ids.ts:1-21`);
|
||||
names FR « Os », « Articulations », « Vertèbres » (validated on board 07, `docs/design/v1-2-6/ARBITRAGES.md:60`),
|
||||
EN « Bones », « Joints », « Vertebrae » (proposal); default colours `#a41e65`, `#ff9500`, `#e100ff`, copied from the
|
||||
equine categories (copying mutates nothing) and shown as « Couleur d'origine » (board 07 A). Names stay stored, so
|
||||
old readers show them.
|
||||
French names « Os », « Articulations », « Vertèbres » (validated on board 07, `docs/design/v1-2-6/ARBITRAGES.md:60`).
|
||||
English names and reference colours, documented from the existing data:
|
||||
|
||||
| Id | FR | EN | Colour | Source |
|
||||
|---|---|---|---|---|
|
||||
| `cat-bone` | Os | Bones | `#a41e65` | equine category `os`: « Os » / « Bones », `#a41e65` (`supabase/seed/anatomical-sheets/equine/draft/document.json:425-430`) |
|
||||
| `cat-joint` | Articulations | Joints | `#ff9500` | equine category `articulations`: « Articulations » / « Joints », `#ff9500` (`document.json:417-422`) |
|
||||
| `cat-vertebra` | Vertèbres | Vertebrae | `#e100ff` | colour of the equine category `zone-colonne` (« Segments vertébraux » / « Vertebral segments », `document.json:441-446`), the one T6 proposes for the vertebra role; no existing category is named « Vertèbres », and EN « Vertebrae » is the existing dictionary pair of the editor tab (`apps/app/src/i18n/fr.ts:1230` « Vertèbres », `en.ts:1199` « Vertebrae ») |
|
||||
|
||||
The colours come from the curated draft, which is the historical sheet's document; the legacy import holds none
|
||||
(`legacy-import/document.json`, every category colour `null`). Copying a value mutates nothing. The colours are shown as
|
||||
« Couleur d'origine » (board 07 A). Names stay stored, so old readers show them.
|
||||
|
||||
## T6 · Equine working copy conversion (V1-2.8)
|
||||
|
||||
@@ -200,7 +216,7 @@ the direct SVG interactions validated by the owner on 2026-11-05 are not reopene
|
||||
neither keep nor reposition, only « Annuler »: stricter than today's attach, which accepts it (stated in U5).
|
||||
- Labels: the owner's French words above; EN « Keep positions », « Reposition annotations », « Cancel » proposed.
|
||||
|
||||
## T10 · Automatic access to a detail view (principle ratified)
|
||||
## T10 · Automatic access to a detail view (ratified: option B)
|
||||
|
||||
- Owner answer: prefer a system navigation type distinct from the visible anatomical taxonomy; check the existing
|
||||
schema constraints before choosing an internal id or category; never categorise this access arbitrarily as Os,
|
||||
@@ -227,8 +243,14 @@ the direct SVG interactions validated by the owner on 2026-11-05 are not reopene
|
||||
category (the role is stripped from snapshots, T7). The editor lists it in no category panel and no picker;
|
||||
only detail triggers use it (an edit refusal and a verdict issue for an observable annotation in it, and for a
|
||||
second category with that role).
|
||||
- Recommendation: (B). It needs the owner's confirmation: a fourth role value and an internal category go beyond
|
||||
the T2 approval, and its names are visible to old readers.
|
||||
- Owner answer, brief U0 (BDR-101): option B validated: internal category `cat-access`, role `navigation`, not
|
||||
visible as an anatomical category, automatic access conditional on U6. Its names and colour are those written in
|
||||
option B above. Creation path (implementer, to keep the editor rule of T4 whole): `navigation` is never given to,
|
||||
changed on or cleared from a category by an edit; the canonical `cat-access` enters a document only inside the
|
||||
core-built automatic-access batch, accepted while no navigation category exists. Limit kept in view: old readers
|
||||
and N-1 show it as an ordinary category (its names are visible there).
|
||||
- Open point for U6 (not decided at U0, owner question if it is visible): the category of an access placed by hand
|
||||
from the view's menu after U6, when the overlap list is not empty. Until U6 the editor chooses it explicitly.
|
||||
- Effect on the plan: automatic access moves from U5 to U6 (it needs the role). U5 keeps the name proposal and the
|
||||
overlap list. Until U6, « Ajouter un accès » (U4) asks the editor for the category as level 1 does: an explicit
|
||||
choice by the editor, never an automatic one. Existing triggers keep their category (the equine « Tête » access
|
||||
@@ -271,7 +293,8 @@ the direct SVG interactions validated by the owner on 2026-11-05 are not reopene
|
||||
- U7 is blocked until the owner supplies the FR and EN text, its source, and who validated it and when. The commit
|
||||
that adds the text cites that record. Until then no such wording is written in the application, the dictionaries
|
||||
or the docs; U7's tests use a fixture text marked as a test value, kept under `tests/`, never shipped.
|
||||
- Contract §7.4 amended at U0 to state this, without any normative wording.
|
||||
- Contract §7.4 amended at U0 to state this, without any normative wording (brief U0: U7 stays blocked until the
|
||||
source and the legal content are validated).
|
||||
|
||||
## T14 · Multi-tab notice (open)
|
||||
|
||||
@@ -280,10 +303,23 @@ the direct SVG interactions validated by the owner on 2026-11-05 are not reopene
|
||||
- Recommendation: out of V1-2.6, tracked as a follow-up. If kept later: heartbeat-based (a crashed tab never says
|
||||
goodbye), wording consistent with « Garder ma version ».
|
||||
|
||||
## T15 · « Annuler » wording (open, needed by U1)
|
||||
## T15 · « Annuler » wording (ratified)
|
||||
|
||||
- Recommendation: keep the validated label; give the header button the accessible name and tooltip « Annuler la
|
||||
dernière modification » / « Undo the last change ».
|
||||
- Owner answer, brief U0 (BDR-101): distinguish the commands. « Annuler la dernière modification » for the history;
|
||||
« Abandonner » or « Abandonner les modifications » for a form.
|
||||
- Applied at U1 and later:
|
||||
- history command: the header button keeps the drawn icon and short label of the approved boards; its accessible
|
||||
name and tooltip are « Annuler la dernière modification » (EN « Undo the last change », proposed); the toast
|
||||
after a gesture undoes the same entry under the same name;
|
||||
- leaving a staged form without applying it (board 02 pending point, board 07 states, board 08 rectangle, board 09
|
||||
regions): « Abandonner »;
|
||||
- returning the draft to its last saved revision (level-1 C11, today `editor.draft.discard` « Annuler les
|
||||
modifications », `apps/app/src/i18n/fr.ts:1238`): « Abandonner les modifications »; its confirmation already
|
||||
uses those words (`fr.ts:1240`);
|
||||
- the trace strip of board 04 already reads « Abandonner ».
|
||||
- Not covered by the answer and unchanged: « Annuler » on dialogs that close without any effect (confirmations,
|
||||
the cleaning dialog, the T9 dialog's third action, which the owner named « Annuler »). Any change there is an owner
|
||||
question, not an implementer choice.
|
||||
|
||||
## T16 · Curve handle editing (ratified: deferred to the curves lot)
|
||||
|
||||
@@ -296,14 +332,18 @@ the direct SVG interactions validated by the owner on 2026-11-05 are not reopene
|
||||
sheet and its working copy derive from them.
|
||||
- Journeys that write geometry: creation makes points and polygons only (`apps/app/src/editor/annotations/creation.ts:90-97`);
|
||||
the editable geometries are circle and polygon (`geometryEdit.ts:9`, `34`); package import, zones from the
|
||||
drawing's shapes and curve drawing are level 2 (contract §8.3, `V1-2_ANATOMICAL_SHEETS.md:1328-1338`).
|
||||
drawing's shapes and curve drawing are level 2 (contract §8.3).
|
||||
- Journeys that meet a path: display by the core layer; the attach repair returns a path unchanged and keeps the
|
||||
attach refused, document unchanged byte for byte (`repair.ts:55-69`, blocked ids `95-100`, C45, `editor-geometry.spec.ts:317`);
|
||||
« Remplacer par un polygone » (`PropertiesPanel.tsx:138`, contract §8.3).
|
||||
- Not inspected: the database contents of DEV and of the sandbox (docs-only brief, no query run). A path there can
|
||||
only come from a direct RPC save or a test fixture. Before U6 or U8 reaches any environment beyond the throwaway sandbox, a
|
||||
read-only count of path geometries in its drafts and published versions is run, by the owner or under an explicit authorisation; a
|
||||
non-zero count reopens T16.
|
||||
only come from a direct RPC save or a test fixture. Before the new model is activated on an environment (its U6
|
||||
write lock lifted there), and before U6 or U8 reaches any environment beyond the throwaway sandbox, a read-only
|
||||
count of path geometries in its drafts and published versions is recorded; on the throwaway sandbox U6 runs it
|
||||
itself, on DEV and any shared environment the owner runs it or authorises it explicitly, never during U0 (brief
|
||||
U0); a non-zero count reopens T16.
|
||||
- Re-checked at U0 (2026-11-05, `a505b24`): same counts (seed draft 22 circles, 6 polygons, 0 paths; legacy import
|
||||
21, 6, 0); `pnpm r5:import-equine --check` clean (0 differences).
|
||||
- Conclusion: the condition holds for every tracked document and every product journey; the deferral is adopted.
|
||||
- Guarantee until the curves lot:
|
||||
- a stored path keeps its `d` text byte for byte; no TypeScript parses it (C45); no operation moves, scales,
|
||||
@@ -312,13 +352,34 @@ the direct SVG interactions validated by the owner on 2026-11-05 are not reopene
|
||||
remap (`remap.path`), the U2 handle layer and zone move (a path gets no handle and no move);
|
||||
- « Remplacer par un polygone » is the one way a path leaves a document: the editor draws a new polygon by hand,
|
||||
one undo entry, published versions untouched. It replaces the curve by the editor's choice; nothing converts
|
||||
it. It stays as ratified in contract §8.3 unless the owner removes it.
|
||||
it. Owner, brief U0 (BDR-101): kept only as an explicit replacement, validated, the old path kept until success,
|
||||
undo and redo supported, no automatic destructive conversion (contract §8.3 as amended). Level 1 already holds
|
||||
it: the trace closes into one `update` committed under the geometry accept, a refusal drops the trace and leaves
|
||||
the annotation unchanged (`apps/app/src/editor/annotations/usePlacement.ts:39-63`, `annotationCommit.ts:55-72`,
|
||||
`93-104`); tests cover the replacement and the refusal (`apps/app/tests/unit/editor-annotations-tab.test.tsx:692-714`,
|
||||
`845-866`). Not yet tested: undo and redo restoring the exact `d`, and Escape during the trace; added at U2
|
||||
(`V1-2-6_UX_TESTS.md` U2, « Paths » row).
|
||||
- Future lot « Courbes » (ex-U9): specification in `V1-2-6_UX_PLAN.md` §2 D, tests in `V1-2-6_UX_TESTS.md`
|
||||
(« Curves lot »), with the path point-correction proposal. Recorded in TODO.md with its dependency rule: no
|
||||
feature that lets a path enter a document (package import, zones from the drawing's shapes, a curve drawing tool)
|
||||
ships before or without it. It needs a size lever (T1) and a round-withdrawal migration.
|
||||
|
||||
## T17 · Vertebral regions entry without a vertebra role (open, needed by U6)
|
||||
## Points from the boards for U1 and later (found at U0, not decided)
|
||||
|
||||
The validated boards show these; level 1 or its contract says otherwise. Each involves a visible choice or another
|
||||
step's scope, so it is an open owner question, asked when the sub-step that builds it is planned; until then the
|
||||
level-1 text stays as written (precedence rule of the level-1 contract header). None blocks U0.
|
||||
|
||||
| Point | Boards | Level 1 or contract | Sub-step |
|
||||
|---|---|---|---|
|
||||
| « Prévisualiser » in the editor header | 01 to 05, 07 to 11, 13 | deferred to V1-2.7 (level-1 CLARIFICATIONS; contract §16.8) | U1 planning: owner question (V1-2.7 is not open) |
|
||||
| Withdrawing a submission from the Vérification tab | 12 C notice | withdrawal deferred to V1-2.7 (same) | U1 planning: owner question |
|
||||
| Recovery buttons « Restaurer » / « Ignorer » | 12 D | C27: « Restaurer la copie » / « Ignorer la copie » | U1 label review |
|
||||
| Properties at creation of points and zones: names and laterality asked before the element exists, no preselected laterality | 02, 04 (laterality and other properties set after creation) | level-1 plan choice 2 (C25), `apps/app/src/editor/annotations/creation.ts:48-56`, `109`; the core requires a laterality (`crates/core/src/domain/sheet/schema.rs:424`, `450`), so the boards' flow implies a default | U2 planning: owner question (detail-view names are not open: choice 6, proposed name, U5) |
|
||||
| Region code read-only after creation | 09 (not legible) | C5: read-only after creation | U6 planning |
|
||||
| Category of an access placed by hand after U6 when annotations overlap | 08 | T10 section above | U6 planning |
|
||||
|
||||
## T17 · Vertebral regions entry without a vertebra role (open, blocks U6, not U0)
|
||||
|
||||
- Facts: board 09 opens the regions from the Vertèbres category; the equine working copy has no role before V1-2.8.
|
||||
- Recommendation: when no category carries the vertebra role, the Annotations panel keeps a « Régions
|
||||
|
||||
Reference in new issue
Block a user