Improve initial flow and enabling/disabling

[Soph]

This changes a few things with entire:

• running entire, entire enable or entire configure in a repo that has no .entire folder yet, will bring you to the setup wizard
• running entire enable on a repo that is setup earlier already it only tells you that entire is enabled
• running entire disable then entire enable will disable -> enable entire now
• running entire configure let's you add more agents later but not remove them, for that you need to use entire configure --remove <agent> to actually remove it

Happy to hear thoughts.

[cursor]

PR Summary

Medium Risk
Alters core CLI control flow and settings read/write behavior (including local-vs-project settings), which could change enable/disable semantics across existing repos if edge cases aren’t covered.

Overview
Improves first-run UX by adding entire configure and making entire (no args) automatically launch the setup wizard when run inside a git repo that isn’t set up yet.

Refactors setup/enable behavior: enable now re-enables an existing repo without re-running full setup (and prints installed agents), while fresh repos funnel through a shared runSetupFlow; configure can add additional agents later (without allowing removal).

Changes setup detection to treat either .entire/settings.json or .entire/settings.local.json as “set up”, and adjusts runEnable to write enabled=true to local settings by default so disable → enable reliably re-enables via the local override. Minor prompt/output text and tests are updated accordingly.

^{Written by Cursor Bugbot for commit 354cb84. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Comment @cursor review or bugbot run to trigger another review on this PR

[Copilot]

Pull request overview

This PR refines the CLI’s first-run and enable/disable/configure flows so repositories without an .entire setup are guided into an initial configuration wizard, and subsequent commands behave more predictably once setup exists.

Changes:

• Add a shared “first-time setup flow” and invoke it from entire, entire enable, and entire configure when the repo isn’t set up yet.
• Make entire enable a no-op (with status output) when already enabled; otherwise re-enable by updating settings.
• Introduce settings.IsSetUpAny() to treat either project or local settings as “already set up”.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
cmd/entire/cli/strategy/common_test.go	Minor test formatting alignment.
cmd/entire/cli/setup_test.go	Update tests for new runEnable signature and adjusted prompt output.
cmd/entire/cli/setup.go	Adds configure/setup flows, changes enable behavior, and adds agent-add flow.
cmd/entire/cli/settings/settings.go	Adds IsSetUpAny() helper to detect setup via either settings file.
cmd/entire/cli/root.go	Runs setup wizard on bare entire in fresh repos; updates getting-started text; registers configure command.