security: remove obsolete branch-local repair writer

[seonghobae]

Purpose

Remove the obsolete repair-pr-67.yml self-modifying branch-local repair workflow that still exists on current protected main, while making its absence a durable repository policy contract.

Test-first state

• Exact protected base at branch creation: 7dd950b92de7c84e80be430451a286cf99c6c19d.
• RED commit: 77658ec6d473255c9936768096e73d3bd73db0eb adds src/lib/repositoryWriterWorkflowPolicy.test.ts.
• Protected main still contains .github/workflows/repair-pr-67.yml, which grants contents: write inside a branch-specific repair job and patches a historical feature branch. The RED contract therefore intentionally fails until that obsolete writer is removed.

Intended security boundary

• no repair-pr-<number>.yml branch-local writer workflows;
• no hidden legacy workflow that applies the historical bounded-repair patch or combines contents: write with git push;
• ordinary CI/review/release workflows remain unchanged;
• no replacement write-capable repair workflow is introduced.

Keep Draft until RED is observed, the workflow is removed, the exact current head passes applicable Test/Release/Security Scan/SAST, and live review/ruleset policy is satisfied. No stale evidence from PR #137 transfers.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 3 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 345bf810-3cb2-4e1a-af7f-a4027835b8da

📥 Commits

Reviewing files that changed from the base of the PR and between 7dd950b and c282ad3.

📒 Files selected for processing (2)

• .github/workflows/repair-pr-67.yml
• src/lib/repositoryWriterWorkflowPolicy.test.ts

---

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