Icon behaviour

Proves what the package selector does for each combination of logo and iconOnly, including a logo filename that does not exist.

Five cards, one per case. Open the browser console before clicking anything: two of these are meant to log an error there and nothing on the page.

Card	Expected
Icon and label	Logo, then the label. This is the default when iconOnly is absent.
Icon only	Logo alone. The label is still the accessible name and the tooltip.
No logo declared	Label alone. Nothing logged, this is a normal card.
Logo that does not resolve	Label alone, plus a console error naming the file.
Bad logo, icon only	Label alone. iconOnly is ignored when no icon resolved, otherwise the card would be empty and unclickable.

Every card points at the same Docker page, so a click that lands anywhere else means the path handling is wrong rather than the icon handling.

Both console errors name the file: one from the worker, visible with gitbook integrations events list harness-package-selector-staging, and one from the webframe in the browser console. Readers see neither.