# test\(server\): migrate-dev-db refuses a legacy thread committed after the guard · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/44bd595e77a0622ab69bcdd0f34970b9b252bbc6)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: 44bd595e77a0622ab69bcdd0f34970b9b252bbc6

Requested commit: 44bd595e77a0622ab69bcdd0f34970b9b252bbc6

Commit: 44bd595e77a0622ab69bcdd0f34970b9b252bbc6

Tree: 1e353b66886a8042fb2dfc1c5f00a618201e7f7e

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
test(server): migrate-dev-db refuses a legacy thread committed after the guard

An old V1 server on an empty pre-V2 source can create its first thread
after ensureNoPendingLegacyThreads passes but before copySourceSlice reads
the source. The unfiltered copy takes the row, migrations and prune drop
it, and the run exits 0. Red test: the race is injected at the destination
state-dir makeDirectory, the first FileSystem call after the guard.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

```

## Parents

- [9bf8c50e9a2976569d06a3cdbb2fedc6919fe1f2](https://git.cafe/pingdotgg/t3code/commit/9bf8c50e9a2976569d06a3cdbb2fedc6919fe1f2?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/44bd595e77a0622ab69bcdd0f34970b9b252bbc6?format=markdown)