refactor: extract replay URL helpers [agent:clawd]

[TargiX]

agent:clawd

Summary

• Extract replay query parsing/syncing out of the large dashboard component into src/lib/replay-url.ts.
• Keep the existing /cockpit?replay=<id>&step=<n> behavior: scenario validation, step clamping, unrelated query params preserved, replay params removed on exit.
• Leave the dashboard focused on orchestration/state instead of URL contract details.

Why now

SignalOps already shipped the shareable replay deep-link in PR #7. This follow-up makes that contract reusable/testable before the next replay/share slice, without touching the big dashboard flow beyond delegating helpers.

Verification

• pnpm typecheck
• pnpm lint
• pnpm build
• ~/.hermes/skills/github/autoreview/scripts/autoreview --mode local → clean, no accepted/actionable findings

Ilya merges manually; no auto-merge.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
signalops	Ready	Preview, Comment	Jul 7, 2026 8:54am

[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: 17 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: a2d60e2d-3b5d-44ba-a56b-569c1fff1090

📥 Commits

Reviewing files that changed from the base of the PR and between eb0e35f and 44c9eab.

📒 Files selected for processing (2)

• src/components/dashboard.tsx
• src/lib/replay-url.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch clawd/signalops-replay-deeplink-tests

---

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