fix(acquisition): restack immutable buyer-evidence toolchain on current main

[seonghobae]

Fresh protected-main test-first successor for #147 / historical #148 on exact base 2b3eee922efaa7ae2f11040b1a82a2ce305b75c6. No predecessor checks, reviews, scanner/model evidence, production KPI evidence, release/deployment evidence, or acquisition evidence transfer.

Current exact test-only RED head a0dc9f5c8797cd55788b32c51e1ad9aa2ce08261 adds only test/acquisition-readiness-scan-toolchain-integrity.test.ts. Protected .github/workflows/acquisition-readiness-scan.yml still uses mutable action tags, broad Node 24, persisted checkout credentials by default, unnecessary dependency installation, no immediate tracked-source identity revalidation before evidence generation, and warning-only retained acquisition artifact publication.

Expected RED: application CI must fail these current-protected-main contracts while unrelated current-main behavior remains intact. After exact RED proof, apply only the bounded acquisition workflow GREEN: immutable reviewed action revisions, checkout credential isolation, exact Node/npm verification, no dependency/lifecycle installation, exact tracked-source/HEAD revalidation before evidence generation, and fail-closed artifact retention. Keep Draft until exact-head application CI, reviewer-ci, protected-base eligible central Security Scan, current review/thread state, and live-base identity are reacquired.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 43 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: 28a12c90-85fd-4245-9136-11ef93619f9c

📥 Commits

Reviewing files that changed from the base of the PR and between 8bb925a and c89e869.

📒 Files selected for processing (2)

• .github/workflows/acquisition-readiness-scan.yml
• test/acquisition-readiness-scan-toolchain-integrity.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.}