T3 Code CLI / server evidence — BEFORE
Commit: f7b81e1d1115bc7284b39161d3cd6c7f3184eb1c
Environment: Linux; real Node CLI and HTTP server; fresh synthetic T3 home.
Starting server with migration manifest through ID 80.
Server ready; ownership held by live process.
Initial ledger: 80 rows; maximum migration ID 80.
CONTROL: matching server / CLI manifests
$ t3 auth session issue --json --base-dir <disposable-home>
exit 0; command succeeded (credential output withheld)
$ t3 pair --ttl 5m --base-dir <disposable-home>
exit 0; command succeeded (credential output withheld)
CLI-only fixture: append migration 81_CliEvidenceProbe; CREATE TABLE cli_evidence_probe(value TEXT).
$ t3 auth session issue --json --base-dir <disposable-home>
exit 0; command succeeded (credential output withheld)
Schema + complete migration ledger unchanged: false
Ledger maximum ID: 81; probe table present: true
$ t3 pair --ttl 5m --base-dir <disposable-home>
exit 0; command succeeded (credential output withheld)
Schema + complete migration ledger unchanged: true
Ledger maximum ID: 81; probe table present: true
$ t3 environment list --base-dir <disposable-home>
exit 0; command succeeded (credential output withheld)
Schema + complete migration ledger unchanged: true
Ledger maximum ID: 81; probe table present: true
Original server remains running: true
Stop original server. Start a build with conflicting ID 81_ServerEvidenceProbe.
Conflicting server exit: 1
[07:05:17.741] ERROR (#2): MigrationError: This database's migration history would skip required schema migrations: 81_ServerEvidenceProbe (recorded: CliEvidenceProbe). The migrator skips every id up to the highest recorded id (81), regardless of name. It was probably written by a different build. Start the build that wrote it, or report this migration history so an upgrade path can be added.