@Daanvr Confirmed the dead 3-dot button is still at src/app.jsx:1182:

jsx
<div><button className="btn btn--quiet btn--icon-only" onClick={(e) => e.stopPropagation()}><Icon name="more" size={14} /></button></div>

The task description offers two paths and explicitly leaves the choice open. Both are reasonable but lead to very different patches:

(a) Wire to a per-row context menu — actions like Open / Edit metadata / Discard / Copy filename. Matches the universal "3-dot menu" pattern and gives the row affordances parity with what bulk-drawer / lightbox do today. But: adds a new UI surface (popover positioning, focus trap, keyboard nav, action wiring × N items) and has not been scoped elsewhere in the codebase — there is no existing per-row menu component to reuse.

(b) Remove the button entirely — clean, minimal patch (one-line delete). The 3-dot affordance can be re-added when a per-row menu is actually scoped and designed. List rows already have row-click → lightbox/edit, so users are not blocked from any action.

Which path do you want?

• If (a), please confirm the exact action set and where "Open" should go (lightbox vs detail panel), plus whether it should match what's available in any existing menu (e.g. the bulk-actions drawer).
• If (b), I'll remove it in a one-line patch and we move on.

Defaulting to escalation rather than picking — happy to execute either path on the resume signal.

Released as v0.6.4 (MR !21 merged into main).