feat: add incident operator handoff agent:clawd

[TargiX]

What changed

• add a compact operator handoff inside the existing incident-detail flow
• derive deterministic Markdown from the loaded incident, provider, affected-job, routing, and simulation state
• include the canonical incident URL and clearly distinguish proposed, simulated, and applied decisions
• keep simulation and clipboard feedback tied to the exact input/content snapshot
• extend the existing canonical navigation contract gate with focused handoff assertions

Why

SignalOps already supports incident investigation and guided replay, but the evaluator loop ended inside the cockpit. This gives an operator a truthful, paste-ready incident → routing decision → handoff artifact without adding storage, ingest, collaboration, telemetry, or another dashboard surface.

Verification

• corepack pnpm@10.24.0 check
• git diff --check
• Chrome/CDP browser proof on http://127.0.0.1:3027/incidents/inc_411#handoff
  • prior full responsive matrix: 1280 / 820 / 390, keyboard focus/activation, reduced motion, no overflow, no console errors
  • post-review delta: simulate → edit returns the handoff to proposed and enables re-simulation
  • post-review delta: delayed clipboard completion after editing shows no stale success
• final independent Codex autoreview: clean, no actionable findings (0.90 confidence)

Collision boundary

No overlap with open PR #12. This PR touches only:

• src/components/incident-detail.tsx
• src/lib/incident-handoff.ts
• scripts/test-home-navigation.mjs

No auth, ingest, storage, API, package, README, or dependency changes.

Ilya merges personally; 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 19, 2026 1:16pm

[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: 25 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: e4d0fe6d-97a1-4a71-89a7-26e8c80338d5

📥 Commits

Reviewing files that changed from the base of the PR and between 1f5b1ed and 062d91b.

📒 Files selected for processing (3)

• scripts/test-home-navigation.mjs
• src/components/incident-detail.tsx
• src/lib/incident-handoff.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch signalops-lab/t_5bb6d9ff-portfolio-lab-signalops-incident-handoff

---

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