[codex] Add git worktree workspace isolation

[senamakel]

Summary

• add a concrete GitWorktreeIsolation provider for harness workspaces
• include create/list/status/diff/remove helpers plus overlap detection
• cover real git worktree behavior with dependency-free temp repo tests

Validation

• cargo fmt --check
• timeout 180s cargo clippy --all-targets -- -D warnings
• timeout 180s cargo test create_then_status_reports_clean_worktree
• timeout 180s cargo test list_includes_created_worktrees
• timeout 180s cargo test status_detects_dirty_changes
• timeout 180s cargo test diff_summary_lists_tracked_and_untracked
• timeout 180s cargo test remove_
• timeout 180s cargo test detect_overlaps
• timeout 180s cargo test sanitize_run_id

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 948e335f-a165-4998-80eb-c23b0fc19a03

📥 Commits

Reviewing files that changed from the base of the PR and between e72036d and 1c788ff.

📒 Files selected for processing (3)

• src/harness/workspace/git.rs
• src/harness/workspace/git/test.rs
• src/harness/workspace/mod.rs

---

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1c788ffc0c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Keep worktrees out of the main checkout

In repos that do not already ignore .claude (including this repo), placing linked checkouts at this path makes git worktree add create an untracked .claude/ in the primary checkout, and git worktree remove leaves the empty parent directories behind. That means simply preparing/cleaning a workspace dirties the user's main tree and can contaminate status/diff based workflows; put the worktree directory outside the tracked checkout or ensure it is excluded and removed.

Useful? React with 👍 / 👎.