Conductor setup incorrectly assumes a sibling directory is a brownfield project

[Sajmani]

n my home directory I have src/birdsync, an established project, and src/phorg, a new, empty project. I ran /conductor:setup in src/phorg, and Conductor asked to examine the sibling birdsync directory. I approved this, and Conductor then assumed that I was working on the birdsync project. That's incorrect; I'm working on a new project (phorg). Was I supposed to decline permission to Conductor to examine the birdsync directory? I mean to start a greenfield project in phorg.

[Sajmani]

Aha, this may be user error! I think I may have accidentally started Gemini CLI from my src directory instead of from src/phorg. If so, this behavior is reasonable. Feel free to close this if it's working as intended.