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

+3
View File
@@ -517,3 +517,6 @@ R5.4: `draft/{labels,changelog,review_report,drawing,overlay,app_review,svg_comp
- 2026-11-03 owner accepted V1-2.5 final checkpoint b4415a3 (V1-2.5 VERIFIED): BDR-099 decisions, LRN-113 TOTP reuse/Storage 409/sandbox order. V1-2.6 editor level 1 authorised (brief « Validation V1-2.5 et autorisation V1-2.6 »).
- 2026-11-03 V1-2.6 owner GO conditional on six FATAL re-check. Fresh verifier: REMAINING(2): fixes 1-5 closed, I1-I5 hold; radius fix 6 opens out_of_frame on small frames; I6 broken (pending recovery copy overwritten by first commit). 2 MINOR. LRN-095 collision + BLK-013 trap in TODO. Executor not launched, STOP.
- 2026-11-03 V1-2.6 owner arbitrations on REMAINING(2) integrated (C25-C31, AAL2 risk V1-2 §13 + RR-12, RR-11 collision noted). Second fresh re-check REMAINING(1): F1 accept trusted core silence on unmeasured views (no drawing / no usable frame); 7 MINOR. All integrated in plan; C26 refinement for inherited out-of-frame edits awaits owner. Executor not launched, STOP.
## 2026-11-04
- V1-2.6 owner GO after REMAINING(1): F1 approved, C26 refined (7 repair rules: commit only when changed annotation error-free after; form group applied whole; frame change never invalidates silently), C32-C34 gated. Execution lots A-M starts.
+1 -1
View File
@@ -671,7 +671,7 @@ Order (BDR-071): P0 docs + decisions → V1-1 clients and animals → V1-2 sheet
- [x] L2 expiry end of day Europe/Paris, species order 0..9 999 in M7, labels, TOTP key test: app 696, supabase 148, pgTAP 1965 fresh + upgrade, types match
- [x] L3 TOTP reuse measured (code accepted by several sessions in its step and the next, refused at N+2), lost-authenticator review (production prerequisite), decisions in docs; sandbox test 103 + 10 skipped x2
- [x] L4 gates: check:all green (dcb1a94; delta = sandbox test + docs), fresh stack test-db 1965, e2e:shell 110 + 8 skipped, sandbox test 103 + 10 skipped after e2e, upgrade from M6 1965 + types match; security PASS x2; verifier ECARTS(6) -> CONFORME; two state-dependent sandbox tests fixed (0499a39, f5456f3); suites need a fresh stack in order test-db, e2e:shell, test
- [ ] V1-2.6 editor level 1: plan APPROVED by the owner 2026-11-03 (brief « GO propriétaire V1-2.6 »: 13 lots A-M, C1-C24, 8 visible choices, M8 sandbox only, no JSON export button, recovery messages exact), gated on a targeted independent re-check of the six FATAL fixes. Re-check 2026-11-03: REMAINING(2) — fixes 1-5 closed, I1-I5 hold; fix 6 (r = 12 + 3 %) opens `out_of_frame` on frames under ~25.5 units (hitbox r in frame bounds); I6 broken: the first commit overwrites a pending recovery copy before « Restaurer » / « Ignorer »; 2 MINOR (N source when the admin read fails, two-copy cap). Executor NOT launched; STOP for the owner. Owner arbitrations 2026-11-03 (« arbitrages propriétaire sur REMAINING(2) »): C25-C31 gated, plan revised; second targeted re-check: REMAINING(1), no BLOCKER, F1 MAJOR (accept trusted the core's silence on unmeasured views) + 7 MINOR, all integrated in the plan; C26 refinement awaits the owner; executor NOT launched, STOP. Contract `.claude/tasks/contracts/2026-11-03-v1-2-6-editor-1509.md`, plan `.claude/tasks/plans/2026-11-03-v1-2-6-editor.md`; sandbox only, no DEV, no worker on DEV, no merge, no V1-2.7; STOP at the V1-2.6 owner checkpoint (trial procedure)
- [ ] V1-2.6 editor level 1: plan APPROVED by the owner 2026-11-03 (brief « GO propriétaire V1-2.6 »: 13 lots A-M, C1-C24, 8 visible choices, M8 sandbox only, no JSON export button, recovery messages exact), gated on a targeted independent re-check of the six FATAL fixes. Re-check 2026-11-03: REMAINING(2) — fixes 1-5 closed, I1-I5 hold; fix 6 (r = 12 + 3 %) opens `out_of_frame` on frames under ~25.5 units (hitbox r in frame bounds); I6 broken: the first commit overwrites a pending recovery copy before « Restaurer » / « Ignorer »; 2 MINOR (N source when the admin read fails, two-copy cap). Executor NOT launched; STOP for the owner. Owner arbitrations 2026-11-03 (« arbitrages propriétaire sur REMAINING(2) »): C25-C31 gated, plan revised; second targeted re-check: REMAINING(1), no BLOCKER, F1 MAJOR (accept trusted the core's silence on unmeasured views) + 7 MINOR, all integrated in the plan. Owner GO 2026-11-04 (« GO propriétaire après REMAINING(1) »): F1 fix approved, C26 refined by seven repair rules, minor effects approved; C32-C34 gated; execution of lots A-M authorised, no third plan review. Contract `.claude/tasks/contracts/2026-11-03-v1-2-6-editor-1509.md`, plan `.claude/tasks/plans/2026-11-03-v1-2-6-editor.md`; sandbox only, no DEV, no worker on DEV, no merge, no V1-2.7; STOP at the V1-2.6 owner checkpoint (trial procedure)
- [ ] A M8 draft_last_save · [ ] B sheet asset accessors · [ ] C preview mutators, edit ops, ids · [ ] D editor store, undo, recovery · [ ] E route, modes, tabs · [ ] F Général, Références, Vertèbres · [ ] G views + upload · [ ] H Annotations · [ ] I Constats · [ ] J Vérification + submit · [ ] K e2e · [ ] L owner trial tooling · [ ] M gates, reviews, checkpoint
- [ ] 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
- [ ] V1-2.5 catalogue, admin space, rights, species, MFA · V1-2.6 editor level 1 · V1-2.7 preview, review, publication UI · V1-2.8 equine working copy and review preparation · V1-2.9 FR/EN acceptance and closure (owner checkpoints V1-2.3, V1-2.4, V1-2.6, V1-2.7, V1-2.8, V1-2.9 + each DEV operation of contract §16.11)
@@ -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
+61 -20
View File
@@ -1,7 +1,7 @@
# Plan: V1-2.6 editor level 1 (revised after challenge, 2026-11-03)
Contract `.claude/tasks/contracts/2026-11-03-v1-2-6-editor-1509.md` (criteria C1 to C24, CLARIFICATIONS [gated
2026-11-03]). Branch `feature/v1-2-anatomical-sheets`, worktree
Contract `.claude/tasks/contracts/2026-11-03-v1-2-6-editor-1509.md` (criteria C1 to C34, CLARIFICATIONS [gated
2026-11-03] and [gated 2026-11-04]). Branch `feature/v1-2-anatomical-sheets`, worktree
`/tmp/claude-1000/-home-bchanot-Documents-faunosteo/e641af9a-743e-46d0-9804-99667836040e/scratchpad/v1-2`, base
7f618d0. Sandbox only (`pnpm db:sandbox`, containers `faunosteo_dbsandbox_*`); the `supabase_*_faunosteo`
containers are DEV: never touched, never a target. Every command runs with the worktree as an absolute,
@@ -143,28 +143,54 @@ here; executors write the code and the tests. Reading list for every executor: t
pending point at the click so the user can change its radius or position, or drop it. A refusal of C, or
`too_small` on A or C (r0 already capped: an extremely elongated frame), creates nothing and shows the core's
issue message beside the creation panel.
- Every later geometry commit (move by drag, numeric cx, cy, r or vertex, vertex added or removed, polygon
replacing a path) uses `accept` too: rolled back when the changed annotation was in frame (or new) before the
commit and the core reports it `out_of_frame` after (message « L'élément sortirait du cadre. »). An annotation
already `out_of_frame` before the commit (inherited, restored) may be edited step by step towards the frame,
keyboard included (C7); its error stays in Vérification until it is inside. [Owner approval pending: this
refines C26's « no geometry commit leaves the changed annotation out_of_frame ».] A radius the user types that
the core reports `too_small` is committed and shown in Vérification (an explicit user value, never an
automatic reduction). Zones and links: the creation insert is refused on `out_of_frame` (tracing kept for
numeric correction or cancel).
- Frame changes (a view's `view_box` update, a drawing set or replaced on a view) use `accept` too: refused when
an annotation of that view that was in frame becomes `out_of_frame`, the refusal listing those annotations.
- Geometry errors (owner 2026-11-04, C33): an annotation's geometry errors are the core's Error issues at
`annotations[i].geometry` (`annotation.geometry.missing`, `out_of_frame`, `too_small`, `interior_too_small`),
mapped to the annotation's id through the document of the same state (an insert, a delete or a reorder shifts
the index); « before » is the report of the last accepted state the store holds, « after » the report of the
candidate state. One rule for every geometry commit (creation insert, move by drag, numeric cx, cy, r or
vertex, vertex added or removed, polygon replacing a path): `accept` refuses it unless the changed annotation
carries no geometry error after it, whether it was new, valid or already invalid before (owner rules 1, 2
and 5). A refusal rolls the handle back (no store change, no `handleVersion` bump, no copy write); the message
is the core's issue (« L'élément sortirait du cadre. » for `out_of_frame`). A radius the user types that the
core reports `too_small` is therefore refused, never committed (rule 2). Zones and links: the creation insert
is refused the same way (tracing kept for numeric correction or cancel).
- Repair through a temporary form (owner rules 3 to 5): the geometry fields of the properties panel (cx, cy, r;
the vertex rows; « Ajouter un sommet » / « Retirer ») form one group held in component state. Enter or leaving
a field proposes the WHOLE group as one `update`; accepted → committed; refused → nothing changes in the
document, the fields keep the typed values marked « non appliqué » with the core's issue message and a
« Revenir aux valeurs enregistrées » action. So an annotation already invalid (inherited, restored) is
repaired by typing a coherent set (e.g. cx then cy) applied once it satisfies the core, never through an
invalid intermediate document; its error stays in Vérification and on the properties panel until the fix is
applied (rule 6: no diagnostic hidden, an invalid annotation never shown as valid). Selecting another element
drops an unapplied group (it was never in the document). Drag on an already-invalid annotation follows the
same rule: a drop that leaves it invalid is rolled back with the message. The save path and the server's
verdict are unchanged: a draft that already holds geometry errors saves as before (the core's rules are never
weakened, nothing is added to them) and the submit stays the server's decision.
- Frame changes (a view's `view_box` update, a drawing set or replaced on a view, rule 7) use `accept` too:
refused when any annotation that had no geometry error before has one after, the refusal listing those
annotations; an annotation already invalid does not block it. Refused too when a measured view holding
annotations becomes unmeasured (the core then goes silent on them: their validity would vanish unseen).
- No move without intent: numeric fields show the stored number exactly (no display rounding; the equine draft
holds values such as 743.0451049804688) and commit only when the typed number differs from it; a drag starts
only after the pointer travelled 4 CSS px from the press, so a click with jitter on a selected marker never
moves it.
moves it (owner 2026-11-04: a plain click still selects, the keyboard path is untouched, pointer events serve
mouse, pen and touch alike; the canvas sets `touch-action: none` only while a drawing tool or a drag is
active, so a touch scroll of the page still works otherwise).
- Unmeasured views, read-only geometry (owner 2026-11-04, C32): existing annotations of such a view stay shown
when the canvas can draw them and stay selectable; their properties show geometry as read-only text, drag is
off, and the hint names the « Vues et illustrations » tab where the drawing is fixed. The fallback frame
`0 0 100 100` is never read as a frame: no proposal, no `accept` verdict, no message relies on it.
- Unit tests on the Node core (C26): frames 40×30, 20×20, 100×300 (detail crops), 500×380, 640×480, 200×150, very
elongated 1000×30 and 4000×200, non-zero origins (e.g. `-50 20 40 30`); clicks on each edge, each corner, at
distance exactly r0 and r0 − 0.005 from an edge; coordinates near 2^20; r0 = min(w, h)/2 exactly; a non-grid
origin with r0 = min(w, h)/2; unmeasured views (a crop of span 0.5, a drawing without `viewBox`, a missing
drawing: every creation and geometry commit refused); an inherited out-of-frame point repaired by two numeric
commits; a `view_box` change refused when it pushes a point out; each case asserts the proposal, the core's
verdict on it and that no point is ever kept `out_of_frame` by a page action.
drawing: every creation and geometry commit refused); repair (C33): an inherited out-of-frame point, then
polygon, whose intermediate values (cx only) are refused with the document unchanged and whose coherent set
is applied, a restored copy holding an invalid point repaired the same way; a valid point given a typed
radius the core reports `too_small` refused; a drag dropping a valid point half out rolled back; a `view_box`
change refused when it pushes a point out or makes it `too_small`, accepted when only an already-invalid
point is affected; each case asserts the proposal, the core's verdict on it and that no page action ever
leaves an annotation with a geometry error it did not already have.
- Keyboard path (C7): under the canvas, « Ajouter un point », « Ajouter une zone », « Ajouter un accès » hold a
pending element at the frame centre (zone and link: a triangle of 10 % of the smaller side) and open the
creation panel; then every coordinate is edited in numeric fields (cx, cy, r; rows « n | x | y »; « Ajouter un
@@ -241,7 +267,10 @@ here; executors write the code and the tests. Reading list for every executor: t
`recovery.pending`, not only disabled buttons, keyboard shortcuts included) and the copy subscription neither
writes nor removes. A stored copy that cannot be read (malformed JSON, `v` ≠ 1, `user_id` or `version_id` not
matching its key) is never overwritten: it opens `recovery = refused` with « Ignorer la copie » only (the report
editor's quarantine pattern). The leave guard is armed while unsaved OR while `recovery` is not `none`.
editor's quarantine pattern) and a notice that names the loss (owner 2026-11-04): « Une copie locale de ce
brouillon existe dans cet onglet mais ne peut pas être lue. Elle n'est pas enregistrée sur le serveur.
L'ignorer la supprime de cet onglet : son contenu sera perdu. » (label proposal); kept until that explicit
abandonment, never replaced or removed otherwise; editing stays blocked until then. The leave guard is armed while unsaved OR while `recovery` is not `none`.
Consultation stays: tabs, selection, list, zoom, pan, properties as text (the read-only field components).
Notice under the header: « Une copie locale temporaire de ce brouillon existe dans cet onglet (révision R,
<heure>). Elle n'est pas enregistrée sur le serveur. Choisissez avant de modifier le brouillon. » (+ « Elle est
@@ -286,7 +315,11 @@ here; executors write the code and the tests. Reading list for every executor: t
temporary and limited to this tab: session or MFA lost (`session_expired`, `rights.mfa`) and an unsaveable draft
(`draft.frozen`, `sheet.inactive`, `rights.capability`) say « une copie locale temporaire existe dans cet onglet »
only when the last write succeeded, otherwise that the unsaved changes cannot be kept.
- Leave guard (`useLeaveGuard`) armed while unsaved or while a recovery offer is not answered (`recovery` ≠ `none`).
- Leave guard (`useLeaveGuard`) armed while unsaved or while a recovery offer is not answered (`recovery` ≠ `none`),
disarmed as soon as both are off (a confirmed save, an explicit abandonment); never kept armed otherwise. Its
limits are written in the owner trial guide and BROWSER_TESTS.md (owner 2026-11-04): `beforeunload` is not
reliable on mobile browsers (iOS Safari, a tab killed in the background) and its text is the browser's own; the
sessionStorage copy is the only fallback there and dies with the tab.
### Upload (§9.2-§9.3)
- File input (`.svg`, `image/svg+xml`), size ≤ 2 MiB checked before reading; bytes → `clean_svg`. `rejected` →
@@ -340,7 +373,7 @@ here; executors write the code and the tests. Reading list for every executor: t
| E | Route `AdminSheetDraftRoute.tsx`, App.tsx, AppLayout width, header, tabs (wide and narrow), modes and permission states, blocking recovery offer (« Restaurer la copie » / « Ignorer la copie », consultation only while pending), cap/quota notice with the other copies, conflict dialog (known N and author, failed read with « Recharger » / « Réessayer »), leave guard, overview links, A1/W1 landing, shared read-only field components; `failureMessage` allowlist; i18n | C1, C11-C13, C16, C27-C29 | unit |
| F | Général (+ annotation categories), Références, Vertèbres; shared delete-with-dependents dialog | C4, C5 | unit |
| G | Vues et illustrations + upload flow | C6, C17 | unit |
| H | `docs/ANNOTATION-RENDERING.md` overlay section first; Annotations: canvas, overlay, tools, list, creation panel, properties panel, keyboard creation, undo/redo controls; default point rule with the corrected-position confirmation and the `accept` hook on every geometry commit (« Default point and the frame ») with its Node-core unit tests | C7, C8, C14, C17, C26 | unit |
| H | `docs/ANNOTATION-RENDERING.md` overlay section first; Annotations: canvas, overlay, tools, list, creation panel, properties panel (geometry group applied whole, « non appliqué » state), keyboard creation, undo/redo controls; default point rule with the corrected-position confirmation and the `accept` hook on every geometry commit (« Default point and the frame »: measured views only, read-only geometry elsewhere, repair rules) with its Node-core unit tests | C7, C8, C14, C17, C26, C32-C34 | unit |
| I | Constats tree | C9 | unit |
| J | Vérification panel + submission | C10 | unit |
| K | e2e `apps/app/e2e/shell/editor-*.spec.ts` reusing `createAccount`, `assignRole`, `seedGrant`, `enrolVerifiedFactor`, `stepUpAdmin`, `seedOfficialSheet`, `expectAccessible`, `expectNoHorizontalOverflow`, `dropLateReplays`; adds editor-only helpers. A2 (hostile refused, Inkscape export cleaned, attach, detail view by crop; both upload outcomes accepted), A3 (points, zones, links by clicks and by keyboard, move, numeric edits), A4 (zones, categories, nodes, refs, regions, reorder, mark reviewed, delete with dependents), journey (the brief's §3 steps 1-12 with two editor accounts: creation, upload, detail view, points/zones/links, categories and findings, save, reload with the beforeunload dialog accepted and the recovery offer, conflict, submit, round `verifying` read back in SQL, no error shown while elements are `to_confirm`), access (reviewer-only read-only, editor grant without admin role read-only, account without capability refused), narrow (320, 375, 800 px read-only, no horizontal scroll; 1 024 px edit without horizontal scroll), axe on editor and read-only, the equine working copy opening (sets aside an active copy first, as `sheets-concurrency.sandbox.ts` does); owner tests (C30): concurrent save between two sessions, older-copy restore then save → conflict dialog then « Garder ma version » confirmation, a pending recovery offer blocks editing until answered, permission changes during an open editing session (grant revoked, grant expired, admin role removed: the next save is refused with its message, the copy wording true), a click near the edge of a detail crop (corrected position shown, confirmed, cancelled), hostile and valid drawing imports, keyboard-only creation and numeric edits; commit latency measured on the equine copy and on a synthetic document near 2 MiB (reported; budget 500 ms per commit on the equine copy); `docs/development/BROWSER_TESTS.md` | C16, C20, C21, C26-C30 | `e2e:shell` on a fresh sandbox |
@@ -438,3 +471,11 @@ F parsed from the attribute text), B (kept input and `handleVersion` only after
pending as it refines C26), E (`restoring` state, one store update, `savedText` stays the server's), F (removal
actions refused while pending, unreadable copy kept as refused, leave guard while an offer is open), G
(`version_id` checked, submit conflict uses the dialog, submit refused under `staleBase`). STOP for the owner.
Owner GO 2026-11-04 (« GO propriétaire après REMAINING(1) »): F1 fix approved (C32); C26 refined by the owner's
seven repair rules (C33: one rule, the changed annotation carries no geometry error after a commit; a typed
`too_small` radius is now refused; repair through a temporary form group applied whole; frame changes refused when
they give an error-free annotation a geometry error or leave a view with annotations unmeasured); minor effects
approved (C34: 4 px threshold with click, keyboard and touch kept, unreadable copy with the loss named, leave
guard disarmed after a confirmed save or an explicit abandonment, mobile limits documented). Execution of lots A-M
authorised without a third plan review; stop and present any blocking defect or contractual impossibility.