chore(memory): V1-2.6 owner GO, C26 repair rules, C32-C34

This commit is contained in:
bchanot committed 2026-11-04 11:32:18 +01:00
1 parent f34381c242
commit 2571978780
4 files changed
+93 -22

No files matched your search

@@ -172,6 +172,13 @@ while a recovery offer is unanswered (« Restaurer la copie » / « Ignorer la c
N from `draft_version.revision`, author and date from `draft_last_save`, failed read → « Recharger » / « Réessayer »,
« Garder ma version » disabled; two-copy cap kept with no automatic eviction of an unresolved copy; AAL2 residual
risk recorded, not fixed; second targeted re-check, then execution without a new authorisation if conforming.
Q: Re-check REMAINING(1) (F1 unmeasured views; C26 refinement for annotations already out; minor effects) / A:
[gated 2026-11-04] owner brief « GO propriétaire après REMAINING(1) »: F1 fix approved; C26 refined by seven
repair rules (new annotation valid before integration; a valid annotation never made invalid; an annotation
already out repairable; intermediate values kept in the form; geometry applied only when the whole satisfies the
core; no diagnostic hidden; a frame change never silently invalidates); 4 px drag threshold, unreadable copy kept
with « Ignorer la copie » naming the loss, leave guard while a decision is pending and not after; execution of
lots A-M authorised without a third plan review; stop on a blocking defect or a contractual impossibility.
## ACCEPTANCE CRITERIA
@@ -281,7 +288,7 @@ checked across develop, main, feature/v1-1, feature/v1-2: next free were BDR-099
annotation `out_of_frame` (rolled back before anything is kept); the decision is the core's report, TypeScript
holds no copy of the frame or size rules; Node-core unit tests cover 40×30, 20×20, 100×300, very elongated
frames, non-zero origins, clicks on edges and corners, equality at the edge, 0.01 rounding and large
coordinates.
coordinates. (Refined by 33: the commit rule covers every geometry error, not only `out_of_frame`.)
27. [gated 2026-11-03] A recovery offer left unanswered blocks every document change: the store refuses commit,
undo, redo, save and submit, and the copy is neither written nor removed; consultation stays; « Restaurer la
copie » goes through the core and keeps the copy's base revision as the expected revision (`staleBase` when
@@ -305,6 +312,26 @@ checked across develop, main, feature/v1-1, feature/v1-2: next free were BDR-099
session, until the token expires after a factor removal) written in the V1-2 contract §13 as a production
prerequisite, not declared fixed, no authentication change in V1-2.6; the LRN-095 and BLK-013 id collisions
with develop recorded for the reconciliation before the merge, registries not renumbered.
32. [gated 2026-11-04] Unmeasured views (no accepted drawing, or `view.frame.unknown` for the view): drawing tools,
keyboard « Ajouter … » buttons and numeric geometry fields disabled with the hint naming « Vues et
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.
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
fields form one group held in the form and applied whole, refused values stay shown as not applied with the
core's message and a way back to the stored values; an annotation already invalid is repaired that way and
its error stays visible until the fix is applied; a frame change (`view_box`, drawing) is refused when an
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.
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
owner trial guide `docs/development/V1-2-6_OWNER_TRIAL.md` covers non-equine creation, SVG import, points,
zones and links, geometry correction, save and restore, two-tab concurrency and submission; the checkpoint
gives HEAD, commits, test and audit results.
## FILE SCOPE