Reset storage revisions with a distinct baseline for fresh databases

[gurnben]

Summary

• Establish a shared revision-one baseline for the planned clean deployment without mistaking historical revision-one databases for the new schema. Packaged metadata supplies format, revision, and baseline identity to Python and SDK generators.
• Refuse legacy/mismatched metadata, empty stamps, and unstamped storage objects without rewriting them; document explicit rebuild/re-import and prepare contracts 0.36.0. Artifact schemas are unchanged.

Compatibility and rollout

This is a pre-GA storage compatibility boundary, not a live database reset or product GA release. Existing stores require an explicit clean bootstrap/re-import or separately reviewed migration. Stop and fence old clients first; they cannot enforce the new baseline. The baseline ID is not cryptographic schema attestation.

Companion SDK branch: traust-security/traust-sdk feat/storage-baseline-reset, pinned to this PR's commit 7cb54f28297860c1c1bd5d498fbeb0a5dcd5fdc0. Merge contracts first, then SDK. If the contracts commit is rewritten, update the SDK pin and regenerate before merging it.

Validation

• 365 Python tests passed, including real PostgreSQL 16 tests.
• Ruff checks/format, wheel metadata inclusion, and release metadata gate passed.
• Companion SDK verified bidirectional Python/Go initialization for SQLite and PostgreSQL with populated report saves.
• No SCI, RDS, cluster, or live ledger changes.

💘 Generated with Crush

[gurnben]

Companion SDK PR: traust-security/traust-sdk#7 . Merge this contracts PR first; the SDK pins the reviewed contracts commit and generates its baseline constants from it.