conductor and gemini-cli plan mode

[kurokirasama]

In gemini-cli 0.33.1 and conductor 0.4.1, the track creation workflow includes a redundant prompt loop after exiting plan mode. When a new track starts, conductor enters Gemini plan mode via a shell call to gather information and generate the track.md file. This works as intended, but once control returns to the main gemini-cli environment, the CLI detects the newly created file and treats it as an existing track. It then prompts the user to either update the track or create a new one, which adds an unnecessary step to the process. The handover logic needs refinement so that gemini-cli recognizes the file generated during plan mode as part of the current session and proceeds without additional confirmation.