fix(operations): restack workflow registry identity guards on current main

[seonghobae]

Purpose

Restack only PR #267's workflow-registry repository/duplicate/identity hardening onto the current protected-main lineage without transferring predecessor CI, review, scanner, coverage, model, release, or operational authority.

Exact construction

• protected main immediately before construction: 1f4964fb3102cc1b0a9bcf19acae461904ecc672;
• predecessor fix(operations): bind workflow registry evidence identities #267 exact head at the final pre-write refetch: 123a478fb138042c0a46e47b5d1edf3819278161;
• successor exact head: 640e7d2bcb14136acd0df55b66a9eac85c382337;
• ancestry: exactly 1 commit ahead / 0 behind protected main, merge base exactly protected main;
• net scope: exactly five paths: scripts/workflow-registry-audit.mjs, test/workflow-registry-audit.test.ts, test/workflow-registry-collector-repository-binding.test.ts, test/workflow-registry-duplicate-records.test.ts, and test/workflow-registry-repository-binding.test.ts.

Before transplant, both pre-existing modified paths were byte-identical between #267's current merge base 10f7874f309cb120bc57b8c0cb637d1292650fe0 and protected main, so the successor does not overwrite intervening protected-main bytes. The three added test files and the two modified blobs are the exact #267 head blobs.

Security / reliability contract

The collector/classifier fails closed on wrong repository identity, repeated registry records, workflow-ID reuse across conflicting paths, and workflow-path reuse across conflicting IDs. It remains read-only evidence processing; it does not disable workflows, mutate the Actions registry, write branches, satisfy formal review, or confer merge/release/deployment authority.

Evidence boundary

Keep Draft until the unchanged exact head receives fresh terminal-success application ci, reviewer-ci, and protected-base-eligible central Security Scan, with exact 100% owned production statement/branch/function/line coverage and zero valid unresolved findings. Pending, queued, skipped, absent, neutral, failed, cancelled, stale, predecessor, status-only, model-only, or rate-limited evidence is non-passing.

Current observable live governance requires the central Security Scan workflow from .github/workflows/security-scan.yml@refs/heads/main; it does not currently require an independent formal approval. No synthetic approval requirement is introduced. Immediately before Ready or merge, re-resolve protected main, exact head/base/ancestry, reviews/threads, checks/workflow checkout SHAs, live rulesets, exact central scanner revision/triggers/base filters/thresholds, releases, and writer state.

Supersedes #267 only after fresh exact-head verification and protected integration. Related: #226.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 112 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: 351b7151-352f-481b-8b61-65efa9d81e43

📥 Commits

Reviewing files that changed from the base of the PR and between 1f4964f and 640e7d2.

📒 Files selected for processing (5)

• scripts/workflow-registry-audit.mjs
• test/workflow-registry-audit.test.ts
• test/workflow-registry-collector-repository-binding.test.ts
• test/workflow-registry-duplicate-records.test.ts
• test/workflow-registry-repository-binding.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.}