docs(docs): V1-2.6 annotations-findings complement, boards 17-22, study
Owner brief: bidirectional navigation between annotations and findings. Relations audit (one finding_zone_id link, no new association), six boards from the equine draft data, placement U2b, risks, tests, owner decisions F1-F16. Design only; U1 plan untouched.
This commit is contained in:
1 parent
2e46c14697
commit
212126c6ce
15 files changed
+1002
No files matched your search
@@ -681,6 +681,7 @@ Order (BDR-071): P0 docs + decisions → V1-1 clients and animals → V1-2 sheet
|
||||
- [x] static audits (core model, rendering/PDF/N-1, geometry/wasm, SQL/worker, editor/tests) · [x] docs/development V1-2-6_UX_{PLAN,COMPATIBILITY,TESTS,RISKS,DECISIONS}.md (sub-steps U0-U9, decisions T1-T19) · [x] independent review (3 lenses: CONCERNS 5/9/6, no BLOCKER) + fixes integrated (plan §6) · [x] commit + push branch · [x] owner answers 2026-11-05 (brief « V1-2.6 UX — Ratification des décisions techniques », BDR-100): T11 approved, T16 conditional deferral (curves lot), T2/T3 conditional on proofs, T4 no residual gap, T5 history preserved, T9 three actions, T10 navigation type, T12 principle · [x] five docs updated (decisions, compatibility §0/§7/§8, tests, risks + blocking criteria, plan §7) · [x] LRN-118 (wasm measuring rule) · [x] independent reviews: correctness challenger CONCERNS(5 MAJOR, 7 MINOR) integrated; verifier ECARTS(2) fixed; targeted re-check ECARTS(2) (one U6 test assumed permissive save, deploy order said all rounds) fixed · [x] third independent check before commit (2026-11-05): ECARTS(2) on K10/K11 (R-3 mitigation, U6 objective on older T4 scope, write-lock test assumed stripping save, T16 count scope in two forms) fixed · [x] fresh targeted re-check: CONFORME 12/12 (G1-G4 closed; 7 observations kept for U0) · [x] commit + push · [x] owner answers 2026-11-05 (brief « Autorisation U0 uniquement », BDR-101): T4 both SQL checks approved (O22 amended), T5 defaults, T10 option B, T15, T16 count before activation, « Remplacer par un polygone » explicit · [x] T17 answered 2026-11-06 (BDR-102) · [ ] still open: T12 text (before U7), T6 (V1-2.8), T14 follow-up; T1 only if a measure exceeds · [x] owner authorisation to start U0 (2026-11-05)
|
||||
- [ ] V1-2.6 UX U0, contract and decisions, docs only (contract `.claude/tasks/contracts/2026-11-05-v1-2-6-ux-u0.md`; no code, no SQL, no DEV, no U1): [x] V1-2 contract §6.2, §6.4, §6.7, §7.4, §8.2-§8.4, §12.2 + §17.1 (O22), §16.7, §16.12, §17.12 · [x] level-1 contract C3, C4, C5, C6, C7, C8, C11, C13, C16, C18, C20, C25, C28, C32, C33, C40, with the precedence rule of its header · [x] docs/design/README.md · [x] rules sheet-model.md, schemas.md · [x] five UX docs · [x] BDR-101 · [x] preconditions (r5:import-equine --check clean, seed 22/6/0 paths, wasm 592 143 B) · [x] independent verification: ECARTS x6 fixed, then CONFORME 12/12 (2026-11-06); open points for U2/U6 not in docs: point edge-size handle (boards 02/03), default laterality of the automatic access (U6), §15 replay text vs the category.fixed.* filter · [x] commit + push · [x] owner U0 checkpoint (approved for good in the brief « Autorisation de U1 uniquement », 2026-11-06)
|
||||
- [ ] V1-2.6 UX U1, editor shell (brief « Autorisation de U1 uniquement » + « U1 — Validation de la conception interne », approach A; contract `.claude/tasks/contracts/2026-11-06-v1-2-6-ux-u1-1123.md`; plan `.claude/tasks/plans/2026-11-06-v1-2-6-ux-u1.md`, lots A, B1, B2, C-I; no Rust/SQL/worker/scripts, no DEV, no merge, no U2): [x] design approach A validated by the owner with 10 precisions · [x] owner choices 2026-11-06 (server save time, non-modal references panel, citation button in the finding's detail, board 01 annotation card) · [x] plan written + three-lens challenge (correctness CONCERNS 6, robustness CONCERNS 5, simplicity CONCERNS 2, no BLOCKER) integrated · [ ] owner plan checkpoint · [ ] lots A-I · [ ] gates, verifier, security · [ ] owner U1 checkpoint
|
||||
- [ ] V1-2.6 UX complement « annotations ↔ constats » (owner brief 2026-11-06 « Nouvelle exigence UX : navigation bidirectionnelle »; contract `.claude/tasks/contracts/2026-11-06-v1-2-6-findings-nav-design.md`; design only, U1 plan untouched, no code, no DEV): [x] relations audit (one link `finding_zone_id`, no new association, equine draft 1:1) · [x] boards 17-22 `docs/design/v1-2-6-constats/` · [x] study `docs/development/V1-2-6_UX_FINDINGS_NAV.md` (no U1 integration point needed, sub-step U2b proposed, risks, tests, decisions F1-F16) · [x] fresh design review APPROVE WITH FIXES (3 MUST-FIX, 16 SHOULD), fixes applied · [ ] fresh verifier (ECARTS(4) round 1 fixed) · [ ] owner validation of the complement (then F1-F12)
|
||||
- [ ] follow-up candidates (owner T14): multi-tab notice; RR item for the rollback limit of the category model (new id, reconcile with develop)
|
||||
- [ ] curves lot (ex-U9, owner T16 2026-11-05): curve handle editing, curved zone move, path remap, path point correction; spec `V1-2-6_UX_PLAN.md` §2 D, tests `V1-2-6_UX_TESTS.md` « Curves lot ». 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. Before the new model is activated on an environment, and before U6 or U8 reaches any environment beyond the throwaway sandbox: read-only count of path geometries in its drafts and published versions (sandbox by U6 itself; DEV and shared environments by the owner or under explicit authorisation; non-zero reopens T16)
|
||||
- [ ] MANDATORY before merging V1-2 into develop (owner 2026-11-03): registry id reconciliation. LRN-095 collides: develop 09655b2 « Port a safe runner verbatim… » (2026-11-02) vs V1-2 « pgTAP across PGlite and the real Supabase image… » (2026-10-28, cited by BDR-084 and the V1-2.1 TODO lines). BLK-013 exists on develop only (« e2e:avatar on develop reached DEV »): `memory.sh` on V1-2 would hand out BLK-013 again, so a V1-2 blocker needs its id checked against develop first. Same for the TODO release-readiness ids: RR-11 is develop's (« sandbox-only e2e follow-ups »), V1-2 uses RR-12. No renumbering during V1-2.6 unless needed; renumber one side and patch its citers at the merge
|
||||
|
||||
@@ -0,0 +1,125 @@
|
||||
# CONTRACT — v1-2-6-findings-nav-design
|
||||
- date: 2026-11-06 | flow: design complement (docs and mockups only) | branch: feature/v1-2-anatomical-sheets
|
||||
- status: active
|
||||
- worktree: /home/bchanot/Documents/faunosteo-v1-2 (every command from this absolute path; never DEV: the
|
||||
`supabase_*_faunosteo` containers are DEV; no sandbox needed for this track)
|
||||
- base: 2e46c14 (U1 contract and challenged plan, awaiting the owner's plan checkpoint). Commit in place, push; no
|
||||
merge, no `gitflow.sh finish`.
|
||||
- context: the U1 plan `.claude/tasks/plans/2026-11-06-v1-2-6-ux-u1.md` stays as committed; this track may only
|
||||
PROPOSE a named amendment to it, applied after the owner's approval.
|
||||
|
||||
## REQUEST (verbatim — IMMUTABLE)
|
||||
|
||||
avant, demande de modification ou detail a apporter :
|
||||
|
||||
# FAUNOSTEO — Nouvelle exigence UX : navigation bidirectionnelle entre annotations et constats
|
||||
|
||||
Le propriétaire ajoute une exigence fonctionnelle aux maquettes validées.
|
||||
|
||||
Cette demande ne doit PAS interrompre le plan U1 actuellement en cours, ni provoquer une implémentation prématurée.
|
||||
|
||||
## Fonctionnement souhaité
|
||||
|
||||
### A. Depuis le schéma anatomique
|
||||
|
||||
Lorsqu'un utilisateur sélectionne un point ou une zone du SVG :
|
||||
|
||||
- Afficher les constats associés à cette annotation anatomique.
|
||||
- Permettre d'ajouter un constat depuis cette sélection.
|
||||
- Permettre de modifier les constats existants.
|
||||
- Permettre de gérer leur association anatomique.
|
||||
- Conserver les familles de constats du modèle existant.
|
||||
|
||||
Exemple : sélectionner le grasset affiche les constats associés au grasset.
|
||||
|
||||
### B. Depuis l'onglet Constats
|
||||
|
||||
Ajouter :
|
||||
- Une barre de recherche avec filtrage instantané.
|
||||
- Un compteur de résultats.
|
||||
- Un bouton « Filtrer sur le schéma ».
|
||||
- Un volet permettant de choisir une ou plusieurs vues anatomiques.
|
||||
- La sélection graphique de points ou de zones pour filtrer les constats.
|
||||
- La combinaison du filtre visuel et de la recherche textuelle.
|
||||
- Une action pour réinitialiser les filtres.
|
||||
|
||||
Les filtres sont des états d'interface : ils ne doivent pas modifier ni sauvegarder le document.
|
||||
|
||||
### C. Correspondance anatomique
|
||||
|
||||
Auditer les relations existantes entre annotations, vues, zones de constats et constats.
|
||||
|
||||
Éviter les doublons lorsque plusieurs annotations représentent une même région anatomique.
|
||||
|
||||
Ne pas inventer de nouvelles associations dans le modèle sans démontrer qu'elles sont nécessaires.
|
||||
|
||||
### D. Contraintes
|
||||
|
||||
- Respecter les autorisations existantes.
|
||||
- Préserver le mode lecture seule sur téléphone en V1-2.
|
||||
- Préserver le fonctionnement du cœur Rust et la compatibilité historique.
|
||||
- Rendre les sélections et filtres accessibles au clavier.
|
||||
- Ne pas modifier la structure documentaire sans validation spécifique.
|
||||
|
||||
## Travail demandé
|
||||
|
||||
Après finalisation du plan U1 actuel :
|
||||
|
||||
1. Examiner si l'architecture U1 doit prévoir des points d'intégration pour cette fonctionnalité.
|
||||
2. Identifier dans quelle sous-étape UX elle doit être implémentée, ou proposer une sous-étape dédiée.
|
||||
3. Produire un complément de maquettes ciblé sur ces interactions.
|
||||
4. Documenter les risques techniques et les tests nécessaires.
|
||||
5. S'arrêter à la validation de cette conception complémentaire.
|
||||
|
||||
Aucun code ne doit être modifié pour cette nouvelle fonctionnalité avant approbation.
|
||||
|
||||
Ne pas toucher à DEV, ne pas fusionner et ne pas commencer V1-2.7.
|
||||
|
||||
## CLARIFICATIONS
|
||||
(none yet; owner questions are listed in the study's « Décisions à prendre » section, never answered by the
|
||||
implementer)
|
||||
|
||||
## ACCEPTANCE CRITERIA
|
||||
1. Audit (request C): the study `docs/development/V1-2-6_UX_FINDINGS_NAV.md` states, with file:line references, every
|
||||
existing link between annotations, views, finding zones, finding categories (families), findings, vertebral
|
||||
regions and references, which side holds it and its cardinality, the core rules that check it, and counts from
|
||||
the equine draft document (annotations per zone, zones without annotation, annotations without zone, zones shown
|
||||
by several annotations); a new association in the model is proposed only with a demonstrated need, and flagged as
|
||||
requiring the owner's specific validation.
|
||||
2. Duplicates (request C): the study and the boards say how findings are shown once when several annotations name the
|
||||
same finding zone (both directions: from the drawing and in the schematic filter).
|
||||
3. U1 integration (work item 1): the study says whether U1 needs integration points; any needed one is a named
|
||||
amendment proposal for `.claude/tasks/plans/2026-11-06-v1-2-6-ux-u1.md`, not applied; the U1 plan and contract
|
||||
are unchanged by this track.
|
||||
4. Placement (work item 2): the study names the sub-step that implements the feature (or a dedicated one), with its
|
||||
dependencies on U1-U6, the files it would touch, whether it needs a Rust core operation (BDR-043, « Rust computes,
|
||||
TypeScript reads ») and the wasm budget effect.
|
||||
5. Boards (work item 3): a targeted complement in `docs/design/v1-2-6-constats/` (HTML source + one PNG per board,
|
||||
rendered with the project's pinned Chromium through the v1-2-6 `render.cjs` pattern), in the validated v1-2-6
|
||||
visual language, covering: A — an annotation selected on the drawing shows its findings by family, add from the
|
||||
selection, edit, manage the association; B — Constats tab with instant search, result count, « Filtrer sur le
|
||||
schéma », a panel choosing one or more views, graphical selection of points or zones, combined text and visual
|
||||
filter, reset; and the states: read-only (rights, frozen) and narrow read-only below 1 024 px, keyboard
|
||||
alternative to the graphical selection, no result, an annotation without finding zone, a zone shown by several
|
||||
annotations. Names and counts come from the equine draft document, computed in the source, never typed.
|
||||
6. Risks and tests (work item 4): the study lists the technical risks (with probability and mitigation) and the tests
|
||||
per kind (unit, core if any, e2e, accessibility, regression) for the feature.
|
||||
7. Constraints: no change under `apps/`, `crates/`, `supabase/`, `packages/`, `scripts/`, `docs/design/v1-2-6/`;
|
||||
filters described as interface state only (no document change, no save); permissions, phone read-only (O14 A),
|
||||
the core and the historical documents unchanged by the design; no V1-2.7 control; the untracked
|
||||
`faunosteo-v1-2-6-revue-ux-chatgpt.md` never staged.
|
||||
CHECK: cd /home/bchanot/Documents/faunosteo-v1-2 && git diff --quiet 2e46c14..HEAD -- apps crates supabase packages scripts docs/design/v1-2-6 && git diff --quiet -- apps crates supabase packages scripts docs/design/v1-2-6 && ! git ls-files --error-unmatch faunosteo-v1-2-6-revue-ux-chatgpt.md >/dev/null 2>&1 && echo FN_SCOPE_OK
|
||||
EXPECT: FN_SCOPE_OK
|
||||
EVIDENCE: MET exit=0 marker-found :: FN_SCOPE_OK
|
||||
8. Every visible choice the design makes beyond the request is listed in the study for the owner (« Décisions à
|
||||
prendre »), with a recommendation; none is presented as decided.
|
||||
9. A fresh independent review of the boards (design) and a fresh verifier against this contract; justified gaps
|
||||
fixed; exact verdicts reported. STOP at the validation of this complementary design.
|
||||
|
||||
## FILE SCOPE
|
||||
- docs/design/v1-2-6-constats/** (new: maquettes.html, PNG boards, contact sheet, REVUE.md)
|
||||
- docs/development/V1-2-6_UX_FINDINGS_NAV.md (new study)
|
||||
- docs/design/README.md (one pointer line to the complement, marked « proposition, non validée »)
|
||||
- .claude/tasks/TODO.md, this contract, .claude/memory (through memory.sh)
|
||||
- NOT in scope: apps/**, crates/**, supabase/**, packages/**, scripts/**, docs/design/v1-2-6/**, the U1 plan and
|
||||
contract, the V1-1 checkout
|
||||
Reference in new issue
Block a user