fix(ci): resolve prettier violations breaking dev 'checks' workflow

[mabry1985]

Summary

Dev CI's checks workflow has been failing since the main->dev back-merge (commit 170f58c onward) on the "Check formatting" step. Reformats 8 files that carried prettier violations into dev. No semantic changes.

Evidence

• Every dev commit since ~PR fix(ci): issue #3299 — FeatureScheduler silently skips features with contradictory isEpic=true + epicId state #3429 has checks RED. Pre-break commit e006655 (PR feat(a2a): agent card identifies this runtime as 'protomaker' #3375) was green.
• CI log (run 24439007986, step "Check formatting"): Process completed with exit code 1
• Reproduced locally: npx prettier --ignore-path .prettierignore --check flagged exactly these 8 files. --write produces clean tree.
• Only files reformatted:
  • apps/server/src/routes/webhooks/routes/github.ts
  • apps/server/src/services/auto-mode-service.ts
  • apps/server/src/services/auto-mode/execution-service.ts
  • apps/server/tests/unit/services/execution-service.test.ts
  • apps/server/tests/unit/services/feature-scheduler-done-lock.test.ts
  • apps/server/tests/unit/services/lead-engineer-review-merge-processors.test.ts
  • apps/server/tests/unit/services/lead-engineer-review-processor.test.ts
  • libs/platform/tests/subprocess.test.ts

Test plan

• Local prettier --check passes on the 8 fixed files
• CI checks workflow passes on this PR
• Dev merge commit shows checks: SUCCESS

Scope

• Unblocks checks only. Separate failures in test and Build & push dev server image are tracked in board feature feature-1776234779049-zgrzez2p2.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@mabry1985 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 0 minutes and 40 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 0 minutes and 40 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: 6b37a0d0-04c2-4517-8aed-48c99207b8ad

📥 Commits

Reviewing files that changed from the base of the PR and between dd65905 and a78290f.

📒 Files selected for processing (8)

• apps/server/src/routes/webhooks/routes/github.ts
• apps/server/src/services/auto-mode-service.ts
• apps/server/src/services/auto-mode/execution-service.ts
• apps/server/tests/unit/services/execution-service.test.ts
• apps/server/tests/unit/services/feature-scheduler-done-lock.test.ts
• apps/server/tests/unit/services/lead-engineer-review-merge-processors.test.ts
• apps/server/tests/unit/services/lead-engineer-review-processor.test.ts
• libs/platform/tests/subprocess.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/ci-prettier-formatting-backmerge

---

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