feat: return ok=true with git_repo=false when bg status is run outside a git repo

[svarlamov]

Summary

When git ai bg status is run outside a git repository, it previously returned ok: false with a git rev-parse error from the daemon. This change adds an early check in the client-side handle_status function: before contacting the daemon, it verifies the path is inside a git repo using find_repository_in_path. If not, it skips the family-level status query but still checks daemon health via daemon_is_up, returning:

{
  "ok": true,
  "git_repo": false,
  "daemon_running": true
}

Normal in-repo behavior is unchanged.

Review & Testing Checklist for Human

• Response shape consistency: The early-return response ({ "ok": true, "git_repo": false, "daemon_running": bool }) is a different shape than the normal ControlResponse ({ "ok", "seq", "data", "error" }). Verify that all consumers of bg status output can handle this divergent schema, or decide if git_repo/daemon_running should be nested inside the standard ControlResponse structure instead.
• Error conflation: find_repository_in_path(...).is_err() treats any error (permissions, git binary missing, corrupt repo, etc.) as "not a git repo." Consider whether some errors should still surface as failures rather than being silently mapped to git_repo: false.
• Manual test: Run git ai bg status from / or /tmp (outside any repo) and confirm the new JSON output includes daemon_running. Then run it inside a repo and confirm normal behavior is unchanged.

Notes

• daemon_is_up checks socket connectivity (control + trace sockets respond within 100ms); it does not issue a full control request.
• No new tests were added for this path. The daemon integration tests don't cover the client-side early return.

Link to Devin session: https://app.devin.ai/sessions/37f5a9c05ad346f587f3cf512e4e58f5
Requested by: @svarlamov

---

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.

[devin-ai-integration]

Test Results

Tested locally by building the debug binary and running git ai bg status from different contexts.

Primary: bg status outside a git repo

Test	Result
Outside a git repo (/tmp)	PASSED — exit code 0, {"ok": true, "git_repo": false, "daemon_running": false}
--repo /tmp flag	PASSED — exit code 0, same graceful response

Regression: bg status inside a git repo

Test	Result
Inside a git repo (repos/git-ai)	PASSED — exit code 1, daemon socket timeout error (confirms early return NOT triggered for valid repos)

CI Note: One flaky failure in subdirs::test_commit_with_mixed_files_with_c_flag_in_worktree (daemon session timeout) — unrelated to this change. All lint, format, coverage, and security checks pass.

Devin session