@jini-ai/chat 0.6.2 → 0.6.3

package/CHANGELOG.md

@@ -1,3 +1,9 @@
+## 0.6.3 — 2026-10-14
+
+- A failed MCP bridge ends the run once with its own message (e350056c): durable recovery no longer retries `MCP_BRIDGE_UNAVAILABLE` runs until the budget runs out and then shows the generic "could not continue" notice; the run is finalized with the bridge failure's exact text.
+- The composer accepts file drops while a run streams (7c3d57a7), matching the attach button and paste; the drop gate (`isChatPaneFileDropEnabled` in `rules.ts`) blocks only on a missing uploader, a disabled/agent-less pane, or an upload in progress.
+- Rides along: a regression test for the lone composer send button (3516cc04).
+
 ## 0.6.2 — 2026-10-13
 
 - A lone composer send button stays at the footer's end (b1d7a7b7): a host with no attach or accessory controls (a public visitor chat) left the send group as the footer's only child, so `space-between` put it at the bottom-left; `margin-left: auto` on a first-child send group keeps it on the right, as in the admin composer.

package/dist/react/features/chat-pane/components/ChatPane.js

@@ -7,7 +7,7 @@ import { appendComposerDiscovery } from '../../../components/composer-discovery.
 import { MessageList } from '../../../components/MessageList.js';
 import { useT } from '../../../hooks/context.js';
 import { definedProps } from '../../../util/defined-props.js';
-import { describeTypedAnswerNotice, isChatPaneApiModeConfigured } from '../rules.js';
+import { describeTypedAnswerNotice, isChatPaneApiModeConfigured, isChatPaneFileDropEnabled } from '../rules.js';
 import { useChatPane } from '../hooks/useChatPane.hooks.js';
 import { useChatPaneAgentControl } from '../hooks/useChatPaneAgentControl.hooks.js';
 import { useChatPaneComposerPlaceholder } from '../hooks/useChatPaneComposerPlaceholder.hooks.js';
