fix(flare-workflow): honor RetryPolicy for StepMode::Loop iterations

[getappz]

Summary

• execute_loop (the code path StepMode::Loop steps like sdd_loop actually dispatch through) never consulted the step's RetryPolicy, hard-failing the whole loop on the first error even when a policy — including the crate's own default (max_attempts: 3) — configured multiple attempts.
• Retries the current iteration in place (not advancing iter) up to the policy's max_attempts with backoff, reusing the same in-memory context across attempts so a partially-completed iteration isn't redone.
• Scope: crates/flare-workflow/src/loops.rs only — sdd_loop is the only StepMode::Loop step in the codebase, confirmed via full-repo search.

Test plan

• cargo test -p flare-workflow — all 43 tests pass, including 2 new ones (loop_iteration_retries_transient_failure_then_succeeds, loop_iteration_fails_after_exhausting_retries) and the existing crash-recovery loop test (no regression to loop durability)
• cargo clippy -p flare-workflow --all-targets -- -A unsafe_code -A clippy::pedantic — clean

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

Limit details: You’ve used all 1 included review currently available under your plan. You completed 72 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: CHILL

Plan: Pro

Run ID: bebd05a2-1f6b-4db2-b357-eab99a847619

📥 Commits

Reviewing files that changed from the base of the PR and between ad0244d and f5c97d4.

📒 Files selected for processing (2)

• crates/flare-workflow/src/loops.rs
• crates/flare-workflow/tests/semantics_test.rs

---

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