9050913e68
On a remote backend a new chat starts in the remembered workspace, and setCurrentCwd persisted that key on every call — including the six paths that merely follow a conversation (resume settling, warm switch, stored-row preview, agent relocation, boot seed, resolved new-chat default). So opening a chat inside a project quietly made that project the destination for the next "New session", which is the half of the report the resolver fix does not reach: a Windows desktop driving a WSL gateway is a remote connection. setCurrentCwdTransient already meant "move the path, claim nothing" — the following paths now use it, and setCurrentCwd is reserved for a workspace the user actually named.