Files
faunosteo/packages
bchanot 74fcb37564 feat(app): R2 switch — the application runs its domain rules in the Rust core
Consumers now fed by the core (crates/core through @faunosteo/core-wasm):
- the sheet: the bundled payload is parsed and indexed by the core
  (SheetHandle, SheetIndexData); SheetIndex reads precomputed tables only;
- the store: new report, add / remove / move observation, draft restore
  (v2 migration + rebase) through the core, actions answering { ok };
- the editor click chain (zone.click), laterality and vertebra pickers
  (zone.add_sides, vertebra.initial / sync / select), the findings picker
  (finding.toggle by clicked leaf position), zone removal;
- the import: engine byte scan (TypeScript until R4), then the core's
  layered reading and rebase in one call; the export: the core builds the
  sheet snapshot, the frozen TypeScript engine writes the PDF (R4).
Lazy core: Home and the new-report form read the sheet availability from
the bundle and load the module on import / submit only; the auth shell
never references it. Degraded states (core_unavailable, invalid_sheet)
show the validated notice with a retry and never redirect or touch the
draft; an unreadable draft or archive is set aside under
osteo:quarantine:* (only content kinds; a failed write keeps it in place
and the editor stays), a rebase that flags items keeps the raw pre-rebase
draft. Four strings, wording validated by the owner.
Deleted: services/zoneInteraction.ts and its suite (13 cases ported to
cargo), the TypeScript Finding builder and vertebra selection rules of the
pickers, store rules, persistence parsing, hydrateReport. ESLint forbids
@faunosteo/domain in apps/app/src; the report:compare CLI keeps the frozen
domain until R4 (scripts/compare/sheet.ts). App suite 313/313 on the real
core (24 new tests: quarantine, degraded editor, core failures, N-1
reader); step6 goldens and the frozen envelopes unchanged.
2026-10-14 00:41:34 +02:00
..

packages/

Shared code lives here once it has a real owner and real content: an empty package would only add build configuration to maintain (IMPLEMENTATION_PLAN.md Step 2, FRONTEND_ARCHITECTURE.md §6). First package: supabase/ (Step 3).

Planned packages and the step that creates each one:

Package Content Created at
@faunosteo/domain Zod schemas: anatomical sheet document + integrity rules (created, Step 4); report document, entitlement capabilities later Step 4 (sheet model)
@faunosteo/anatomy legacy importer (created, Step 4b), curation pipeline: changeset → working draft + report migration map (created, Steps 4c/5), pure annotation-layer renderer @faunosteo/anatomy/render shared with the app (created, Step 5) Step 4b (importer)
@faunosteo/pdf browser-free PDF engine (created, Step 6): report archive export from explicit inputs (report, sheet snapshot, branding, labels, rasterizer), layered archive reading, SVG sanitiser, page renderers Step 6 (PDF archives)
@faunosteo/i18n FR/EN dictionaries (no React) + useT first second consumer (public-web or worker)
@faunosteo/supabase browser client factory, generated database types, PGlite harness running the pgTAP suite, sheet publish gate created, Step 3
@faunosteo/core-wasm loader of the Rust core compiled to WebAssembly (pkg/ built by pnpm wasm:build, git-ignored), TypeScript types of the contracts generated by ts-rs (committed), the R0 proofs (panic and stack traps, JSON.stringify parity, Zod readers, size budget) created, R0 (Rust review)

From R2 on, the Rust core (crates/core) replaces the TypeScript business logic of domain, anatomy and pdf phase by phase (docs/development/RUST_ARCHITECTURE_REVIEW.md Part VI); each TypeScript package is deleted in the phase that switches its last consumer. | @faunosteo/config | runtime config resolution shared by app, public-web, worker | with public-web | | @faunosteo/ui | UI primitives and design tokens | only when public-web reuses them |

Convention: a package has its own package.json (name, exports, types), tsconfig.json extending the root one, and tests beside its sources.