docs(chore): step 4c validated — head view check, migration limit BLK-008, review semantics, .env.example expected change, BDR-037, TODO follow-up

This commit is contained in:
bchanot committed 2026-10-10 10:32:57 +02:00
1 parent c0c17fcf5f
commit 866e84f75b
7 files changed
+50 -2

No files matched your search

@@ -363,6 +363,31 @@ level B or C change, every finding, finding category and annotation it
touched is left at `to_confirm` (recorded in the CHANGELOG), and an explicit
`reviewed` in such a change throws.
Head view after the single-asset switch (checked 2026-10-10): the `head`
detail view still exists (`parent_view_id: main`, opened by `head-trigger`),
keeps its 9 annotations with the same ids (parietal, frontal, occipital and
hyoid at their legacy position, the five others moved by CHG-044), and is
rendered as the `view_box` crop of the shared drawing. `svg_asset_id` stays
nullable per view, so a future revision can give any view its own drawing
again (CHG with `set view:<id>.svg_asset_id`), nothing in the model assumes
one asset.
Status semantics: technical integrity (zero issue) is not anatomical or
clinical validation. `inherited` = taken over from the legacy catalog
without review; `reviewed` = checked against a cited source by a level A
change; `to_confirm` = changed or added on documented grounds, awaiting the
partner osteopath. The draft is the reference draft of the application until
a platform admin publishes it after that review (REVIEW-REPORT §10, 11 open
questions; the legal scope text must be re-read on the consolidated
Légifrance articles first).
Known limit of migration 20261010100000: it tightens the CHECK to
`document_schema_version = 2` without rewriting stored rows, so it fails on a
database that still holds a schema 1 draft (a dev database seeded before Step
4c). It is safe with `db reset`; before any database with real data, write a
data migration that lifts stored documents to the current schema, then
tightens the CHECK (BLK-008). Future schema bumps follow that order.
Seed: `equine_draft.sql` is idempotent and converging. On a fresh database
it inserts the sheet, the cleaned asset row and the draft through
`private.insert_sheet_draft`; when the sheet's only version is a draft