[Bug] MCP Supabase tool uses wrong project instead of configured .env.local credentials

**Bug Description**
Ao verificar se uma função SQL tinha sido testada, o Claude Code consultou o projeto Supabase errado (via MCP) em vez do projeto configurado no .env.local do repositório, e apresentou dados desse projeto errado como se fossem do meu projeto.

**Environment Info**
- Platform: win32
- Terminal: windows-terminal
- Version: 2.1.241
- Feedback ID: 10723b50-4fc9-432e-9a67-39b710175c2d

**Errors**
```json
[{"error":"TelemetrySafeError: VirtualMessageList: itemKeys/messages length desync (keys=31 messages=30 range=[10,31))\n at X20 (B:/~BUN/root/cli:23311:34430)\n at mCg (B:/~BUN/root/cli:23311:27293)\n at Fr (B:/~BUN/root/cli:2993:21427)\n at qc (B:/~BUN/root/cli:2993:40531)\n at Ss (B:/~BUN/root/cli:2993:51459)\n at Oze (B:/~BUN/root/cli:2993:89122)\n at $7e (B:/~BUN/root/cli:2993:88070)\n at pae (B:/~BUN/root/cli:2993:87890)\n at pv (B:/~BUN/root/cli:2993:84152)\n at mt (B:/~BUN/root/cli:2993:6693)","timestamp":"2026-08-31T22:00:28.063Z"}]
```

Start by reproducing the MCP Supabase interaction on win32 with the repository's .env.local credentials, then compare the project queried with the configured project. Done means the tool consistently queries only the configured Supabase project and does not present data from another project; also determine whether the reported VirtualMessageList error is related.

Written by the indexing model from the issue text.