Migrate with an explicit review

The beta CLI implements a bounded local v1-to-v2 migration workflow: review, row accounting, application, read selection and rollback. It does not automatically convert a production database or a native sensor archive.

npx @disclosureos/cli@2.0.0-beta.4 migrate --help

Unknown fields, conflicting revisions and quarantined rows require explicit handling. Retain original material and migration receipts. Historical scores stay separate from v2 rankings.

The supported synthetic software acceptance suite passes ten scenarios, including interrupted application, stale-head rejection, rollback and corruption handling. This establishes the tested local software behavior; it does not establish partner mapping fidelity or scientific reproducibility.

Read the bounded migration closeout before planning a migration. Existing v1 documentation and historical schema URLs remain available.