test(review): require the channels subtree separator in the slack-scope guard

[khaliqgant]

User description

Follow-up to #40, which was merged while this one-line review fix was in flight (the push landed 2 minutes after the squash-merge and silently re-created the deleted head branch — cherry-picked here onto fresh main instead).

gemini + codeant both flagged the coverage predicate in the #40 regression test: startsWith('/slack/channels') also accepted sibling subtrees like /slack/channels-private/**. Require the trailing slash so only the real channels subtree passes.

npm test: 20/20.

🤖 Generated with Claude Code

---

Summary by cubic

Require a trailing slash in the Slack channels subtree check in the review test. This excludes siblings like /slack/channels-private/** and avoids false positives in the scope coverage.

^{Written for commit de2ef7f. Summary will update on new commits.}

---

CodeAnt-AI Description

Tighten the Slack scope test so it only accepts the real channels path

What Changed

• The Slack coverage test now requires /slack/channels/ instead of any path starting with /slack/channels
• This prevents sibling paths like /slack/channels-private/** from passing the check

Impact

✅ Fewer false-positive Slack scope checks
✅ Safer coverage for the channels writeback path
✅ Clearer test failures for missing Slack access

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

CodeAnt AI is reviewing your PR.

[coderabbitai]

Warning

Review limit reached

@khaliqgant, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 4 minutes and 33 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: bf9c046d-e332-45c7-ba8b-4ea44d7d1fc5

📥 Commits

Reviewing files that changed from the base of the PR and between e829723 and de2ef7f.

📒 Files selected for processing (1)

• tests/review-agent.test.mjs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch test/slack-scope-guard-tighten

---

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 and usage tips.}

[gemini-code-assist]

Code Review

This pull request updates a test assertion in 'tests/review-agent.test.mjs' to check for a trailing slash in the Slack channels path, ensuring it starts with '/slack/channels/' instead of '/slack/channels'. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}

[codeant-ai]

CodeAnt AI finished reviewing your PR.