41 KiB
Changelog
All notable changes to Faunosteo are documented here. Format: Keep a Changelog. Versions follow Semantic Versioning.
[Unreleased]
Nothing in this section is released or deployed: faunosteo.com runs 0.1.0.
Everything below is on develop only, accumulated since 0.1.0: the SaaS
Steps 0 to 8 and the Rust migration R0 to R5 included. release/0.2.0 (Steps
3 to 6) was cut on 2026-10-11 and never finished; its [0.2.0] section lives
on that branch and reaches this file only if the release is finished (TODO
RR-9).
Fixed (2026-10-27, V1-1 DEV acceptance, RESP-01)
- The dashboard no longer scrolls sideways on a phone when the account e-mail is long: the card grid has one explicit column below the
mdbreakpoint, so the cards keep the screen's width, and the e-mail wraps instead of being cut (a long one was truncated on desktop and pushed the cards past a 320 to 430 px screen from about 31 characters).e2e/shell/responsive.spec.tschecks nine shell pages, the archive confirmations and the drawer at 320 to 430 px and on desktop, in French and English.
Removed (2026-10-25, Rust R5.7: the TypeScript pipeline and domain packages)
packages/anatomy(legacy importer, curation pipeline, TypeScript renderer,import-equineCLI) andpackages/domain(Zod schemas and rules) are deleted, with the TypeScript upload scriptpackages/supabase/scripts/upload-sheet-assets.tsand the scriptspnpm import:equine:legacyandassets:upload:legacy. The Rust core does all of it:pnpm import:equineandpnpm assets:uploadare unchanged for the user.@xmldom/xmldomleaves the lockfile;tsxis no longer a dependency of any package (pnpm keeps it only as an optional peer of vite); root Prettier stays (pnpm format,db:types).- Every one of the 407 TypeScript test cases is dispositioned in
crates/core/tests/curation/LEDGER.tsv(ported, replaced by a frozen oracle, or deleted with its reason, none uncovered) and every deleted file incrates/core/tests/curation/FILES.tsv; the contracts the TypeScript alone still checked are ported to Rust (the 612 legacy leaves and 26 legacy annotations, region inference, the R5.1 artifact ledger, the generated folders' file list, the migration-map oracle entry by entry, review overlay removals, the halo filter, reserved and dollar-tag refusals). Thereport-v2.*.jsonfixtures moved tocrates/core/tests/fixtures/with their bytes unchanged. No oracle, golden, digest or seed byte changed. The historical TypeScript pipeline stays replayable from commit59521dc(official writer) or756b7ef(last revision holding it) in a detached worktree (docs/development/RUST.md§11.23).
Changed (2026-10-25, Rust R5.6: the sheet fingerprint convention sha256-rfc8785-validated-v1)
- The equine sheet's fingerprint is now the SHA-256 of the RFC 8785 canonical form of the validated document:
12d78872…74e2indraft/sheet-ref.json(with afingerprintblock naming the convention) and indraft/report-migration-map.json, the only two seed files changed;document.json, the drawing and the SQL seed are byte-identical. The previous value27c7383c…2660stays recognised for this sheet only, through the core's compiled registry and a fingerprint recomputed from the loaded document: old reports and PDFs open with no message and no rebase, and a re-export keeps their stamp so older readers keep the archive. A report written after the switch, opened by a build from before it, is rebased with nothing lost.pnpm import:equineruns the Rust pipeline; the TypeScript generator stays aspnpm import:equine:legacyuntil R5.7 (docs/development/RUST.md§11.22).
Changed (2026-10-23, Rust R5.5: the sheet-asset upload tool in Rust)
pnpm assets:upload [--check] <seed folder>runs the Rust binaryupload-sheet-assets(crates/core, featureupload,ureq) in place of the TypeScript script (kept asassets:upload:legacyuntil R5.7). Local stack only: no default destination,httpwith an explicit port on loopback or the configured DEV address, a private-bucket handshake before any transfer; every file checked againstassets.jsonand the SVG reader before the first request; an existing object is hashed and never overwritten, a missing or foreign asset row stops the run, a row is confirmed only after its object is read back; bounded retries, resumable; the service key is never printed. Runbookdocs/development/SUPABASE.md§3.1,pnpm e2e:sheet-assetsfor the local stack,docs/development/RUST.md§11.16.changes.jsonandreferences.jsonare refused above 4 MiB with an explicit message (core and binary). The serde tolerance of the R2 contracts is characterised (testcharacterisation_serde_tolerance), not changed.
Changed (2026-10-23, Rust R5.4: the review files in Rust)
- The review drawings (
review/annotations-*.svg,review/app-*.svg),CHANGELOG.mdandREVIEW-REPORT.mdof the draft are produced by the Rust pipeline: the two reports and three drawings byte for byte with the committed files;review/app-main.svgcarries the head trigger's English name ("Head (left lateral view)"), the name the editor canvas shows since R3, where the committed file repeats the French one.pnpm r5:import-equine --checknow compares the whole draft (12 files) and fails on any file missing or different without a declared rule;--outwrites the 18 files. The seed,horse.svg,pnpm import:equineanddocumentSha256are unchanged (docs/development/RUST.md§11.14).
Changed (2026-10-22, Rust R5.3: the curated draft in Rust)
- The draft side of the anatomical pipeline runs in Rust behind the core's
curationfeature (crates/core/src/curation/draft): the authored changeset and references files parsed strictly, the six ops of a change applied on the plain JSON document with their records, the review rule of levels B and C, the shape and integrity gate of the R2 core, the report migration map, the document statistics and the seed SQL.pnpm r5:import-equine --checkreproduceslegacy-import/and the R5.3 files ofdraft/(document.json,assets.json,sheet-ref.json,report-migration-map.json,equine_draft.sql, the frozenassets/horse.svg) byte for byte, 12 files, 0 differences;pnpm r5:import-equine --out <dir>writes both folders into an empty folder and never deletes anything. The review drawings,CHANGELOG.mdandREVIEW-REPORT.mdof the draft stay with the TypeScript until R5.4;pnpm import:equineand the seed are unchanged;documentSha256stays27c7383c…2660until R5.6 (docs/development/RUST.md§11.12).
Changed (2026-10-22, Rust R5.1b and R5.2)
- The core prints an exact decimal tie as JavaScript does (
840.1692504882812, round half to even), its digits now fromzmij, the formatter serde_json already used; no historical output carried such a value, so no oracle, golden or PDF digest changed (docs/development/RUST.md§11.9). - The legacy importer runs in Rust behind the core's
curationfeature:import-equine --checkreproduces the committedlegacy-import/folder byte for byte, and--out <dir>writes it into an empty folder. The TypeScript pipeline,pnpm import:equineand the seed are unchanged;documentSha256stays as it is until R5.6 (§11.10).
Changed (2026-10-22, Rust R5.1: the TypeScript pipeline frozen, not yet ported)
packages/anatomyandpackages/domainare unchanged; their outputs are recorded as oracles undercrates/core/tests/oracles/r5/(intermediate values, ids and slugs, the fingerprint of every generated JSON file under today's rule and the candidate rules of D-R5), generated bypackages/anatomy/tests/r5.pipeline-oracles.test.tswithMAKE_R5_ORACLES=1. Study scriptsscripts/r5-fingerprints.mjsandpackages/supabase/scripts/r5-jsonb-fingerprint.mjs(read-only).documentSha256and the generated seed are untouched; the D-R5 decision is the owner's (docs/development/RUST.md§11). Known defect recorded, not fixed: the core's JavaScript number printing rounds an exact decimal tie upward where JavaScript rounds to even (no value of the curated draft is affected).
Fixed (2026-10-21, R4 close)
- Sign-in redirects: a
nextvalue whose dot segments normalise into//host(/..//host,/%2e%2e//host) now falls back to the dashboard instead of being returned as a protocol-relative path. The worker image runs ondistroless/static-debian13:nonroot(the Debian 12 tags are no longer updated). DEPLOY.md showshttp2 on;for nginx 1.25.1 and later and keeps thelisten ... http2form for nginx 1.24 (docs/development/RUST.md§10.14). - Dependencies:
rustls-webpki0.103.16 andwebpki-roots1.0.10 (RUSTSEC-2026-0382, RUSTSEC-2026-0381; the worker's TLS client),react-router-dom7.18.4 (GHSA-wrjc-x8rr-h8h6, GHSA-chx6-hx7r-mcp5 and three RSC / SSR advisories the application does not reach). A worker test proves the HTTPS client refuses an untrusted server certificate (docs/development/RUST.md§10.13). - The footer's « Propulsé par ZenQuality » logo is bundled with the application instead of loaded from zenquality.fr: the documented production CSP (
img-src 'self' data: blob:) refused the external image and showed the alt text in its place. Same picture, no policy change; the exported PDF never depended on it.
Fixed (2026-10-18)
- Improve Safari/iOS PDF download reliability by attaching the download link to the document during activation and delaying object URL revocation by 30 seconds. The file name and content remain unchanged.
Changed (Rust R4, PDF core, 2026-10-18 to 2026-10-19; validated by the owner's device acceptance on the computer, Android and a real iPhone, and merged 2026-10-21)
- The PDF archives are read, written and checked by the Rust core (
crates/core/src/pdf,docs/development/RUST.md§10). Import: the attachment is located by the core's byte scan, inflated under the 16 MiB cap, probed as JSON and read by the R2 layered reader, inside a module worker created for the file and terminated after it (R4.3; the rescue copy follows the same path). Export: an incremental session in the page's engine composes each view, takes the browser's rasters one by one, decodes and writes each image on arrival, and hands the file out in parts (R4.6; no raster and no second copy of the file kept).pnpm report:compareruns the core'sreport-comparebinary (R4.7). The PDFs are the ones the TypeScript engine wrote: same streams, images, links, metadata and attachment, pixel-identical through poppler on the reference reports; three declared differences only (Producer/CreatornowFaunosteo, the attachment's report in contract key order, hostile files refused where the TypeScript repaired them). - Removed at R4.8 (2026-10-19):
packages/pdf(the TypeScript engine and its tests),pdf-lib,@pdf-lib/*and@resvg/resvg-js, the TypeScript CLIapps/app/scripts/compare-reports.ts, the application's TypeScript import path and its dependency on@faunosteo/domain, the oracle generators. Kept: the frozen oracles, goldens and fixture PDFs, the frozen N-1 readers (packages/core-wasm/tests/n-1: the Zod schemas and the byte-scan reader of the R3 build),packages/anatomyandpackages/domainfor the curation pipeline until R5. - Old browsers (Firefox 102 to 112, Safari 16.0 to 16.3) gain the import and the logos; module workers need Firefox 114 (OD-1). Memory: the import worker holds one copy of the file; the export's linear memory stays reserved in the page until reload (OD-2), about 62 MiB for a 44 MiB file; the per-export growth of the browser's own process in Chromium is an open reserve (BDR-063). Module 1,535,289 B raw, 519,795 B gzip (budget 600 KB).
Changed (Rust R3, anatomy core, 2026-10-15; validated by the owner's LAN acceptance and merged 2026-10-17)
- The editor canvas draws what the Rust core composes (
crates/core/src/anatomy): one SVG reader for every drawing the product shows (bounds checked by a markup scanner before any XML parser, the engine's allowlist matched the same way, a reference graph refusing cycles and expansions over 50,000 elements, a serialiser that re-reads to the same tree), the annotation layer and the view composition, reached through the newview.canvasoperation and memoised per view. The canvas keeps its in-place selection styling, click and tooltip delegation. The browser-side denylist and the app's dependency on the TypeScript renderer are gone; the PDF engine and the curation pipeline keep the TypeScript renderer until R4 and R5. - No visible change, proven first with the TypeScript: canvas trees of both views and 28 selection states, layer trees with attribute order, 36 PDF highlight compositions, 36 hostile SVGs and 10 generated floods, the 4 product SVGs untouched; in Chromium 156 the live canvas trees equal the frozen ones and 30 screenshots (desktop and phone) are pixel-identical before and after. The Step 6 goldens are untouched.
- Declared differences, none on a product drawing: elements outside the SVG namespace removed, comments dropped, no
class/styleon the inline root, stricter ids, text only intitle/desc(4 KiB each), floods and reference cycles refused, a product drawing the allowlist would alter refused at load instead of silently cut, a canvas that cannot be composed shows the existing degraded notice with a retry (docs/development/RUST.md§9.4). docs/ANNOTATION-RENDERING.mdrewritten to describe the code exactly (no rendering change). Module 396 KB gzip (+56 KB, budget 600 KB).- Owner decisions after the R3 review: a detail-view trigger without its own name now carries the opened view's name in each language (the English attribute and the tooltip title used to repeat the French name); the canvas tells an engine that did not load ("Réessayer") from a view whose drawing is refused or cannot be composed (its own message, no retry); after its three recoveries the engine shows a clear final state, never a retry that cannot work: in the canvas, the editor banner slot, the top of Home and New report and the full-page notice, and in the action, export, import and new-report alerts. Two variants: report saved in the tab ("Recharger la page"), or tab storage full ("Télécharger une copie" of the in-memory report, no reload button, native confirmation before leaving). A recovery that fails below the cap is restarted by the next call (the canvas "Réessayer" now restarts the engine), and a core failure reading the tab draft no longer reports a held session (except a trap of the engine on the draft,
internal, held as an engine failure since the final checks below). - R3 final checks (owner decisions 2026-10-17): the rescue copy can be restored: the Home picker now accepts the JSON downloaded by "Télécharger une copie" next to the PDF (routed by content, strict UTF-8, size cap, read by the core's draft restore; a refused file changes nothing). A draft that traps the engine (out of memory) no longer loops on the reload screen: the editor shows the resolution panel with the draft kept as is, New report and Import say so and open it, the trapping draft is read once, and only "Réessayer" reads it again. New report and the file pick ask before replacing a bilan in progress (cancel, open it, replace), and the "unsaved changes" browser prompt now guards every page, not only the editor. Documented in
docs/development/RUST.md§8.3, §8.7 item 3 and §9.4 item 9.
Security (maintenance after R2, 2026-10-14)
- Worker TLS: rustls 0.23.45 → 0.23.46 (
Cargo.lockonly, throughureq3.4.2): RUSTSEC-2026-0346 (session values'Debugprinted TLS secrets), 0347 (ECH rejection), 0348 (Brotli certificate decompression), 0349 (unauthenticated ServerHello pinning the next key exchange group). None reached the worker as configured (ring provider without ML-KEM groups, no ECH, nobrotlifeature, sessions never printed); the bump removes them anyway. No API or feature change; the patch also fixesStreamOwnedflushing and surfaces a connection's fatal error on the next write.cargo deny check advisoriesclean.
Fixed (maintenance after R2, 2026-10-14)
- Session texts never lost when the browser storage is full. A draft or archive the running build cannot read, and that cannot be set aside (storage full, or the quarantine slot already holds an earlier text, which is no longer replaced), now stays where it is: nothing is opened over it, and the editor shows a resolution panel with an exact copy to download, a permanent deletion or (for a draft to adapt to the current sheet) the adapted version, each behind a confirmation, and a retry. "New report" and "Import" refuse to start while such a text is held and send the practitioner to that panel; they also read a draft the page never opened before replacing it, so an unreadable one is set aside first. An unreadable draft is set aside together with the archive kept beside it. The draft mirror no longer reacts to unrelated store changes, and a refused draft write shows a storage-full banner in the editor. No change for a readable session.
supabase/.temp/cli-latest(the Supabase CLI's version-check cache) is no longer tracked: it had been committed before thesupabase/.temp/ignore rule existed, so every CLI run dirtied the tree. The local copy stays; the ignore rules already cover.temp/,.branches/andsupabase/.env.*.
Changed (Rust R2, domain core, 2026-10-14)
- The application's domain rules run in Rust (
crates/core, through the wasm facade and@faunosteo/core-wasm): sheet, report and archive contracts with the Zod semantics reproduced, the 21 sheet integrity rules and the publish check, the sheet index, the v2 → v3 migration, the rebase on the loaded sheet, the sheet snapshot, the layered archive reading, the editor's click chain and reducers, the findings and vertebra rules, report creation and the observation list operations. Consumers switched: the editor, the pickers, the store, the draft restore, the PDF import (after the engine's byte scan) and export (snapshot), the Supabase publish gate (fails closed). The module (340 KB gzip) loads only on the sheet pages; sign-in, the/appspace and Home never request it. Without'wasm-unsafe-eval'in the CSP the editor shows a degraded notice with a retry and leaves the session's draft untouched (DEPLOY.md: set the keyword before deploying an R2 image; R2 images are never built on the VPS). - Session data never dropped silently: an unreadable draft or archive is set aside under
osteo:quarantine:*with a notice; a draft rebased with unresolved items keeps its raw text. - Behaviour differences, declared in
docs/development/RUST.md§8.7: drafts and attachments written in contract order (values unchanged, the previous build reads them, D-R11); typed errors on inputs the interface never produced. - Lone UTF-16 surrogates refused, never altered (L1, owner decision): a draft, archive or attachment whose JSON escapes a lone surrogate is no longer read with U+FFFD in its place. The draft or archive is set aside verbatim under its quarantine key with the existing notice; a PDF import is refused with a new message (malformed text, file not modified); an editor action is refused and the report left as it was.
- Proofs: contracts byte-equal to the Zod output on the reference documents, the three archive envelopes frozen before the switch and deep-equal after, 924 cases and verdicts frozen from the TypeScript, permanent N-1 reader test, generated pgTAP conformance file (real stack 446/446), CSP proof on the real image. No interface, archive format, database or graphic change; release 0.2.0 untouched.
Changed (development environment, 2026-10-13)
- DEV on the private network — the owner tests from other devices: the DEV origin (the machine's LAN address,
FAUNOSTEO_DEV_HOST, detected or set) lives inscripts/dev-env.sh;pnpm devserves the app on that origin wired to the local stack,pnpm dev:offlinekeeps the local tool alone; every Supabase CLI call goes throughscripts/supabase.shsoconfig.toml(API external URL for the mail links, site URL, Studio API URL viaenv()) follows the origin; private-network redirect URLs for the PKCE links. Identity recorded: Faunosteo, https://faunosteo.com; environments DEV / STAGING / PROD and the exposure table indocs/development/ENVIRONMENTS.md.
Added (SaaS migration, plan Step 8 = Rust R1)
- Files foundation and profile photo (Step 8) —
public.assetsas the authority over user files (status, owner, server-built keys, worker lease token), seven private Storage buckets (onlyavatarsopen, through SELECT / INSERT policies evaluated onassets; the six others closed until their step), a quarantine upload path (begin_avatar_upload→ direct upload at the quarantine key →confirm_asset_upload), a deferred purge queue (48 h for a replaced or removed avatar, 1 h for quarantine and rejected uploads: the backup invariant) and the audited RPCs of the browser and of the worker (migration20261013100000, pgTAP 010 with 125 allowed and denied checks, policy census). Rust worker job loop (crates/worker, R1): the keyed parent claims leased jobs through PostgREST, downloads the quarantine bytes, hands them to the sandboxeddecodechild of R0 (empty environment, rlimits, seccomp allowlist unchanged), uploads the 512 × 512 lossy WebP, commits the row, deletes the quarantine object, rejects with closed codes (unsupported_type,decode_failed,dimensions,processing_error), sweeps expired uploads, the purge queue and quarantine leftovers; JSON line logs with a field allowlist; per-stage watchdog; Compose serviceworker(profileworker, read-only, no capability, external Supabase network,.env.worker). Profile photo in Mon compte (preview before any request, save, processing with polling, rejection messages, replacement, removal with confirmation) and in the sidebar, the mobile drawer and the top bar (name beside it on desktop, link to Mon compte); JPEG / PNG / WebP only, never SVG, downscaled to 1024 px in the browser as transport, judged again by the worker; the owner downloads the clean object under RLS (no signed URL). Real-stack end-to-end runpnpm e2e:avatar. Spec:docs/development/STORAGE.md.
Added (Rust foundation, plan R0)
- Rust by default (rule adopted 2026-10-12,
docs/development/RUST_ARCHITECTURE_REVIEW.md): Cargo workspace with three crates,crates/core(contracts and the JavaScript-compatible JSON formatter, no I/O by lint),crates/wasm(browser facade built intopackages/core-wasm/pkg) andcrates/worker(the future file-processing worker: sandboxeddecodechild with rlimits and a seccomp allowlist derived bystrace, image decoding in pure Rust, lossy WebP through libwebp confined to the child, parent-side container check;run --checkonly, no job loop before R1). Reference toolchain in Docker (docker/rust-builder.Dockerfile,pnpm rust:check,pnpm wasm:build), worker image ondistroless/static, CI jobrust, nightly advisories, manual digest-tagged image workflow (no deploy). R0 proofs recorded indocs/development/RUST.md:float_roundtriprequired for JSON parity, traps leave a wasm instance unusable (fresh instance per recovery), CSP needs'wasm-unsafe-eval'. No application behaviour, interface, archive or database change; the frontend does not load the module.
Changed (Rust foundation, R0 correction 2026-10-13)
- Native Rust toolchain as the primary path on the Ubuntu development machine (user-level rustup, channel of
rust-toolchain.toml,wasm32-unknown-unknown,wasm-bindgen-cli0.2.129,cargo-deny0.20.2):pnpm rust:checkandpnpm wasm:buildrunscripts/rust-check.shandscripts/wasm-build.shnatively (moved fromdocker/, PATH guardscripts/rust-env.sh); the builder image stays the reproducible alternative (pnpm rust:check:docker,pnpm wasm:build:docker). The native check now covers the worker's unit tests; the sandbox tests and the seccomp derivation stay Docker-only (pnpm worker:test). Newpnpm check:all(scripts/check-all.sh): every check a branch must pass before a merge, in one command. The Gitea workflow files are kept but marked prepared and never executed (no runner, secret or registry on the forge). Workerunsafeblocks: SAFETY comments rewritten as verifiable invariants (no approval marker), WebP stride computed with checked arithmetic.docs/development/RUST.md§1 and §4 describe the three environments (Ubuntu native development, Docker for services and isolation, separate production VPS).
Added (SaaS migration, plan Step 7)
- Identity (Step 7) — sign-in and sign-up by email/password (confirmation mandatory, policy 12 chars + lower/upper/digit), password recovery, OAuth buttons (Google, Apple) driven by
APP_AUTH_PROVIDERS, landing route for confirmation / OAuth links; the guarded/appshell (desktop sidebar, light top bar, mobile drawer) with a dashboard (greeting, profile completeness, local tool, account) and Mon compte (personal, professional, preferences, security). Profile columnspractice_name,professional_title,siret(migration20261011100000, pgTAP 009), language synced withprofiles.locale, platform roles shown read-only. GoTrue TOTP enabled server-side; MFA enforcement for platform roles documented as a gap (docs/development/IDENTITY.md). The local tool (/,/new,/editor) stays unauthenticated; the Home header links to the space only when Supabase is configured.
Added (SaaS migration, plan Steps 3–6)
-
Autonomous PDF archives (Step 6) — new
@faunosteo/pdfengine (packages/pdf): the PDF is rendered from explicit inputs (report, sheet snapshot, branding, labels, locale, rasterizer, export date), with no network and no browser DOM; the attachment becomes a report archive envelope v1 (osteo-report.json) carrying the Report v3, a lean but valid snapshot of the anatomical sheet (views, annotations, geometry, colours, relations, the finding paths used with their ancestor labels, the SVG drawing), the branding used at export and the FR/EN label dictionary, so an old bilan is reproduced identically after any catalog, wording or logo change. Layered reading keeps the report even when the wrapper or the snapshot is refused (closed reasons), v2 and bare v3 PDFs still import, a PDF whose attachment was stripped is recognised. Imported archives are kept in the session; a bilan reopened on a different sheet is rebased on a working copy with unresolved items flagged and their labels kept, and the import message says so. SVG assets go through an allowlist sanitiser with size and complexity caps checked at import and at export; a WinAnsi guard keeps any text from crashing the export. Pages unchanged (frozen by 39 goldens).docs/PDF-FORMAT.mdwritten for real. -
Supabase foundation — local stack (
supabase/config.toml), migrations (schemasprivate/audit,profiles, platform roles with audited RPCs), pgTAP suite run on PGlite (pnpm test:run) and on the real stack (pnpm db:test),@faunosteo/supabasetyped client + generated types. No UI change. -
Anatomical sheet model —
@faunosteo/domain: canonical sheet document (views tree, annotations with stable ids and explicit laterality, ordered vertebral regions, typed finding categories, explicit annotation → finding zone links, FR/EN labels) with integrity validation; tablesspecies,anatomical_sheets,anatomical_sheet_versions(published rows immutable, one draft per sheet, deletion preconditions),anatomical_sheet_assets; lifecycle RPCs (create, draft, publish, deprecate, delete, fork with provenance, archive, assets) audited and under RLS. Spec:docs/development/ANATOMICAL_SHEET_MODEL.md. -
Application on the canonical sheet (Step 5) — the editor renders the bundled reference sheet (curated equine draft,
SHEET_BUNDLE=draft; a default build carries no sheet): markers drawn from the document with the legacy look (@faunosteo/anatomy/render), head view as a crop of the same drawing, zone interaction service, pickers on the sheet's regions (usual count, extension to the documented range) and finding zones. Report document v3 (packages/domain/report): zones by annotation and view ids, findings by zone and path, severity codes, exact sheet reference; v2 PDFs and drafts migrate through the generatedreport-migration-map.json, unresolved items kept with their labels. Removed: species registry, label matchers, SVG convention parser,/editors,/svg-editor,pathology-editor.html,scaffold:species; the legacy sources now live undersupabase/seed/anatomical-sheets/equine/legacy-sources/. Archive check toolpnpm report:compare(attachment vs its v3 reading, unresolved items flagged); the 612 legacy catalog leaves are tested through the migration in both packages. -
Equine sheet curation (Step 4c) — document schema v2 (references registry,
review_statuson findings and annotations, configurable vertebralcount_range; migration20261010100000, pgTAP 008);@faunosteo/anatomycuration pipeline: authored changeset (curation/changes.json, levels A/B/C, before/after records) applied to the legacy baseline → working draft withCHANGELOG.md,REVIEW-REPORT.md(10 sections for the osteopath) and before/after review drawings; one cleaned SVG asset, head view as a crop. Content: research-backed audit of the horse sheet (44 changes, 48 verifiable references): sphenoid zone restructured, NAV terminology, FR/EN translations, vertebral ranges, ten SVG points relocated, carpus zone added, veterinary red flags, legal disclaimer anchored on R. 243-6 / R. 243-8, osteopathic-model status on unvalidated concepts, 11 questions for the professional. Still a private DRAFT, not published. Docker resources prefixedfaunosteo_(Compose project and container). -
Equine import (Step 4b) —
@faunosteo/anatomydeterministic importer:Horse.svg+Horse_head.svg+pathologies.json→ canonical document, legacy id map, French import report, idempotent seed creating the official sheetfaunosteo-chevalas a private DRAFT (never published by code). Storage bucketanatomical-sheet-assets(content-addressed SVGs, read through the sheet, operator upload script).
Changed (SaaS migration, plan Step 2)
- pnpm workspace — the application moved to
apps/app(@faunosteo/app) withgit mv; root commands (pnpm typecheck|test:run|lint|build|dev) delegate to the packages.packages/reserved, empty. CI workflow added (.gitea/workflows/ci.yml). - Node 24 LTS / pnpm 10.13.1 — declared in
.nvmrc,.node-version,engines,packageManager;engine-stricton; Dockerfile builds onnode:24-alpineand copiesapps/app/dist.
Added (SaaS migration, plan Steps 0–1)
- Implementation plan —
docs/development/(27-step plan, migration map, domain map, architecture, strategies, open questions). - Characterisation suite — 91 tests on the real SVGs, catalog and PDF pipeline; two golden Report v2 fixtures (
CHARACTERIZATION_REPORT.md).
Added
- Laterality & bilaterality —
LateralSideSchema(left/right) +Bone.lateral,data-anno-lateralparsed from the SVG;LateralityPickermodal in the zone-click flow, side shown in zone badges and PDF labels; bilateral zones get a separate findings picker per side. - SVG anatomy editor —
/svg-editorroute, the vanilla annotation tool wrapped in React (BDR-017). - Standalone pathology editor —
public/pathology-editor.html, a zero-dependency JSON tree editor with SVG zone selection (BDR-020/021/022). - Welcome screen — tabbed editor entry with a project SVG picker;
/editorslisting page. - Footer branding — global footer with copyright, "Powered by ZenQuality" and the "Paws in Harmony" partnership logo, on both the site and the exported PDF.
- gitflow socle —
main/developmodel + versioned pre-commit hook.
Changed
- Unified
AppHeaderacross every route (logo brand + tagline). - Responsive mobile — full phone/tablet adaptation across all components.
- Project renamed Zoosteo → Faunosteo across the whole codebase.
Removed
canvgdependency — PDF SVG rasterization now uses the browser's nativeImage/canvaspipeline (src/pdf/render/svgToPng.ts) instead of thecanvglibrary.
Fixed
pathology-editor.html404 in production — it lived at the repo root, Vite never bundled it intodist/; moved topublic/so it ships (LRN-029).- Docker species caching —
Cache-Control: no-cacheheader added for/species/assets so an updated catalog is served fresh. - nginx runner base image pinned to
nginx:1.31-alpine(was the floatingnginx:alpinetag).
Security
- Docker container runs fully as non-root (
USER nginx) —PORTmust now be>=1024(default8080unaffected). - Supply-chain guard —
.npmrcgainedminimum-release-age=1440, blocking install of package versions published less than 24h ago. - User-imported SVGs sanitized — the SVG editor and the standalone pathology editor now strip
<script>/<foreignObject>nodes,on*event-handler attributes, andjavascript:hrefs before inserting an imported SVG into the DOM.
[0.1.0] — 2026-05-21
First public release. Single-praticien web app for veterinary osteopathy bilans on animal anatomy SVGs. Static SPA, no backend, no auth; the exported PDF is the long-term record, with the full report JSON embedded as a native PDF attachment so re-importing the PDF restores the session for a follow-up.
Added
- Anatomy canvas — inline SVG with clickable zones, hitbox+visible twin pattern, delegated click listener, async-mount safe.
- Detail popups — click a zone (e.g. head) to open a secondary SVG with finer-grained zones. Independent bones map, fallback lookup across main + detail.
- Vertebra picker — region tabs (C/T/L/S/Cd) with multi-select chip grid; region tab preselected from the clicked zone label.
- Hierarchical findings tree — per-zone picker with breadcrumb drill-down, leaf toggle, vet-referral badge, count badges on intermediate nodes, scope-disclaimer modal shown once per session.
- Bilingual UI (FR / EN) — full i18n via flat dict +
useT()hook, language switcher in every header, locale persisted tolocalStorage, default auto-detected from the browser. - PDF export — A4 portrait with rasterized anatomy SVGs (canvg
@ 2×), structured per-zone observation sections (
CONSTATS — <ZONE>CONSTATS LIBRES), severity pill, conclusion page, locale-aware static labels. Inter-item separator rendered as accent-coloured bold bullet.
- PDF import — Zod-validated re-import of a previously exported PDF
restores the entire session. Typed
ImportError(discriminant +foundVersion) with i18n-resolved user-facing messages. - Practitioner cache — last-used practitioner block prefilled via
localStorage. - Runtime identity —
APP_SITE_NAME/APP_BRAND_NAME/APP_FOOTER_NAME/APP_TAGLINEinjected intoenv.jsat container start; no rebuild required for brand changes. - Species auto-discovery — drop a
src/domain/species/<id>/index.tsdefault-exporting aSpeciesManifestand the species appears in the picker.pnpm scaffold:specieswrites a valid skeleton. - Findings catalog v2.0 — full equine catalog authored by the
domain expert: 26 zones (9 head + 17 body), 792 nodes, 612 leaves,
41 vet-referral leaves. Schema documented in
docs/PATHOLOGIES-FORMAT.mdwith the 3 standardized categories per zone, 5 taxonomy patterns for dysfunctions, structural authoring rules (depth ≤ 4, ≥ 2 children per intermediate, sibling-scoped ID uniqueness), and the legal-scope disclaimer. - Fuzzy zone matcher — SVG
data-anno-name-fr/-en↔ JSONzone.name_fr/name_enbridged via normalize + Levenshtein (EN-first, FR fallback). Tolerant of case, accents, and minor typos. - Docker delivery — multi-stage
Dockerfile(node:20 → nginx:alpine),docker-compose.yml,entrypoint.shruntime env injection, nginx SPA fallback +env.jsno-cache rule. Production deploy guide inDEPLOY.md. - Documentation —
README.md,CLAUDE.md(project conventions for Claude),docs/ANATOMY-SVG-CONVENTION.md(SVG data-* contract),docs/ADDING-A-SPECIES.md(recipe for a new species),docs/PATHOLOGIES-FORMAT.md(findings JSON authoring contract),docs/PDF-FORMAT.md(PDF layout placeholder), and project-state notes under.claude/{tasks,memory,audits}/.
Changed
- Report schema v1 → v2:
Observationcarries hierarchicalfindings: Finding[](zone + path + snapshotted FR/EN label + vet flag) andfreeTextFindings: string[]; oldpathologyIds/freeTextPathologiesremoved.ReportSchema.versionbumped1→2. v1 PDFs are not migrated — they hard-fail import with a version-specific message (no install base to justify a migration shim). - Catalog v1.2 → v2.0 contract:
requires_vet_referralboolean is now the sole source of truth for the vet-orientation flag. Generic "orienter vers vétérinaire" wording purged fromdescription_fron 25 leaves where the boolean alone sufficed. 16 leaves carrying a clinical differential (cause neuro/sinusale/ ligamentaire/etc.) keep theirdescription_fr. Consumers relying ondescription_fr.includes('vétérinaire')must migrate — all in-tree consumers already key off the boolean. - PDF locale = render preference, not a schema field. Finding
snapshots already carry both FR and EN labels (
labelFrSnapshot/labelEnSnapshot), soexportReportToPdf(report, { locale })picks the right snapshot at render time without a schema bump. - PDF date format — locale-aware via
formatDate(iso, locale), replacing the FR-onlyformatDateFrhelper.
Fixed
- PDF export crashed
WinAnsi cannot encode "⚠" (0x26a0)whenever an observation carried arequires_vet_referralfinding —pdf/fonts.tsembedsStandardFonts.Helveticawhich uses WinAnsi (cp1252, Latin-1 only). PDF vet-referral marker swapped⚠→(!); picker DOM keeps⚠(browsers render U+26A0 natively). Regression test added onwidthOfTextAtSize+ prefixed label. Follow-up tracked: switch PDF body to embedded TTF (Inter / Fraunces perCLAUDE.mdspec) so future non-Latin-1 glyphs work without ASCII surrogates. - PDF import error messages localized via typed
ImportErrordiscriminant — the prior FR-only messages leaked through to the EN UI on import failure. - Detail-popup zone clicks silently dropped — main-only bones map
did not know detail SVG ids; fallback lookup
bones.get(id) ?? detailBones.get(id)added in the shared click handler. - PDF text overlap —
drawText({ maxWidth })wraps glyphs but not the cursor; caller now measures withwidthOfTextAtSizeand advances cursor per wrapped line. - PDF multi-SVG layout — observation pages with N SVGs overflowed page bounds. Now: pre-rasterize all, measure aspect, reserve text-area height, derive cell budget per row; single-SVG layout halved + centered.
- PDF anatomy rasterization leaks — interaction-only attributes
(
data-anno-*, transparent hitboxes, faint default fills) stripped before raster, non-selected zones hidden, selected zones recoloured. - Zone highlight scoping — collapsed observations no longer leave faint tints on the canvas; highlights re-painted after async SVG mount so detail-popup zones colour correctly.
- Hyoid label case — SVG
data-anno-name-fr="hyoïde"→"Hyoïde"to match the JSON strict-equality rule across all 26 zones (fuzzy matcher still acts as safety net). - i18n key parity — fr/en dicts validated by a parity test
(
Object.keys(fr).sort()deep-equalsObject.keys(en).sort()) so a missing translation fails CI instead of falling back to the key literal at runtime.
Known limitations
- PDF body fonts are
StandardFonts.Helvetica/TimesRoman(WinAnsi / Latin-1) instead of the planned TTF Inter / Fraunces. Any non-Latin-1 glyph in PDF text needs an ASCII surrogate until the TTF migration lands. description_frfor sensitive vet-referral leaves and thescope_disclaimerare FR-only; vet-expert authoring is needed for the EN copy.- Only the equine species ships. The infrastructure (manifest + auto-discovery + scaffold script + schema) accepts any species — domain expert authoring is the gating step.
- No backend, no accounts, no cloud sync. Each PDF is the long-term record for the corresponding bilan.
Pre-1.0 milestones (for reference)
These were never tagged but are reflected in git history on main.
- Scaffold (2026-05-18) — initial skeleton from approved design
spec: 80+ files (schemas, stubs, routes, stores, PDF modules, Docker
infra), real
Horse.svg+Horse_head.svg,pnpm/build/typecheck/testsall green. - Editor polish (2026-05-19) — detail-popup click bridge, VertebraPicker auto-region, PDF rendering fixes (header rule clear, text-line wrapping, multi-SVG grid, halo glow), eyebrow + Times 22 title + accent severity pill.
- Findings tree pivot (2026-05-20) — B0 schema (
findings.tsZod), B1 Report schema v2 (Observation.findings), B2 UI (FindingsTreePickerreplaces flatPathologyPicker), B3 i18n FR/EN site + PDF, B5 stub cleanup.requires_vet_referralboolean introduced alongside the textual fallback. - Catalog v2.0 + WinAnsi hotfix (2026-05-21) — full 26-zone horse
catalog landed,
requires_vet_referralbecomes the sole source of truth, PDF vet marker swapped to a WinAnsi-safe surrogate. Docs refreshed,DEPLOY.md+CHANGELOG.mdwritten, repo pushed tohttps://git.bchanot.fr/bchanot/faunosteo.git.