docs: retire the test-branch PR flow — all submodule PRs target main

[sweetmantech]

Part of recoupable/chat#1850 — the doc-drift fix behind the base-branch correction in that issue's PR matrix.

What

1. Retire the test-branch PR guidance (the reason for this PR). The Git Workflow section still instructed api and chat PRs to target test with a test-sync ritual. That flow was retired — api#750 (merged 2026-07-03) and chat#1843 — and both submodules' own CLAUDE.md files already say PRs target main. The stale root doc caused agents to be briefed with the wrong base on 2026-07-06 (caught by the submodule docs before any PR was opened against test). Both blocks are replaced with a single rule: all submodule PRs target main, and the "(e.g., test vs main)" example under the common rules is corrected to match.

2. Rides along (pre-existing local edit, committed with permission): the "Internal issue workflow" section documenting the recoup-internal-dev-issue-tracker / recoup-internal-dev-ship-issue skills and the all-issues-live-in-recoupable/chat convention.

Done when

• No doc in the mono root instructs targeting test in any repo (grep -n "target.*test" AGENTS.md → no PR-flow hits).
• Root guidance agrees with api/CLAUDE.md and chat/CLAUDE.md.

🤖 Generated with Claude Code

---

Summary by cubic

Retires the test-branch PR flow; all submodule PRs now target main, aligning root guidance with api/CLAUDE.md and chat/CLAUDE.md to avoid wrong base selection.
Adds an “Internal issue workflow” section documenting recoup-internal-dev-issue-tracker and recoup-internal-dev-ship-issue, and clarifies that all issues live in recoupable/chat.

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

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 3 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 62720b7f-651b-41b9-a4e7-f896f34d2025

📥 Commits

Reviewing files that changed from the base of the PR and between 5582c3e and bc041cd.

📒 Files selected for processing (1)

• AGENTS.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/prs-target-main

---

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

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}