T3 Code CLI / server evidence — AFTER
Commit: 111f11209c6331c58f1c3312a315a7e82c3c5218
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 1
[07:05:22.393] ERROR (#2): ServerOwnsDatabaseError: Another T3 Code process, usually a running server, owns <disposable-home>/userdata, and this CLI would change its database schema. Use the `t3` that matches the running server, or stop that server, then retry. The database was not changed.
    at Object.ServerAlreadyRunningError (file://<checkout>/apps/server/src/persistence/Sqlite.ts:33:21)
    at file://<checkout>/node_modules/.pnpm/effect@4.1.2/node_modules/effect/dist/internal/effect.js:1499:27
    at SqlitePersistence.runMigrationsAsOwner (file://<checkout>/apps/server/src/persistence/Sqlite.ts:118:36)
    at SqlitePersistence.runMigrationsAsOwner (definition) (file://<checkout>/apps/server/src/persistence/Sqlite.ts:26:37)
    at Sqlite.setup (file://<checkout>/apps/server/src/persistence/Sqlite.ts:70:20)
    at auth.runWithEnvironmentAuth (file://<checkout>/apps/server/src/cli/auth.ts:180:5)
    at auth.runWithEnvironmentAuth (definition) (file://<checkout>/apps/server/src/cli/auth.ts:27:39)
Schema + complete migration ledger unchanged: true
Ledger maximum ID: 80; probe table present: false
$ t3 pair --ttl 5m --base-dir <disposable-home>
exit 1
[07:05:23.071] ERROR (#2): ServerOwnsDatabaseError: Another T3 Code process, usually a running server, owns <disposable-home>/userdata, and this CLI would change its database schema. Use the `t3` that matches the running server, or stop that server, then retry. The database was not changed.
    at Object.ServerAlreadyRunningError (file://<checkout>/apps/server/src/persistence/Sqlite.ts:33:21)
    at file://<checkout>/node_modules/.pnpm/effect@4.1.2/node_modules/effect/dist/internal/effect.js:1499:27
    at SqlitePersistence.runMigrationsAsOwner (file://<checkout>/apps/server/src/persistence/Sqlite.ts:118:36)
    at SqlitePersistence.runMigrationsAsOwner (definition) (file://<checkout>/apps/server/src/persistence/Sqlite.ts:26:37)
    at Sqlite.setup (file://<checkout>/apps/server/src/persistence/Sqlite.ts:70:20)
    at pair.mintPairingLink (file://<checkout>/apps/server/src/cli/pair.ts:549:29)
    at pair.mintPairingLink (definition) (file://<checkout>/apps/server/src/cli/pair.ts:435:32)
Schema + complete migration ledger unchanged: true
Ledger maximum ID: 80; probe table present: false
$ t3 environment list --base-dir <disposable-home>
exit 1
[07:05:23.690] ERROR (#2): ServerOwnsDatabaseError: Another T3 Code process, usually a running server, owns <disposable-home>/userdata, and this CLI would change its database schema. Use the `t3` that matches the running server, or stop that server, then retry. The database was not changed.
    at Object.ServerAlreadyRunningError (file://<checkout>/apps/server/src/persistence/Sqlite.ts:33:21)
    at file://<checkout>/node_modules/.pnpm/effect@4.1.2/node_modules/effect/dist/internal/effect.js:1499:27
    at SqlitePersistence.runMigrationsAsOwner (file://<checkout>/apps/server/src/persistence/Sqlite.ts:118:36)
    at SqlitePersistence.runMigrationsAsOwner (definition) (file://<checkout>/apps/server/src/persistence/Sqlite.ts:26:37)
    at Sqlite.setup (file://<checkout>/apps/server/src/persistence/Sqlite.ts:70:20)
    at environment.runWithPeerLinks (file://<checkout>/apps/server/src/cli/environment.ts:129:5)
    at environment.runWithPeerLinks (definition) (file://<checkout>/apps/server/src/cli/environment.ts:27:33)
Schema + complete migration ledger unchanged: true
Ledger maximum ID: 80; probe table present: false
Original server remains running: true
Stop original server. Start a build with conflicting ID 81_ServerEvidenceProbe.
Conflicting build starts successfully; migration 81_ServerEvidenceProbe recorded.
Ledger tail: (81, 'ServerEvidenceProbe')