feat(plugins): augment_prompt for the follow-up planner + reconcile docs

[OBenner]

Two follow-ups to the Direct-API augment_prompt work in #421 (both merged: #417 tool hooks, #421 augment_prompt).

1. Follow-up planner was uncovered

planner.run_followup_planner builds its own Direct-API session via a separate builder that #421 didn't touch, so plugin prompt contributions (rules-steering-compiler, codebase-intelligence, ...) never reached it. Now it applies the same augmentation to its message.

2. Centralized the helper

Moved the coder-local _augment_direct_api_prompt into plugins.runtime as the public augment_direct_api_prompt; both coder.py and planner.py call it (planner no longer reaches into coder-private state). Same guarded semantics: no-op for claude (already augmented via create_client), degrade-to-base on failure.

3. Docs reconciliation

#417 landed a plugin-development note stating augment_prompt is "Claude SDK only" — #421 made that false. This flips the matrix row to ✅ for Direct-API and Codex (delivered via the agent message) and rewrites the note to describe the system-prompt-vs-message split and the double-apply guard.

Tests

test_direct_api_prompt_augmentation.py (renamed from test_coder_prompt_augmentation.py, repointed at the shared helper): claude not augmented, openai/codex augmented with correct args, failure degrades to base. Regression: 246 runtime + 18 planner + plugin_runtime tests pass; ruff check + format clean.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 54 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: ASSERTIVE

Plan: Pro

Run ID: fe56d1a8-159f-46ae-8323-b8f0e5124215

📥 Commits

Reviewing files that changed from the base of the PR and between d5ac1ee and 751aefa.

📒 Files selected for processing (5)

• apps/backend/agents/coder.py
• apps/backend/agents/planner.py
• apps/backend/plugins/runtime.py
• docs/guides/plugin-development.md
• tests/test_direct_api_prompt_augmentation.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/augment-followup-planner

---

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud