chore(entire): share agent hooks across worktrees

[anderskev]

Summary

Commit Entire’s project-level integration files so every Git worktree inherits session capture for all configured agents. The files were generated by the installed Entire CLI and match the integrations already active in the primary worktree.

Changes

Added

• Claude Code lifecycle hooks in .claude/settings.json.
• Codex lifecycle hooks and feature flag in .codex/.
• Cursor lifecycle hooks in .cursor/hooks.json.
• Entire’s generated OpenCode plugin.
• Entire’s generated Pi extension.

Motivation

Agent configuration previously existed only as ignored or untracked files in the primary checkout. Secondary worktrees therefore inherited the checkpoint remote but not the agent lifecycle hooks required for transcript and session attribution.

Testing

• Generated every integration with Entire CLI 0.8.42.
• Confirmed generated files match the currently installed primary-worktree files byte-for-byte.
• Parsed Claude, Codex, and Cursor configuration successfully.
• Parsed the Codex TOML feature configuration successfully.
• Verified OpenCode and Pi extensions invoke their Entire lifecycle hooks.

Checklist

• No checkpoint backend or checkpoint-remote setting changed.
• No active Entire session was stopped, cleaned, adopted, or committed.
• Only the six agent integration files are included.

[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: 28 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: ea0cc44b-edea-4def-941f-454080f9ae48

📥 Commits

Reviewing files that changed from the base of the PR and between 60be2d1 and 982b4d1.

📒 Files selected for processing (6)

• .claude/settings.json
• .codex/config.toml
• .codex/hooks.json
• .cursor/hooks.json
• .opencode/plugins/entire.ts
• .pi/extensions/entire/index.ts

---

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