no-ref: ignore local tool artifacts and planning docs

[stephen-kintsugi]

Summary

• Ignore .full-review*/ and .serena/ local tool state, and keep docs/plans/ local per the org-wide planning-doc-placement rule.

Mirrors kintsugi-platform #14860.

Jira

no-ref

Tests

Not applicable, .gitignore only.

Document Checklist

n/a

---

Note

Low Risk
.gitignore-only change with no runtime or security impact.

Overview
Extends .gitignore so local, non-deliverable paths stay out of version control.

Adds ignores for .full-review*/ and .serena/ (regenerated agent/tool state) and docs/plans/ (planning docs kept local per the org planning-doc-placement rule). Aligns with kintsugi-platform #14860.

^{Reviewed by Cursor Bugbot for commit 186f249. Bugbot is set up for automated code reviews on this repo. Configure here.}

[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: 15 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: 8cc06c0f-dd29-423e-adbc-75980ccf5c7e

📥 Commits

Reviewing files that changed from the base of the PR and between fab9465 and 87e8252.

📒 Files selected for processing (1)

• .gitignore

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/no-ref/gitignore-local-tool-artifacts

---

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

[cursor]

PR Risk Assessment

Re-evaluated after synchronize (merge main into branch). Incremental change is branch-healing only; the substantive diff remains .gitignore additions with no production-code impact.

Cluster: .gitignore

• Files/codepaths: .gitignore only — adds .full-review*/, .serena/, and docs/plans/ ignore entries.
• Blast radius: none; affects what Git tracks locally, not runtime behavior.
• Reversibility: trivially reversible (revert 7 lines).
• Shared-resource pressure: none.
• Tests: exempt — tooling/config with no runtime behavior change.

Active approval: @michael-kintsugi approved on HEAD (186f2498). No re-approval needed.

risk_level: Very Low
review_required: false
reviewers: []
action_taken: no_action
rationale: Single-file .gitignore-only change adding local tool-state and planning-doc ignore patterns; no production code, infra, or runtime behavior modified. Trivially reversible with zero blast radius.

  

_{Sent by Cursor Automation: Assign PR reviewers & Assess Risk & Approve if Safe}