fix(deploy): V2_ORACLE_TASKS allowlist for mcp-server + validation findings

[bejranonda]

Summary

Three findings from the live flag-enable validation, fixed/documented:

1. V2_ORACLE_TASKS added to the mcp-server compose allowlist (was web-only) — default stays false for forks
2. KNOWN_ISSUES §0k: brain_ask_oracle is project-context-free, so its OPEN TASKS block stays empty even with the flag — pre-existing tool limitation; the spec's actual §4c surface (webapp Oracle) has both flag and project context. Fix candidate noted, deliberately not a drive-by
3. meeting-miner protocol + KNOWN_ISSUES: for: addressing must use the assignee's Brain account email (operator account is admin@…local, not the external Gmail) — first live addressed-injection test caught this

Live validation already passed on the injection surface: session start in the fixture project carried openActionItems with the correctly-addressed [BLOCKER] item and no leakage of other assignees' items; resolvedActionItemIds retired 2 items at close.

Test plan

• ✅ Live prod validation of addressed injection + resolve (see above)
• ✅ Compose defaults verified false
• ⬜ CI green
• ⬜ Webapp Oracle OPEN TASKS check needs a signed-in human/test-account (operator step)

🤖 Generated with Claude Code

https://claude.ai/code/session_01KfujUMcYWzRkwHmG8RYTDM

[coderabbitai]

Warning

Review limit reached

@bejranonda, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 46 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: a1670b0d-c4a3-4133-ab9f-dd6b30cdb442

📥 Commits

Reviewing files that changed from the base of the PR and between c6fbf36 and 6c6e491.

📒 Files selected for processing (3)

• deploy/docker-compose.yml
• docs/KNOWN_ISSUES.md
• docs/protocols/meeting-miner.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/mcp-oracle-flag-allowlist

---

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.}