docs: document main merge protections

[avery-salhotra]

What changed

• Enable CodeRabbit's request-changes workflow through .coderabbit.yaml.
• Document the active main protections: verify, verified commit signatures, resolved review conversations, one fresh non-author approval, stale-approval dismissal, and administrator enforcement.
• Configure the live GitHub branch protection to match that policy.

Why

Every pull request targeting main must receive CodeRabbit review, and unresolved review conversations or unsigned commits must block merging. CodeRabbit's documented request-changes workflow supplies the enforceable review lifecycle: it requests changes for findings and approves after its conversations are resolved and configured pre-merge checks pass.

Validation

• npm run verify
  • Dependabot guard passed
  • 26 tests passed
  • TypeScript check passed
  • production build passed
• GitHub reports every commit in this PR as verified with a valid SSH signature.
• CodeRabbit requested changes, the findings were addressed or resolved with evidence, then CodeRabbit approved the latest head.
• GitHub reports zero unresolved review conversations.
• Required verify and CodeRabbit checks are successful; PR merge state is clean and review decision is approved.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 39 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 Plus

Run ID: 08f727ac-b4f0-4e3b-acfa-fbed823739bf

📥 Commits

Reviewing files that changed from the base of the PR and between 8bbde54 and 0fa3771.

📒 Files selected for processing (2)

• docs/superpowers/plans/2026-07-24-parallel-worktree-execution.md
• readme.md

📝 Walkthrough

Walkthrough

The changes document expanded main branch-protection requirements across two implementation plans and the README, and enable CodeRabbit’s request-changes workflow through .coderabbit.yaml.

Changes

Branch protection documentation

Layer / File(s)	Summary
Merge-gate policy documentation .coderabbit.yaml, docs/superpowers/plans/*.md, readme.md	Configures CodeRabbit’s request-changes workflow and documents required verify checks, verified commit signatures, resolved PR conversations, fresh non-author approval, stale-approval dismissal, administrator enforcement, and manual handling when enforcement is unavailable.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely summarizes the main change: documenting main branch merge protections.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/required-verify-gate

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/superpowers/plans/2026-07-24-ux-portfolio-implementation.md`:
- Around line 2251-2259: Update the GitHub merge-gate paragraph to explicitly
identify author/approver separation and stale-approval dismissal as planned or
manually enforced controls, not currently active branch-protection requirements.
Align the wording with the status documented in parallel-worktree-execution.md
and readme.md while preserving the active checks and truthful permission
limitation.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d1944a1d-0b2a-43af-b9f0-fef042e78198

📥 Commits

Reviewing files that changed from the base of the PR and between c87be16 and de84ba2.

📒 Files selected for processing (3)

• docs/superpowers/plans/2026-07-24-parallel-worktree-execution.md
• docs/superpowers/plans/2026-07-24-ux-portfolio-implementation.md
• readme.md

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@readme.md`:
- Line 46: Update the pull request requirements wording in the README to qualify
CodeRabbit enforcement as applying where supported, and document that the same
review checklist must be completed manually when the status cannot be configured
as a branch-protection requirement.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 0353bb85-d486-4519-b29a-c1397620648b

📥 Commits

Reviewing files that changed from the base of the PR and between de84ba2 and 763fc1e.

📒 Files selected for processing (3)

• docs/superpowers/plans/2026-07-24-parallel-worktree-execution.md
• docs/superpowers/plans/2026-07-24-ux-portfolio-implementation.md
• readme.md

🚧 Files skipped from review as they are similar to previous changes (2)

• docs/superpowers/plans/2026-07-24-parallel-worktree-execution.md
• docs/superpowers/plans/2026-07-24-ux-portfolio-implementation.md

[avery-salhotra]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[avery-salhotra]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/superpowers/plans/2026-07-24-parallel-worktree-execution.md`:
- Around line 177-179: Update the CodeRabbit approval description in the
parallel worktree execution plan to state that approval requires both resolved
review conversations and successful configured pre-merge checks.

In `@readme.md`:
- Around line 45-46: Update the branch-gate approval requirement in the README
so the single fresh approval must come from a reviewer who is not the pull
request author, while preserving the existing stale-approval behavior.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: c3cba665-0133-460a-b01d-ea29495bffb2

📥 Commits

Reviewing files that changed from the base of the PR and between 763fc1e and 8bbde54.

📒 Files selected for processing (4)

• .coderabbit.yaml
• docs/superpowers/plans/2026-07-24-parallel-worktree-execution.md
• docs/superpowers/plans/2026-07-24-ux-portfolio-implementation.md
• readme.md

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/superpowers/plans/2026-07-24-ux-portfolio-implementation.md