# Before: main 5b89a53585

## t3 auth session issue --token-only
```
== commit 5b89a53585, home /tmp/issue-lead-26696-r1/runs/20261028-224027-87931/home, cli: auth session issue --token-only
== 1. start the server
72 WaitingLinkRequestIndex
71 PeerLinkFence
== 2. newer CLI: same checkout plus 073_CliOnlyProbe
cli exit=0
-- cli stderr (last 5):
-- ledger:
73 CliOnlyProbe
72 WaitingLinkRequestIndex
server still running: yes
== 3. restart the unmodified server
started
Database migration history diverges from this build; recorded migration ids are skipped, not reconciled by name.
== 4. a later build ships a different 073 (ReleasedFeature)
start failed (pid alive: no)
would skip required schema migrations: 73_ReleasedFeature (recorded: CliOnlyProbe). The migrator skips every id up to the highest recorded id (73), regardless of name. It was probably written by a dif
run dir: /tmp/issue-lead-26696-r1/runs/20261028-224027-87931
```
## t3 pair --ttl 5m, t3 environment list
```
== commit 5b89a53585, home /tmp/issue-lead-26696-r1/runs/20261028-224116-89375/home, cli: pair --ttl 5m
== 1. start the server
72 WaitingLinkRequestIndex
71 PeerLinkFence
== 2. newer CLI: same checkout plus 073_CliOnlyProbe
cli exit=0
-- cli stderr (last 5):
-- ledger:
73 CliOnlyProbe
72 WaitingLinkRequestIndex
server still running: yes
== 3. restart the unmodified server
started
Database migration history diverges from this build; recorded migration ids are skipped, not reconciled by name.
== 4. a later build ships a different 073 (ReleasedFeature)
start failed (pid alive: no)
would skip required schema migrations: 73_ReleasedFeature (recorded: CliOnlyProbe). The migrator skips every id up to the highest recorded id (73), regardless of name. It was probably written by a dif
run dir: /tmp/issue-lead-26696-r1/runs/20261028-224116-89375
== commit 5b89a53585, home /tmp/issue-lead-26696-r1/runs/20261028-224206-90771/home, cli: environment list
== 1. start the server
72 WaitingLinkRequestIndex
71 PeerLinkFence
== 2. newer CLI: same checkout plus 073_CliOnlyProbe
cli exit=0
-- cli stderr (last 5):
-- ledger:
73 CliOnlyProbe
72 WaitingLinkRequestIndex
server still running: yes
== 3. restart the unmodified server
started
Database migration history diverges from this build; recorded migration ids are skipped, not reconciled by name.
== 4. a later build ships a different 073 (ReleasedFeature)
start failed (pid alive: no)
would skip required schema migrations: 73_ReleasedFeature (recorded: CliOnlyProbe). The migrator skips every id up to the highest recorded id (73), regardless of name. It was probably written by a dif
run dir: /tmp/issue-lead-26696-r1/runs/20261028-224206-90771
```

# After: fix/issue-26696 823987682c

## t3 auth session issue --token-only (newer CLI, server running)
```
== commit 823987682c, home /tmp/issue-lead-26696-r1/runs/20261029-012053-120617/home, cli: auth session issue --token-only
== 1. start the server
72 WaitingLinkRequestIndex
71 PeerLinkFence
== 2. newer CLI: same checkout plus 073_CliOnlyProbe
cli exit=1
-- cli stderr (last 5):
-- ledger:
72 WaitingLinkRequestIndex
71 PeerLinkFence
server still running: yes
== 3. restart the unmodified server
started
== 4. a later build ships a different 073 (ReleasedFeature)
started ok
run dir: /tmp/issue-lead-26696-r1/runs/20261029-012053-120617

ERROR (#2): ServerOwnsDatabaseError: Another T3 Code process, usually a running server, owns /tmp/issue-lead-26696-r1/runs/20261029-012053-120617/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.
```
## Control: nothing pending, server running (same head)
```
auth session issue exit=0 (token printed); pair --ttl 5m exit=0; ledger max 72
```