[Chore] Append scope-boundary instruction to CodeRabbit global path instructions

[zoomote]

​Created by Roomote. Follow up by mentioning @roomote, in the web UI, or in Discord.

Related GitHub Issue

No linked issue — this is a directly requested CodeRabbit configuration change.

Description

Appends a scope-boundary instruction to the existing global **/* entry in reviews.path_instructions in .coderabbit.yaml. No existing instructions were removed or reworded; the new text is appended verbatim:

Treat the linked issue and this PR description as the scope boundary. When a confirmed defect needs work beyond that boundary and this PR does not create the hazard, do not request changes for it. List it once in the walkthrough under follow-up candidates, with one line for the trigger.

This asks CodeRabbit to keep its change requests within the scope of the linked issue and PR description, and to surface out-of-scope confirmed defects once in the walkthrough as follow-up candidates instead of blocking the PR.

reviews.profile (assertive), reviews.request_changes_workflow, and chat.allow_non_org_members are unchanged.

Test Procedure

• Parsed .coderabbit.yaml with the yaml Node package (yaml@2.9.0): parses successfully; reviews.path_instructions still has 11 entries.
• Verified via the parsed document that the **/* entry's instructions end with the appended text verbatim, and that profile: assertive, request_changes_workflow: true, and chat.allow_non_org_members: false are unchanged.
• Pre-commit hooks ran the repo lint and check-types turbo tasks; all 11 packages passed each.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Testing: New and/or updated tests have been added to cover my changes (if applicable).
• Visual Snapshot (UI changes only): If a user would notice this change at a glance (layout, theme tokens, brand elements, empty/error states), I've added or updated a *.visual.tsx snapshot in webview-ui/. See webview-ui/AGENTS.md → "When a UI change needs a snapshot".
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Visual Snapshots

Not applicable — no UI changes; this PR edits only .coderabbit.yaml.

Videos (interaction / animation only)

Not applicable — no interaction or animation changes.

Documentation Updates

• No documentation updates are required. (The change tunes the CodeRabbit review bot's instructions; it does not change user-facing product behavior.)

Additional Notes

Resulting **/* path_instructions entry (as parsed, folded whitespace collapsed):

Act as an adversarial second-opinion reviewer. Verify PR claims against implementation and contracts. Trace changed inputs through normal, boundary, error, cancellation, retry, and default paths and their direct test counterparts. Do not flag defects in files not changed by this PR unless the defect is directly triggered by changed code and cannot be detected in the changed file alone. Seek plausible counterexamples and regressions from removed safeguards. Identify assumptions in changed code that depend on facts outside the diff. First verify repository conventions, tests, and related implementations. When a potential finding depends on external behavior, use web search and prefer official documentation, specifications, or upstream repositories. Report only concrete, actionable conflicts or failure modes, citing the relevant repository location or external source. Prioritize correctness, security, data loss, lifecycle, and test gaps. Do not report generic best practices, unsupported concerns, speculative style comments, or unrelated refactors. When changed code introduces a local implementation of a cross-cutting concern, check whether it bypasses or duplicates an established repository abstraction or nearby convention. Report only a concrete inconsistency with behavioral or maintenance impact, and allow intentional deviations. Treat the linked issue and this PR description as the scope boundary. When a confirmed defect needs work beyond that boundary and this PR does not create the hazard, do not request changes for it. List it once in the walkthrough under follow-up candidates, with one line for the trigger.

Get in Touch

Reachable via this PR's comments.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: Zoo-Code-Org/Zoo-Code/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 61a1bac0-671d-4bbe-9d93-2991d178d498

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

Review status

This PR was opened by an automated account. A human maintainer must verify the change intent, provenance, and validation before merging.

Current step: Required CI passed. Waiting for automated review of the latest commit.

If automated review does not start, a maintainer must restart it.

Review-state labels are managed by this workflow; do not edit them manually.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!