fix(pr-review): unbreak reviews — stub must not forward lsp_pilot_variant to the pinned channel

[don-petry]

🔴 Production hotfix — every pr-review has been failing with startup_failure

Since #1034 merged (2026-07-03), every pr-review-trigger run has ended in startup_failure (confirmed across the last 15+ runs on main). No PR is getting reviewed.

Root cause — release-channel skew

#1034 modified the thin ring-0 caller stub (pr-review-trigger.yml) to forward a new lsp_pilot_variant input to pr-review.yml@pr-review/next. But the pinned channel pr-review/next (ded84ce) is behind #1034 and does not declare that input. Passing a with: key the called reusable doesn't declare is an invalid workflow → startup_failure on every review — even with an empty value, and for event-triggered runs.

This is the thin-caller-stub hazard called out in CLAUDE.md / the stub's own header ("this file only changes when the ring-0 channel itself changes"): the stub was changed to forward an input ahead of the channel that defines it.

Fix

Remove the premature lsp_pilot_variant dispatch input + its forwarding from the stub, restoring its with: block byte-for-byte to the pre-#1034 set (18 deletions, one file). Nothing else changes.

pr-review.yml on main keeps its lsp_pilot_variant input + env/gating logic — it's harmless there. The stub forwarding should be re-added only after pr-review/next is advanced (via cut-release.sh --channel) to a commit that declares the input, so the stub and the channel it pins stay in lockstep.

Validation

• pr-review-trigger.yml parses as YAML; no lsp_pilot_variant reference remains in the stub.
• Diff is deletions-only against main.

Follow-up (separate, non-urgent)

Re-enable the pilot A/B on this repo's PRs the right way: advance pr-review/next to include #1034 first, then reintroduce the stub forwarding. Tracked against epic #839 / #844.

🤖 Generated with Claude Code

---

Generated by Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 55 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: ASSERTIVE

Plan: Pro

Run ID: ffaa0fbf-3431-4bbe-9528-caba14015e57

📥 Commits

Reviewing files that changed from the base of the PR and between 4485a5b and f5afd87.

📒 Files selected for processing (2)

• .github/workflows/pr-review-trigger.yml
• tests/dev-lead/integration/test_pr_review_lsp_pilot_plumbing.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/mcp-review-enrichment-6h269j

---

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

[Copilot]

Pull request overview

This PR is a production hotfix to restore pr-review-trigger workflow execution by removing an undeclared reusable-workflow input (lsp_pilot_variant) from the thin caller stub, which was causing startup_failure when calling the pinned pr-review/next channel.

Changes:

• Removes the workflow_dispatch input definition for lsp_pilot_variant from pr-review-trigger.yml.
• Stops forwarding lsp_pilot_variant in the with: block to the pinned reusable pr-review.yml@pr-review/next, avoiding invalid-input startup failures.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[don-petry]

Dev-Lead — fix-bot-comment (no-changes)

Agent reasoning

Issues addressed: 0
Files changed: tests/dev-lead/integration/test_pr_review_lsp_pilot_plumbing.py
Skipped (informational): 0
No actionable issues — Quality Gate passed with zero new issues and zero security hotspots.
```
The PR is in good shape. All quality gates pass with no bugs, vulnerabilities, or code smells detected.