Improved entire enable flow on folders that are not git repos yet

[Soph]

Summary

Lets entire enable bootstrap a brand-new folder all the way to a working repo — git init, agent setup, initial commit, and a matching GitHub repository via the gh CLI — instead of exiting with "Not a git repository".

Flow

~ cd my-new-project
~ entire enable

No git repository in "my-new-project". Initialize one here? [Y/n]

━ Setting up git repository
✓ Initialized empty git repository

Create a matching repository on GitHub? [Y/n]
Choose the GitHub owner for the new repository:
  > my-username
    my-org
Repository name:         [my-new-project]
Repository visibility:   [Private / Public / Internal]
Initial commit:
  > Commit with default message "Initial commit"
    Customize message...
    Skip — I'll commit manually later

━ Enabling Entire
Agent: Claude Code

Installed 7 hooks for Claude Code
✓ Project configured (.entire/settings.json)
✓ Created orphan branch 'entire/checkpoints/v1' for session metadata

━ Publishing to GitHub
✓ Created initial commit (Initial commit)
✓ Created my-username/my-new-project (private)
  https://github.com/my-username/my-new-project
✓ Pushed initial commit to origin

Done.

All prompts go through NewAccessibleForm, so ACCESSIBLE=1 works
as expected.

Flow details worth calling out

• Fresh-machine safety — if git identity isn't configured anywhere,
  we source user.name / user.email from gh api user (falling back
  to the GitHub no-reply address when the user's email is private),
  then prompt, then fail with a pointer to git config --global.
  Values are written to the local repo config only. The initial commit
  also runs with -c commit.gpgsign=false so a broken or absent signer
  doesn't block the first commit.
• Default branch — the pre-push hook installed during agent setup
  would otherwise push entire/checkpoints/v1 alongside main on the
  first push, which GitHub then picks as the repo's default branch. The
  initial push uses git push -q --no-verify -u origin HEAD; only
  main lands on the remote and the checkpoint metadata branch is
  pushed normally on subsequent pushes.
• Two-phase bootstrap — phase 1 (git init, identity, gather GH
  choices) runs before agent setup; phase 2 (git add -A + commit +
  gh repo create + push) runs after, so the initial commit captures
  .entire/, .claude/, agent hooks, and every other file setup
  writes.
• Error paths —
  • gh missing or unauthenticated → print a hint (brew install gh && gh auth login) and fall through to local-only bootstrap.
  • Ctrl+C before git init → legacy "Not a git repository" error.
  • Ctrl+C after git init → new "Bootstrap cancelled. A local git repository has been initialized but setup didn't complete. Run entire enable again to continue." message.
  • Setup fails after init → skip the commit / push; files remain untracked, user can fix and rerun.
  • Skipping the commit still creates the GitHub repo and prints the exact git add -A && git commit && git push commands to finish.

Flags

All optional; each suppresses the matching interactive prompt, so
automation can drive the flow end-to-end without a TTY.

Flag	Effect
--init-repo	Accept the git init prompt
--no-init-repo	Decline the git init prompt (mutually exclusive with --init-repo)
--repo-name <name>	GitHub repo name (validated against GitHub's charset)
--repo-owner <owner>	GitHub user or org login
--repo-visibility <public|private|internal>	internal only valid for orgs
--no-github	Local git init + initial commit only; skip GitHub
--initial-commit-message <msg>	Override the default commit message
--skip-initial-commit	Skip the initial commit (mutually exclusive with --initial-commit-message)

Setting any of --repo-name / --repo-owner / --repo-visibility
implicitly answers "yes" to the GitHub-confirm prompt.

Notes for reviewers

• gh is shelled out via exec.Command rather than pulled in as a Go
  dep. All calls go through a bootstrapRunner interface so unit tests
  don't hit the network.
• The commit-message prompt is a 3-option huh.NewSelect (default /
  customize / skip) rather than a freeform input. "Skip" was the only
  freeform input where a skip shortcut made sense — repo name and
  identity have no sensible "no value" semantics — so we didn't try to
  generalize it.
• The full matrix of branches (confirm init → GH yes/no → commit
  default/custom/skip → various flag combinations) is covered by unit
  tests with a mocked bootstrapRunner. Two integration-style tests
  (TestBootstrap_FreshMachine_RealGit,
  TestBootstrap_FreshMachine_NoIdentity_RealGit) run real
  git init/git commit against a temp dir isolated via HOME +
  GIT_CONFIG_GLOBAL to prove the identity + gpgsign fixes end-to-end.

Test plan

• mise run check (fmt + lint + unit + integration + Vogon canary + roger-roger external-agent canary) — already green locally
• Manual: fresh empty folder → entire enable with no flags walks through prompts and pushes to GitHub; default branch on the remote is main, no entire/checkpoints/v1 on the remote
• Manual: fresh folder → entire enable --init-repo --no-github --initial-commit-message "init" --agent claude-code completes non-interactively, no GitHub call, one commit
• Manual: fresh folder → entire enable --init-repo --no-github --skip-initial-commit leaves files unstaged and prints the manual-commit hint
• Manual: Ctrl+C at owner/name/visibility/commit-message prompt → "Bootstrap cancelled" message, .git/ still in place
• Manual: entire enable --init-repo --no-init-repo → cobra's mutually-exclusive error
• Manual: existing git repo → entire enable behaves exactly as before (bootstrap skipped entirely)
• Manual: machine without gh → hint printed, local git init + initial commit still succeed

[Copilot]

Pull request overview

This PR extends entire enable to support bootstrapping a brand-new folder into a usable git repository (including an initial commit) and optionally creating/pushing to a matching GitHub repository via the gh CLI, instead of immediately failing when no git repo is present.

Changes:

• Add a GitHub bootstrap flow (git init, optional gh repo create, initial commit with identity + commit.gpgsign=false handling).
• Add entire enable flags to drive the bootstrap flow non-interactively (--init-repo, --no-github, --repo-*, etc.).
• Add unit + regression-style tests covering slugification/validation, gh helpers, bootstrap paths, and fresh-machine git identity behavior.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 6 comments.

File	Description
cmd/entire/cli/setup_github.go	Implements the new bootstrap flow (git init + optional gh repo creation + initial commit + identity handling).
cmd/entire/cli/setup_github_test.go	Adds tests for repo name handling, gh helpers, bootstrap behavior, and real-git regressions.
cmd/entire/cli/setup.go	Hooks the bootstrap flow into entire enable and adds new bootstrap-related flags.

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ 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

^{Reviewed by Cursor Bugbot for commit 7023b4e. Configure here.}