[Feature]: Watch a parent folder and offer to add new repositories as projects

[gustavolpaiva]

Problem or use case

I keep all my projects under one parent folder (for example ~/dev/<project>). As far as I can tell, Orca only knows about repositories that were added explicitly — through the UI or orca repo add --path. When a new repository appears in that folder (a fresh git clone or a new project), it does not show up in the Projects sidebar until it is added by hand.

In my case, 16 repositories were registered and 2 other Git repositories in the same parent folder were not registered, so they did not appear in the sidebar. I checked orca agent-context --json (Orca 1.4.200) and found no command to scan or watch a folder for repositories.

Proposed solution

A per-host setting listing one or more watched parent folders:

• Orca scans each watched folder (depth 1 by default, configurable) for Git repositories that are not registered yet.
• For each new one, Orca asks: Add · Not now · Never for this folder. Asking should be the default; adding automatically could be an option.
• "Never" is remembered per path, so throwaway clones don't keep asking.
• Hidden folders (.worktrees, .wt, …) and folders without .git are ignored by default.
• Orca waits until a clone has finished (for example, HEAD resolves to a commit and there is no index.lock) before asking.

CLI parity would help automation:

orca repo scan --root ~/dev --json   # list unregistered git repos under a root
orca repo watch add ~/dev            # manage watched roots

Alternatives or additional context

• [Feature]: Multi-repo support — show Git status/tree for nested repos under the opened workspace folder #13989 asks for nested-repository detection inside an opened workspace (Git panel). This request is about the Projects sidebar registry instead: discovering new top-level repositories under a parent folder and registering them.
• PR feat(cli): add --kind folder to repo add #13359 (still open) proposes orca repo add --kind folder. This request is about discovery, not about the project kind.
• Workaround I use today: a macOS launchd agent that watches the folder, checks orca repo list --json, asks in a native dialog, and runs orca repo add --path if I accept. It is macOS-specific and lives outside Orca.