@volter-ai-dev/supercode-ui 0.1.21 → 0.1.23

package/README.md

@@ -126,11 +126,17 @@ The browser cannot supply locators, credentials, policy, environment variables,
 materialization paths. Session keys and target harnesses must be revalidated by the host.
 `pickContext` is optional and host-owned: the default composer shows one attachment control when
 this callback exists and accepts either typed text context (`detail`) or native image inputs
-(`url`). Images can also be pasted directly. The composer bounds images to four supported browser
-formats at 5 MB each, previews them locally, and keeps both attachment kinds associated with queued
+(`url`). Images can also be pasted or dropped directly, and an image-only turn is sent without
+inventing fallback prompt text. The composer bounds images to four supported browser formats at
+5 MB each, previews them locally, and keeps both attachment kinds associated with queued
 messages, retry, edit, and new-chat recovery. The host still chooses how explicit file selection
 is exposed and must revalidate every returned item.
 
+Transcript images with a browser-safe URL open in a keyboard-accessible, viewport-bounded viewer;
+remote images expose copy-link and open-original actions, while local data images can be downloaded.
+If a host deliberately omits a large historical data URL from its bounded projection, the UI shows
+an honest unavailable-preview attachment instead of a broken thumbnail or a deceptive action.
+
 An embedding product such as Vibewaiting should therefore be small: Lucarne owns its iframe and
 launcher lifecycle, Supercode owns this UI and the controller semantics, and Vibewaiting only
 bridges state/intents plus host-specific theme and persistence policy.

package/components.d.ts

@@ -5,7 +5,9 @@ export {
   ContinuationBar,
   Conversation,
   HarnessLogo,
+  ImageViewer,
   LoadingStatus,
+  MessageImages,
   RequestCard,
   SessionDetails,
   SessionList,