Files
faunosteo/.claude/tasks/contracts/2026-10-25-rust-r5-7-cleanup.md
T
bchanot 4e0a6c04d6 docs(docs): R5.7 census, ledger, reproducibility, RUST.md 11.23
CLAUDE.md, WORKSPACE, packages/README, README, sheet model, SUPABASE, TEST_STRATEGY,
PDF-FORMAT and ANNOTATION-RENDERING follow the deletion; RUST.md 11.23 records the census,
counts, the historical TS replay procedure and hashes; CHANGELOG, TODO, R5.7 plan and
contract.
2026-10-25 04:00:15 +01:00

4.0 KiB

CONTRACT: R5.7 consumer census and deletion of packages/anatomy and packages/domain, owner brief 2026-10-25 « Validation R5.6 et autorisation R5.7 »

  • branch feature/rust-r5-pipeline-core, base 756b7ef (R5.6 active since 9e87016)
  • plan .claude/tasks/plans/2026-10-25-rust-r5-7-cleanup.md

Clauses

C1. Census. Every consumer of packages/anatomy and packages/domain outside them is listed (runtime and type imports, fixtures read by Rust, TS tests, oracles and goldens, pnpm scripts, build dependencies, seed scripts, docs, dev and check tools, historical references). Nothing still required by an active feature is deleted.

C2. Matrices. crates/core/tests/curation/FILES.tsv names every deleted tracked file with its Rust counterpart or the reason it goes; crates/core/tests/curation/LEDGER.tsv has one row per TS case of both packages at 756b7ef (407), with the case's contract, old location, equivalent after the deletion, status ported / replaced / kept / deleted (with the justification), and the historical reference kept. No row is a gap: a contract still relevant and uncovered is ported first.

C3. Fixtures. report-v2.full.json and report-v2.minimal.json move under crates/core/tests/fixtures/ with their bytes unchanged (sha256 before = after, recorded); the Rust readers use the new place. No oracle, golden, frozen digest, migration data, N-1 reader or reference PDF is changed, regenerated or removed; a moved reference file keeps its sha256.

C4. Active checks preserved. The contracts the brief §5 lists stay covered by tests that run in pnpm rust:check or pnpm check:all (sheet model validation, reference integrity, deterministic UUIDs, legacy catalog conversion, changeset application, migration map, statistics, seed SQL, SVG rendering, RFC 8785, historical aliases, PDF import and export, old archive compatibility); the application and interface suites keep passing; test counts before and after are measured and documented.

C5. Historical reproducibility. The documentation names the reference commits of the TypeScript pipeline, the versions (Node, pnpm, dependencies), the historical generation and comparison commands, the isolated-worktree procedure and the expected sha256 of the artifacts; the procedure is rehearsed once; the old engine is not reintroduced in the current tree.

C6. Dependencies and scripts. The two packages' own dependencies leave the lockfile through pnpm install; @xmldom/xmldom and tsx are gone; root prettier stays (used by pnpm format and db:types); pnpm import:equine stays the Rust pipeline; import:equine:legacy and assets:upload:legacy are removed; no other dependency changes major version; the lockfile installs with --frozen-lockfile.

C7. Census tests. r4.census.test.ts proves xmldom and the TS engines are no active dependency, and cannot pass on a lockfile or tree that reintroduces them (a non-vacuity check); a census proves no production path (app, glue, supabase package, Dockerfile, Vite/TS config) imports a deleted engine, and that the two matrices agree with the tree.

C8. Docs. CLAUDE.md, WORKSPACE.md, packages/README.md, RUST.md §11, CHANGELOG, TODO, the curation commands and the test registers are updated; the seed SQL header is kept (frozen bytes) and explained beside it; audits are append-only; the brief §10 follow-ups stay tracked (rollback limit, DEV hardening, migration-map cascade debt, direct export API trust boundary, SQL checks before public exposure, accepted LOW items).

C9. Checks. pnpm install --frozen-lockfile, pnpm rust:check, pnpm check:all, pnpm import:equine --check (0 difference), the RFC 8785, alias and archive suites, PDF and report:compare, the N-1 reader, the moved fixtures, the sheet and seed integrity suites, and the absence of any import of the deleted packages, all green on the final state.

C10. Limits. Branch only; no merge, no release, no deploy, no Supabase DEV data change, no migration, no new feature; no seed byte changed.