chore: add git worktree docs and roborev configuration

[ian-flores]

Summary

• Add Git Worktrees section to CLAUDE.md formalizing the namespaced worktree convention (team-operator-<branch>)
• Add .roborev.toml configuring automatic code reviews with claude-code agent

Test plan

• Verify worktree creation with namespaced path works
• Verify just build and just test work in a worktree
• Verify roborev triggers on commit (roborev status)

[claude]

Claude finished @ian-flores's task —— View job

---

Review Complete

• Gather context and read review guidelines
• Analyze the diff and changed files
• Submit review with inline feedback

Reviewed both changed files (.roborev.toml and CLAUDE.md). Left one minor suggestion about the worktree path documentation clarity. No blocking issues found.

[claude]

Review Summary

Clean, well-structured additions. Two minor observations:

CLAUDE.md — worktree path clarity
The relative path ../../.worktrees/ and the description referencing ptd-workspace/.worktrees/ assume a specific parent directory layout. If someone clones to a different location, ../../.worktrees/ won't resolve to ptd-workspace/.worktrees/. Consider either:

• Adding a note that the repo is expected to live at ptd-workspace/team-operator/, or
• Removing the ptd-workspace/ mention and relying solely on the relative ../../.worktrees/ form with a brief explanation of the assumed structure.

.roborev.toml
Minimal and straightforward — no concerns.

Overall this looks good to merge.

[statik]

@ian-flores this looks good to me. would you be up for adding a note to CONTRIBUTING.md?

I was thinking something like

roborev code review

If you would like to use roborev continuous code review, you will need to run roborev install-hook to install the commit hooks into your copy of the repo.

---

or, alternatively, should we put in CLAUDE.md a check or prompt asking the user if they want to install and use roborev?

[Lytol]

You could argue that the worktree stuff better belongs in a CLAUDE.local.md since it's a personal workflow thing, but I'm also fine with having it be a project norm. Your call, approved!