@@ -258,11 +258,12 @@ export function ChatPane({ transport, agents: injectedAgents = EMPTY_AGENTS, run
     // the provider directly over HTTP and never touches the CLI inventory.
     const unavailable = pane.selectedAgent === undefined && !apiModeConfigured;
     const fileDrop = useChatPaneFileDrop({
-        enabled: surface.uploadAttachments !== undefined
-            && !disabled
-            && !unavailable
-            && !pane.conversation.isStreaming
-            && !pane.isUploadingAttachments,
+        enabled: isChatPaneFileDropEnabled({
+            canUpload: surface.uploadAttachments !== undefined,
+            disabled,
+            unavailable,
+            uploading: pane.isUploadingAttachments,
+        }),
         onFiles: pane.addAttachments,
     });
     // `composerSlots`'s type excludes both `leadingAccessories` and `footerAccessories` (see

package/dist/react/features/chat-pane/rules.d.ts

@@ -48,6 +48,20 @@ export declare function isChatPaneApiModeConfigured({ executionMode, apiModeAvai
     readonly apiModeAvailable: boolean;
     readonly byokRuntime: ByokRuntimeSummary | undefined;
 }): boolean;
+/**
+ * Whether the composer's drop target accepts dropped files right now. A running run is NOT a
+ * reason to refuse: files staged mid-run sit in the composer and go out with the next message
+ * (`send()` queues that turn with its attachments; the queue flush waits for uploads too), the same
+ * as the attach button and paste, which were never gated on the run. Only a missing uploader, a
+ * disabled or agent-less pane, or an upload already in progress (the attach button's own gate)
+ * blocks a drop.
+ */
+export declare function isChatPaneFileDropEnabled({ canUpload, disabled, unavailable, uploading, }: {
+    readonly canUpload: boolean;
+    readonly disabled: boolean;
+    readonly unavailable: boolean;
+    readonly uploading: boolean;
+}): boolean;
 /**
  * The single source of truth for "may this pane send right now?", shared by the composer-driven
  * `send()` and every agent-driven caller so the two can never enforce different rules.

package/dist/react/features/chat-pane/rules.js

@@ -54,6 +54,17 @@ export function resolveChatPaneSelection({ agents, requested }) {
 export function isChatPaneApiModeConfigured({ executionMode, apiModeAvailable, byokRuntime, }) {
     return executionMode === 'api' && apiModeAvailable && Boolean(byokRuntime?.model?.trim());
 }
+/**
+ * Whether the composer's drop target accepts dropped files right now. A running run is NOT a
+ * reason to refuse: files staged mid-run sit in the composer and go out with the next message
+ * (`send()` queues that turn with its attachments; the queue flush waits for uploads too), the same
+ * as the attach button and paste, which were never gated on the run. Only a missing uploader, a
+ * disabled or agent-less pane, or an upload already in progress (the attach button's own gate)
+ * blocks a drop.
+ */
+export function isChatPaneFileDropEnabled({ canUpload, disabled, unavailable, uploading, }) {
+    return canUpload && !disabled && !unavailable && !uploading;
+}
 /**
  * The single source of truth for "may this pane send right now?", shared by the composer-driven
  * `send()` and every agent-driven caller so the two can never enforce different rules.

package/dist/server/durable-runs/recover.js

@@ -3,6 +3,9 @@ import { classifyAgentServiceFailure } from "@jini-ai/agent-runtime";
 import { continuationRequest } from "../../core/durable-runs/continuation.js";
 import { RECOVERY_LIMIT, RECOVERY_WINDOW_MS, RUN_STALENESS_MS, SAVED_WORK_NOTICE, EXHAUSTED_NOTICE } from "../../core/durable-runs/policies.js";
 export { RECOVERY_LIMIT, RECOVERY_WINDOW_MS, RUN_STALENESS_MS, SAVED_WORK_NOTICE, EXHAUSTED_NOTICE } from "../../core/durable-runs/policies.js";
+// translateRunFrame saves a run error frame as a status label holding only its message: the
+// daemon's MCP_BRIDGE_UNAVAILABLE code is dropped, so the bridge failure is matched by its text.
+const MCP_BRIDGE_FAILURE = /The assistant's tools did not load \(MCP bridge "jini" status: [^\r\n]*/;
 /** Retryability is independent of session resumability. Inspect executor diagnostics, never
  * answer text or tool results: those can quote unrelated failures from completed work. Old
  * attempt diagnostics remain visible but cannot decide the fate of their continuation. */
@@ -23,6 +26,10 @@ function attemptDiagnostics({ run }, _optional = {}) {
 }
 function attemptFailure(run) {
     const diagnostics = attemptDiagnostics({ run }, {});
+    // MCP_BRIDGE_UNAVAILABLE needs bridge repair; another attempt repeats the same failure.
+    // Classify it before interpreting the bridge's stderr as an agent auth/watchdog failure.
+    if (MCP_BRIDGE_FAILURE.test(diagnostics))
+        return "permanent";
     if (/inactivity[_ -]?(timeout|watchdog)|watchdog.*(kill|stop)/i.test(diagnostics))
         return "inactivity-watchdog";
     const service = classifyAgentServiceFailure({ text: diagnostics });
@@ -118,8 +125,9 @@ export function createDurableRecovery(ports, _optional = {}) {
         const failure = attemptFailure(run);
         if (failure === "auth-failure" || failure === "inactivity-watchdog")
             return finalize(run, failure === "auth-failure" ? "Not logged in. Saved work is above." : "Stopped. Saved work is above.", true);
+        // A bridge failure shows its own reason (and stderr): the generic notice hides what needs repair.
         if (failure === "permanent")
-            return finalize(run, EXHAUSTED_NOTICE);
+            return finalize(run, attemptDiagnostics({ run }, {}).match(MCP_BRIDGE_FAILURE)?.[0] ?? EXHAUSTED_NOTICE);
         return resolveMissing(run, probe, trigger);
     }
     async function resolveMissing(run, probe, trigger) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jini-ai/chat",
-  "version": "0.6.2",
+  "version": "0.6.3",
   "description": "Jini's chat/artifact frontend, consolidated into one package with two subpaths: framework-free chat vocabulary and pure parsers in `/core`, headless hooks + presentational components + slots in `/react`. Import only the layer you need.",
   "license": "Apache-2.0",
   "repository": {
@@ -196,7 +196,7 @@
     "registry": "https://registry.npmjs.org"
   },
   "dependencies": {
-    "@jini-ai/core": "^0.4.5"
+    "@jini-ai/core": "^0.4.6"
   },
   "peerDependencies": {
     "react": "^18.3.0 || ^19.0.0",
@@ -302,13 +302,13 @@
     "@electric-sql/pglite": "0.5.8",
     "pg": "8.23.0",
     "@ag-ui/core": "0.0.58",
+    "@jini-ai/agent-runtime": "0.4.11",
+    "@jini-ai/ui": "^0.5.3",
     "@jini-ai/agentic": "^0.4.4",
+    "@jini-ai/protocol": "^0.4.4",
     "@jini-ai/db": "0.3.4",
-    "@jini-ai/agent-runtime": "0.4.9",
-    "@jini-ai/core": "^0.4.5",
     "@jini-ai/diagnostics": "^0.5.2",
-    "@jini-ai/protocol": "^0.4.4",
-    "@jini-ai/ui": "^0.5.2"
+    "@jini-ai/core": "^0.4.6"
   },
   "typesVersions": {
     "*": {