Add relay-fleet review redispatch loop

[sungjunlee]

Part of #479. Completes Phase 2 Sub-PR B.

Summary

• extend relay-fleet --review from a single review pass into the review/redispatch loop
• redispatch children in changes_requested with dispatch.js --manifest <child-manifest> and re-enter review until ready_to_merge or escalated
• extend --resume to re-enter review orchestration and skip still-running child review/redispatch subprocesses via runtime PID guards
• keep reviewing fleet state stable during resume and document the Phase 2 loop behavior

Validation

• node --test tests/relay-fleet/scripts/*.test.js
• node --test tests/relay-dispatch/scripts/*.test.js
• node --test tests/skills-lint/scripts/*.test.js
• git diff --check

Broader suite note

• Attempted node --test tests/relay-review/scripts/*.test.js: 388/390 passed. Two failures are outside this PR's touched files: advisory-review-schema.test.js ambiguous prose/fenced-output assertion and review-runner.test.js PR body snapshot timeout (spawnSync gh ETIMEDOUT).

[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, add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

Warning

Review limit reached

@sungjunlee, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 18 minutes and 26 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

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.

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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9f0cfadf-1545-410f-834b-7fe439309c2c

📥 Commits

Reviewing files that changed from the base of the PR and between df9ea59 and 7130ee9.

📒 Files selected for processing (4)

• skills/relay-fleet/SKILL.md
• skills/relay-fleet/references/design.md
• skills/relay-fleet/scripts/relay-fleet.js
• tests/relay-fleet/scripts/relay-fleet.test.js

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/fleet-review-redispatch-loop

---

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 and usage tips.}

[sungjunlee]

Local review LGTM.

Reviewed head 7130ee9 after CI. I also fixed two self-review findings before merge:

• --resume now preserves existing pre-manifest dispatch failures when it re-enters review orchestration.
• non-zero child review/redispatch exits remain fleet failures even if the manifest advanced.

Validation:

• node --test tests/relay-fleet/scripts/*.test.js
• node --test tests/relay-dispatch/scripts/*.test.js
• node --test tests/skills-lint/scripts/*.test.js
• git diff --check

GitHub Actions test: passing. Codex/CodeRabbit review bodies were unavailable due usage/rate limits, with status context green.