feat: connections registry with logos + custom connections (#327)

[Rchari1]

Implements #327

Connections Registry: Formalized Panel with Logos + Custom Connections

• Expand built-in catalog to 5 (Harmoniqs Cloud, Pasqal Cloud, Slack, GitHub, Linear) with inline SVG icons
• Introduce ConnectionRegistry pattern (BUILT_IN_CATALOG + custom-connections.json at 0600 atomic)
• Only configured connections visible in panel; Add picker surfaces unconfigured built-ins + custom entry
• Custom connections: name+token+optional URL, optimistic connected, Remove deletes
• Built-in Disconnect hides card (reappears in Add picker)
• Validators: Slack auth.test, GitHub /user, Linear GraphQL per spec
• Backward-compatible wire shape (icon optional), new routes /catalog, /add-custom, /remove (loopback-guarded)
• UI: ConnectionIcon (18px + 6px badge), ConnectionPicker, filtered tab with empty state

Vendor opencode bump to 52351dae (fork branch connections-registry).

Closes #327

Summary by CodeRabbit

• Chores
  • Updated the extension’s bundled release reference to the latest maintenance revision.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 33 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 Plus

Run ID: 34097b6d-3d84-4c77-9900-3ee178e8d000

📥 Commits

Reviewing files that changed from the base of the PR and between 87f6095 and 5379441.

📒 Files selected for processing (1)

• packages/extension/opencode.lock.json

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4af0ccdb-fc03-4fa6-9fbf-6230f60d6e5d

📥 Commits

Reviewing files that changed from the base of the PR and between 84440c9 and 87f6095.

📒 Files selected for processing (1)

• packages/extension/opencode.lock.json

🚧 Files skipped from review as they are similar to previous changes (1)

• packages/extension/opencode.lock.json

---

📝 Walkthrough

Walkthrough

The extension lockfile now references OpenCode tag v1.18.10-amicode.7 and commit b01e3329cc7beffc8455b3ed3993ed21cbefa4bb.

Changes

OpenCode lockfile update

Layer / File(s)	Summary
Update OpenCode reference packages/extension/opencode.lock.json	The lockfile updates the OpenCode tag and associated commit hash.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Mergeability Score: ⚪ Minimal · up to 87f60

The current head contains only a localized dependency lockfile update, and no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title claims a connections registry with logos and custom connections, but the changes only update the opencode lockfile.	Change the title to describe the opencode dependency bump, or include the implementation changes described by the title.
Linked Issues check	⚠️ Warning	The changes only update opencode.lock.json and do not implement the registry, built-ins, custom connections, routes, validators, or UI requirements in [#327].	Include the implementation changes required by [#327], or link this dependency-only change to an issue that covers the opencode version bump.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Out of Scope Changes check	✅ Passed	The lockfile update supports the stated opencode version bump and does not show unrelated code changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/connections-registry-327

---

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