# test\(server\): build path expectations from the Path the code resolves with · pingdotgg/t3code

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

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

Visibility: public

Requested revision: de8410c3f37ff5d450a60d82e48ec67cad1d8a61

Requested commit: de8410c3f37ff5d450a60d82e48ec67cad1d8a61

Commit: de8410c3f37ff5d450a60d82e48ec67cad1d8a61

Tree: 42cb975e2f82b02d51fbd8bfc86c32535ed1e545

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
test(server): build path expectations from the Path the code resolves with

ProviderInstanceRegistryLive, AntigravityAdapter, and
SourceControlRepositoryService asserted literal posix paths against values
the code under test had run through Path.resolve or Path.join, so on Windows
the received side carried a drive letter and backslashes. Resolve the
expectation with the same Path. cli/config tolerates the bootstrap fd
already being closed where the reader has no /proc path and consumes the fd
itself, and WorkspaceFileSystem skips its FIFO case on Windows.

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

```

## Parents

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

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