ci: acknowledge composio/action_tool.rs in feature-gate-smoke allowlist

[M3gA-Mind]

Summary

Merged #4995 added a #[cfg(feature = "flows")] #[tokio::test] to src/openhuman/composio/action_tool.rs but did not add that file to the EXPECTED allowlist in the rust-feature-gate-smoke lane's "Guard — new feature-gated test modules must be acknowledged" step (.github/workflows/ci-lite.yml).

As a result the guard fails on every PR branched off post-#4995 main:

::error::Gated-test file set changed. ...
> openhuman/composio/action_tool.rs

This currently blocks otherwise-green PRs #5064, #5066, #5067 (and any future recent-base PR). PRs on an older base (e.g. #4998) are unaffected.

Fix

Add openhuman/composio/action_tool.rs to the EXPECTED allowlist — one line.

The test is properly #[cfg(feature = "flows")]-gated, so it compiles out entirely in the gates-off build and cannot carry a #5022-class ungated-assert regression. Per the guard's own guidance that means an allowlist entry only — no change to the scoped cargo test filter is needed.

Verification

Ran the guard's own EXPECTED vs ACTUAL diff locally with this change applied: they match exactly (gate-contract test coverage allowlist is current). No source/behaviour change — CI-config only.

Related

• Root cause: fix(composio): gate per-action tools on their full contract (#4853) #4995 (48cba1a02)
• Unblocks: fix(embeddings): differentiate custom endpoint verification failures (#5017) #5064, fix(harness-init): show runtime-setup overlay on first run only (Closes #5047) #5066, fix(inference): probe /v1/models for OpenAI-compatible local runtimes (Closes #5053) #5067
• Guard rationale: Gates-off build red on main: 2 ungated voice asserts + smoke lane runs no tests #5022 / CI: run the full gates-off test suite (blocked on task_local stack overflow) #5021

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 9 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: CHILL

Plan: Pro

Run ID: eac958fe-71f7-46ea-acc1-01e5294e5bcd

📥 Commits

Reviewing files that changed from the base of the PR and between d13a559 and fb728ee.

📒 Files selected for processing (1)

• .github/workflows/ci-lite.yml

---

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