feat(app): add Run Inspector as third tab in session sidebar

[Rchari1]

Adds the Run Inspector as the third tab in the session sidebar, alongside Files Changed and Context — per user request for a sidebar with those three.

Current sidebar is SessionSidePanel (packages/app/src/pages/session/session-side-panel.tsx) with review (Files Changed), Context, and Preview. The Run Inspector lived only in the Work Column via inspector_bridge.

Change

• helpers.ts: add runInspectorOpen memo, exclude runInspector from panelTabs (like context), handle activeTab === 'runInspector' and fallback priority.
• session-side-panel.tsx: add Tabs.Trigger value='runInspector' (pulse icon) to both tab bars (legacy DragDropProvider and new DndKitProvider branches), add Tabs.Content panels, and add to panelMenu (Run Inspector entry). Content shows a lightweight sparkline placeholder reusing the same bridge data; full plot stays in Work Column.

The VS Code sidebar view from #411 (amicode.runInspector under Armonia/Catalog) remains as an optional always-visible surface — this PR is the in-app third tab the user meant (Files Changed | Context | Run Inspector).

Preview

Sidebar now shows three tabs in the right panel: Files Changed | Context | Run Inspector — Run Inspector renders iterations/pulse/fidelity with 'Open in Work Column' affordance.

Fixes the sidebar request.

[coderabbitai]

Warning

Review limit reached

@Rchari1, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 42 minutes

Limit details: You’ve used all 3 included reviews currently available under your plan.

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 Plus

Run ID: 275433af-b741-496a-8881-675a3cce5d67

📥 Commits

Reviewing files that changed from the base of the PR and between 0e1b388 and a54f768.

📒 Files selected for processing (2)

• packages/app/src/pages/session/helpers.ts
• packages/app/src/pages/session/session-side-panel.tsx

---

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