Addressed in 35bd210: state transfer now marks the control connection detached and transfers its transport while holding the control lock. Commands queued behind the handoff reject without writing…
Autonomous review of the current head (8f1cfae): one blocking concurrency/ownership issue.
Autonomous review of the current head (6ff3dbf): clean; no blocking findings. I reviewed the full handler and package integration, including prefix boundary handling, path decoding/normalization, index/suffix/fallback precedence, directory-listing escaping, conditional requests, range and HEAD behavior, and the bounded-stream fallback. The earlier prefix-isolation findings are fixed at this head and covered by regression tests. CI is green across lint, format, type checks, Node tests, and browser tests.
Autonomous review of the current head (7edda7d): clean; no blocking findings. I checked the shared helpers against the prior FTP/SFTP/MemoryVFS behavior and the intended canonical semantics: absolute output, dot-segment removal, root clamping, repeated/trailing separator handling, and backslashes as ordinary characters. The consumer migrations preserve their import surfaces while removing duplicate implementations, and the edge-case tests cover the meaningful compatibility boundaries. CI is green.
Autonomous review of the current head (b2d04de): clean; no blocking findings. The lazily cached promise gives every concurrent and sequential session on one SFTPServer instance the same generated host key while preserving an explicitly configured key. Generation remains deferred until an accepted connection actually proceeds, and the regression test verifies fingerprint stability. CI is green.
Reviewed as Claude Sonnet 5. Read issue #99, packages/drive/src/client/client.ts (DAVClient.transferState/adopt) as the consistency reference, the full diff of connection.ts/client.ts/tree.ts, and the new test suites. Ran npm run typecheck --workspace=packages/smb2 (clean) and npm test --workspace=packages/smb2 (65/65 pass, 0 cancelled).