feat(sidebar): move Run Inspector under context tree

[Rchari1]

Moves the Run Inspector from the Work Column-only location to the sidebar, stacking under Armonia + Catalog in the amicode container — per user request.

What / why

Current state is ADR 0006: inspector lives as a Work Column SolidJS tab fed via inspector_bridge. Great for session binding, but it competes for editor width and isn't visible when the chat is the focus. Request was to have the inspector under the context tree (sidebar, always visible).

Implementation

• package.json: register amicode.runInspector as a webview under amicode container (same container as armonia/catalog) so it renders as a collapsible section below them at 320px.
• run_inspector_view.ts (new, 170 LOC): WebviewViewProvider that reuses the existing registerInspectorPoster fan-out — no new RunsManager pipeline. run:iteration/run:pulse/run:completion stream to both sidebar + Work Column, so live solves stay in sync. Renders a lightweight sparkline + iter/objective/fidelity + status; 'Open in Work Column' jumps to the detailed plot.
• extension.ts: register the provider on activate.

Trade-offs / why this is cheap now

• Reuses the bridge, so no duplication of pulse buffering or timing logic.
• Work Column tab is kept for full-fidelity plots (many drives / long pulses need width); sidebar is the summary. We can retire the Work Column tab later if desired — flipping that is a one-line removal.

Preview

• This PR's widget sidebar-run-inspector-preview (hero) is live in your Amicode dashboard — Pin it to see the stacked Armonia / Catalog / Run Inspector mock with sparkline.
• Real VS Code preview: pnpm --filter @amicode/amico-run build && pnpm --filter amicode build && vsce package → install .vsix and reload — the Run Inspector appears under Catalog in the Amicode sidebar. Also works via pnpm run watch.

Follow-ups

• Keep vs. remove Work Column tab (flip condition in ADR 0006)?
• Persist collapsed state / add 'pin' for the sidebar inspector?

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 46 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: 0ab9307a-7a00-4c60-8d66-ecbaa27af455

📥 Commits

Reviewing files that changed from the base of the PR and between b712baa and 31e36ee.

📒 Files selected for processing (3)

• packages/extension/package.json
• packages/extension/src/extension.ts
• packages/extension/src/run_inspector_view.ts

---

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

[Rchari1]

Closing — desired location is the in-app session sidebar as third tab (Files Changed | Context | Run Inspector), implemented in harmoniqs/opencode#211. VS Code sidebar view under Armonia/Catalog was the wrong container; keeping the Work Column + in-app sidebar instead.