refactor(pipeline): resolve clippy::pedantic cast-precision lints in base.rs

[nh13]

Resolves the pre-existing clippy::pedantic cast-precision warnings in src/lib/unified_pipeline/base.rs. These live entirely in the #[cfg(feature = "memory-debug")] reporting path, so they only surface under a full cargo clippy --all-features --all-targets run and never tripped the ci-lint gate (which enables compare,simulate,profile-adjacency, not memory-debug). All are lint-only display conversions; no computed value changed.

• PipelineStats::get_memory_breakdown — 25 u64 as f64 byte→GB/MB conversions (clippy::cast_precision_loss): kept the casts and added a single function-scoped #[allow(clippy::cast_precision_loss)] with a rationale. Real RSS/queue sizes are far below f64's 2^52-byte exact-integer limit (4 PiB), so the precision loss is unobservable and the truncated GB/MB figure is exactly what the log line wants.
• log_comprehensive_memory_stats — two f64 as u32 integer-percentage casts (clippy::cast_possible_truncation, clippy::cast_sign_loss): kept the casts and added statement-scoped allows. Both are guarded by system_rss_gb > 0.0 with non-negative numerators (one via saturating subtraction), so truncating toward zero and dropping the never-present sign is the intended display behavior.

No crate- or module-wide blanket allow was added and the ci-lint gate is unchanged. Verified: cargo ci-fmt and cargo ci-lint stay green, cargo clippy --all-features --all-targets -- -W clippy::pedantic shows no remaining cast warnings in base.rs, and the 346 unified_pipeline unit tests (run with memory-debug enabled) pass.

Closes #788

[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: 20 minutes

Limit details: You’ve used all 1 included review currently available under your plan. You completed 139 included PR reviews in the past 7 days; at that activity level, included reviews refill at 1 review per hour.

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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 174fd338-5fcd-4aaa-9801-7c6e34aba81d

📥 Commits

Reviewing files that changed from the base of the PR and between 0c307f8 and bee6941.

📒 Files selected for processing (1)

• src/lib/unified_pipeline/base.rs

Note

Reviews paused

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.23%. Comparing base (0c307f8) to head (bee6941).
⚠️ Report is 8 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #790   +/-   ##
=======================================
  Coverage   94.22%   94.23%           
=======================================
  Files         186      186           
  Lines      111822   111822           
=======================================
+ Hits       105369   105371    +2     
+ Misses       6453     6451    -2     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[nh13]

@coderabbitai pause

[coderabbitai]

✅ Action performed

Reviews paused.

[nh13]

@coderabbitai review

[coderabbitai]

❌ Action failed

Review failed.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[nh13]

@coderabbitai full review

[coderabbitai]

⚠️ Action not completed

Review rate limited.

---

Your included review limit is currently reached under our Fair Usage Limits Policy. Your recent PR review activity is in the 95th percentile or higher among CodeRabbit users, so adaptive limits apply. This review may still proceed through usage-based billing if eligible. Your next included review will be available in 20 minutes.