Make create organization popover more compact

[shomix]

Summary

Fixes the create organization popover so it no longer widen to fit long helper text.

Problem

The new organization popover was too wide because the helper text and its icon used a flex layout that expanded to accommodate the content, resulting in a poor UX.

Solution

Constrained the popover width for non-list modes and reworked the helper text markup so the key icon is inline with the text, allowing the text to wrap naturally beneath the icon instead of stretching the container.

Key Changes

• Added w-64 width constraint to OrgSwitcher's popover content when not in "list" mode.
• Replaced the flex-based helper text layout with an inline icon (IconKey) positioned via align-text-top and me-1.5, so wrapped text flows beneath it.
• Added a changeset documenting the compact popover fix for @agent-native/core.

BEFORE

AFTER

---

  

---

To clone this PR locally use the Github CLI with command gh pr checkout 2480

You can tag me at @BuilderIO for anything you want me to fix or change

[builder-io-integration]

Builder reviewed your changes — looks good ✅

Review Details

Code Review Summary

PR #2480 makes the create-organization and invite-member OrgSwitcher popovers compact by applying w-64 only outside list mode, and changes the vault notice to inline icon/text flow so long helper text wraps within the constrained content. The changeset correctly records a patch release for @agent-native/core.

This is a low-risk UI-only change. The approach is appropriately scoped: list-mode sizing remains unchanged, while create/invite modes receive the intended width constraint, and the helper text no longer uses a flex row that can widen the popover. Two independent code-review passes found no clear functional, accessibility, security, or release-metadata issues.

Key Findings

No reportable issues found.

Browser testing

🧪 Browser testing: Attempted full visual verification, but all 13 planned cases were blocked by an infrastructure issue: the Chrome DevTools/MCP browser bridge was unreachable in executor sessions. The dev server itself was running and healthy; no browser evidence was produced.