[kazemek21]

TL;DR

Delete chat was missing from the context menu of active, agent-created Solo chats. The permission was granted and the item was rendered, but it was clipped by the shared menu's fixed 24rem height cap, behind macOS's hidden overlay scrollbar. This bounds .buzz-menu-popup by the available viewport height only, so every permitted action is visible without scrolling.

Fixes NEXUS-4264

Diagnosis

• Eligibility is correct. A plain member of an agent-created Solo chat gets Archive, Unarchive and Delete together from the owner-agent grant (the agent's verified NIP-OA attestation names the viewer). The relay authorizes 9008 delete the same way (actor_owns_any_owner_agent). Nothing about attestation, confirmation-time validation or relay authorization changes here.
• The menu for that chat has 11 rows (huddle, mark unread, rename, settings, move, share, copy link, convert, leave, archive, delete). They need about 26.4rem, more than the min(24rem, var(--available-height)) cap, so Delete sits just past the fold. In the reported app (text scale 1.3) the popup measured at the 499.2px cap. An owner's channel menu has no Leave row and overflows by only a couple of pixels, which is why Delete still showed there. Rows and the rem cap grow together with text scale, so the clipping does not depend on it.
• Playwright's click() scrolls items into view, so existing journeys could not catch this. DESIGN.md asks that long lists stay scrollable and all actions reachable; the viewport bound keeps the scroll fallback for genuinely short windows.

Change

• src/shared/design-system/styles/components.css: .buzz-menu-popup max-height is now var(--available-height) (still overflow-y: auto). This is a shared design-system recipe, so it affects every menu: they grow up to the available viewport height instead of stopping at 24rem. That matches .buzz-select-popup and .buzz-popover-popup, which already use the uncapped viewport bound, so long lists in selects and popovers are unchanged. A viewport shorter than a menu still scrolls.
• tests/browser/channel-lifecycle.spec.mjs: a new journey opens the Solo chat menu as a plain member whose agent owns the chat, then asserts that Leave, Archive and Delete are fully in the viewport, that the menu has no scroll overflow, and that no lifecycle event is published.

Browser-only justification: the defect is layout (computed height versus the scroll box), which jsdom cannot measure, and Playwright clicks would otherwise mask it. Fail-then-pass on a Blox workstation (chromium and webkit): before the fix the new case failed on the overflow check (Expected: 0, Received: 4); after it, channel-lifecycle, channel-archive-delete-pane and the design-system specs passed (30 tests, both engines), with Biome and design:check clean. The case runs at the default text scale on purpose: at 1.3 the 10-row fixture menu fits under the old cap (overflow 0 on base in both engines), so a scaled run would not catch the regression.

Deferred and related

• Not yet checked in the native macOS app at text scale 1.3; the browser case covers the layout contract.
• Related, non-overlapping: fix(channels): show channel actions as soon as the menu opens #2657 (live lifecycle offers; does not change the menu height) and fix(agents): restrict workflow requests in bb-block only #2518 (owner-attestation verifier; untouched here).

Initiative status: https://g2.sqprod.co/apps/kylez-buzz-improvements-status

— Posted by Claude Code (claude-opus-5-5) on behalf of kylez

🤖 Generated with Claude Code

[dr0uleau]

🤖 approved at 8d44b66 -- CI passes. native macOS at text scale 1.3 remains unverified