The suites were written as executable contracts for the implementation
process. Three of their checks only policed that process and would fail on
any legitimate future change:
- schema.rs/migration.rs/backup.rs pinned by SHA-256
- the impl Database write-surface symbol inventory pinned by name
- specific restore test function names asserted to exist
The behavioural assertions, the DML column-authority scanner, the type
barriers and the pinned oracle fixture hashes are kept: those catch real
regressions.
Headers are rewritten as contract documentation; the stale red/green
ledgers no longer described reality.
The handoff, contracts, restructure ruling, reviewer spec and main-project
contract were scaffolding for the implementation process, not deliverables.
Their technical invariants now live in the code and the certification suites.
Kept: the extensions design appendix (future work) and the restore hardening
debt register (known issues in shipped code).
Certification suite comments that pointed at the removed restructure ruling
are made self-contained.
SaladDay