ci(library-selection): #205 acceptance + bench workflows + bench/ stub

[zackees]

Wires the gates already shipped (PR #208 acceptance + PR #210 benches) into CI, and stubs the warm-cache benchmark home #205 explicitly calls for.

What ships

• `.github/workflows/acceptance-205.yml` — runs the `#[ignore]`'d Phase 6 gates (`teensylc_acceptance` + `stm32_acceptance`) on manual + nightly + scoped-PR triggers. 45-minute timeout, fail-fast off so a teensy regression doesn't mask an stm32 one.
• `.github/workflows/bench-205.yml` — runs the criterion benches (`scan_throughput` + `resolve_cold`) and uploads HTML reports as 14-day artifacts. Manual + scoped-PR. No CI threshold gates yet (capturing P-02 / P-03 numbers until runner variance is characterized).
• `bench/fastled-examples/` placeholder — README documenting the future warm-cache matrix per feat(library-selection): Rust-native LDF-style transitive header scanner, zccache-backed #205 AC#5 / P-01. Status: empty placeholder, awaits Phase 4 (zccache K/V cache, gated on zackees/zccache#130).
• Closed teensy30/LC: Teensy orchestrator compiles unreferenced framework libraries (FNET, Snooze, RadioHead, mbedtls) — causes .bss / .dmabuffers RAM overflow #204; commented on already-closed stm32: Arduino_Core_STM32 framework libraries (SPI, Wire, ...) not discovered — fatal error: SPI.h: No such file or directory #202 with the resolution path.

Verification

• YAML parses via `pyyaml.safe_load`.
• Workflow path filters and bench names match the real files in `crates/fbuild-{header-scan,library-select}/benches/` and `crates/fbuild-build/tests/`.

Out of scope (still tracked)

• Phase 4 — zccache K/V memoization.
• P-01 / P-04 perf gates — depend on Phase 4.
• CI threshold gates on P-02 / P-03 — wait for runner-variance data.
• Phase 8.b — `framework_libs.rs` cleanup once Phase 4 lands.

Refs: #202 (commented), #204 (closed), #205, zackees/zccache#130

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@zackees has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 13 minutes and 6 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 13 minutes and 6 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 5cc553b4-8965-4355-a7b9-e5cb3e3bdc56

📥 Commits

Reviewing files that changed from the base of the PR and between 0bf4b2f and 23772e8.

📒 Files selected for processing (5)

• .github/workflows/acceptance-205.yml
• .github/workflows/bench-205.yml
• bench/README.md
• bench/fastled-examples/README.md
• docs/INDEX.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/205-phase-7-and-8-finalization

---

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 and usage tips.}