[Bug] Docker Compose project-name collision causes `down` to remove unrelated containers

**Bug Description**
Bug report drafted: Docker Compose project-name collision caused `down` to remove the user's real dev containers │
│ │ What happened: While building a new root-level docker-compose.yml (separate from an existing backend/compose.dev.yml), I initially gave it the same top-leve…

**Environment Info**
- Platform: win32
- Terminal: vscode
- Version: 2.1.250
- Feedback ID: fa0ed42d-67b8-47ea-b6a7-3768dd6c221d

**Errors**
```json
[]
```

Start by reviewing the root-level docker-compose.yml and backend/compose.dev.yml mentioned in the report, then reproduce the shared project-name scenario with Docker Compose on the reported environment if possible. Done means running down for one Compose project no longer removes unrelated containers from the other project.

Written by the indexing model from the issue text.