@evandu/super-pi 0.1.30 → 0.1.32

package/dist/server/terminal.js

@@ -164,8 +164,7 @@ const MAX_CHUNK_BYTES = 64 * 1024;
 /** Hard per-session backlog. Beyond this the session is considered runaway and is killed. */
 const MAX_BACKLOG_BYTES = 4 * 1024 * 1024;
 /**
- * Reads the opt-in flag. Anything other than an explicit truthy string leaves the terminal OFF, so a
- * typo in a deployment config fails closed rather than silently exposing a shell.
+ * Reads the opt-in flag. Anything other than an explicit truthy string leaves the terminal OFF.
  */
 export function isTerminalEnabled(env = process.env) {
     const raw = env.SUPER_PI_TERMINAL?.trim().toLowerCase();
@@ -174,7 +173,7 @@ export function isTerminalEnabled(env = process.env) {
 /** The sentence a browser shows when the terminal is missing. Says WHICH of the three gates closed. */
 export function terminalDisabledReason(env = process.env) {
     if (!isTerminalEnabled(env))
-        return "终端未启用。设置 SUPER_PI_TERMINAL=1 后重启 Super Pi 即可使用。";
+        return "终端未启用。设置 SUPER_PI_TERMINAL=1 后重启即可使用。";
     if (ptyLoadFailure)
         return `node-pty 未能加载（${ptyLoadFailure}）。请重新安装依赖，或确认 node-pty 版本不低于 ${MINIMUM_PTY_VERSION}。`;
     return "";

package/dist/server/tool-calls.d.ts

@@ -62,6 +62,27 @@ export declare function extractToolResultText(result: unknown): ToolResultSummar
  * shape can be regression-tested at all.
  */
 export declare function describeToolCall(name: string, args: unknown): string | undefined;
+/**
+ * THE SAME LINE, READ OUT OF A CALL THAT IS STILL BEING WRITTEN.
+ *
+ * The block for a call appears the instant the model starts writing it, and for an `edit` that is several
+ * seconds before the arguments are complete. Showing 「工具 · 正在生成参数…」 through all of it says the
+ * reader nothing they can act on - not WHICH tool, and not what it is aimed at, which are the two things
+ * the finished block is going to say. So the same `describeToolCall` mapping runs against the fragments
+ * that have arrived so far.
+ *
+ * TWO STEPS, because a partial JSON document almost never parses. The fragments are tried whole first -
+ * that is the case where the last one closed the object. Failing that, the FIRST `"key": "value"` pair in
+ * the text is read out on its own, and its value does not have to be CLOSED - a fragment usually stops
+ * mid-string, and a path that has arrived half-written still says more than a placeholder does. A fragment
+ * that has produced neither yet yields `undefined`, and the caller decides what an unknown call says
+ * rather than this module inventing a word for it.
+ *
+ * The pair is read with a pattern rather than by parsing a repaired document: repairing JSON is a parser's
+ * job, and a half-repaired document here would risk naming the wrong file - the one thing this line must
+ * never do.
+ */
+export declare function describeToolCallInProgress(name: string, argumentsSoFar: string): string | undefined;
 /**
  * Every parameter of one call, as a bounded list of `key`/`value` pairs a block can show when expanded.
  *

package/dist/server/tool-calls.js

@@ -152,6 +152,46 @@ export function describeToolCall(name, args) {
     }
     return undefined;
 }
+/**
+ * THE SAME LINE, READ OUT OF A CALL THAT IS STILL BEING WRITTEN.
+ *
+ * The block for a call appears the instant the model starts writing it, and for an `edit` that is several
+ * seconds before the arguments are complete. Showing 「工具 · 正在生成参数…」 through all of it says the
+ * reader nothing they can act on - not WHICH tool, and not what it is aimed at, which are the two things
+ * the finished block is going to say. So the same `describeToolCall` mapping runs against the fragments
+ * that have arrived so far.
+ *
+ * TWO STEPS, because a partial JSON document almost never parses. The fragments are tried whole first -
+ * that is the case where the last one closed the object. Failing that, the FIRST `"key": "value"` pair in
+ * the text is read out on its own, and its value does not have to be CLOSED - a fragment usually stops
+ * mid-string, and a path that has arrived half-written still says more than a placeholder does. A fragment
+ * that has produced neither yet yields `undefined`, and the caller decides what an unknown call says
+ * rather than this module inventing a word for it.
+ *
+ * The pair is read with a pattern rather than by parsing a repaired document: repairing JSON is a parser's
+ * job, and a half-repaired document here would risk naming the wrong file - the one thing this line must
+ * never do.
+ */
+export function describeToolCallInProgress(name, argumentsSoFar) {
+    const text = argumentsSoFar.trim();
+    if (!text)
+        return undefined;
+    try {
+        const parsed = JSON.parse(text);
+        const described = describeToolCall(name, parsed);
+        if (described)
+            return described;
+    }
+    catch { /* the document is still being written, which is the normal case here */ }
+    const pair = /"([A-Za-z_][A-Za-z0-9_-]*)"\s*:\s*"((?:[^"\\]|\\.)*)/.exec(text);
+    if (!pair)
+        return undefined;
+    // The closing quote is OPTIONAL in the pattern because a fragment almost always stops mid-string, and a
+    // path that has arrived half-written is still worth more than the placeholder word. What is captured is
+    // unescaped because an escaped quote is part of the VALUE, not the end of it - without this, a file
+    // named with a quote in it would be displayed with a backslash the reader never typed.
+    return describeToolCall(name, { [pair[1]]: pair[2].replace(/\\(["\\])/g, "$1") });
+}
 /**
  * How one non-string argument value is NAMED without being read.
  *

package/dist/server/types.d.ts

@@ -131,6 +131,10 @@ export type ToolCallBlock = {
      * distinction that matters when a reader copies it.
      */
     live?: string;
+    /** The model is still GENERATING this call's arguments. Nothing has reached the host yet, so this is
+     * the only thing on screen during a long parameter stream - an 'edit' block carries a whole file's
+     * replacement text, and without this the screen is blank until the last token arrives. */
+    preparing?: boolean;
     at?: number;
 };
 /**
@@ -164,7 +168,21 @@ export type ToolCallNotice = {
     durationMs?: number;
     result?: ToolResultSummary;
     live?: string;
+    preparing?: boolean;
 };
+/** WHAT THE RUNTIME HANDS A CALLER WHEN THE MODEL STARTS, OR CONTINUES, BUILDING A TOOL CALL. *
+ *
+ * `detail` is the line naming what the call is aimed at - the file for a `read`, the command for a `bash`
+ * - read out of the arguments as far as they have arrived. It is `undefined` when nothing identifying has
+ * been written yet, which is a different fact from an empty one: the caller has a placeholder word for the
+ * second case and must not invent one for the first.
+ */
+export interface ToolCallPreparing {
+    contentIndex: number;
+    name: string;
+    delta?: string;
+    detail?: string;
+}
 /**
  * `archivedAt` is the whole archive mechanism: a state MARKER, not a move. The conversation object never
  * changes workspace or position, so archiving and restoring are a stamp and a clear of one optional field.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@evandu/super-pi",
-  "version": "0.1.30",
+  "version": "0.1.32",
   "description": "Web control plane and companion for Pi",
   "license": "MIT",
   "type": "module",
@@ -96,7 +96,8 @@
     "scripts/queue-dock.test.mjs",
     "scripts/md-render-browser.test.mjs",
     "scripts/right-sidebar-browser.test.mjs",
-    "scripts/sidebar-tools-browser.test.mjs", "scripts/session-context-menu-browser.test.mjs",
+    "scripts/sidebar-tools-browser.test.mjs",
+    "scripts/session-context-menu-browser.test.mjs",
     "scripts/tool-call-blocks-browser.test.mjs",
     "scripts/files-tab-browser.test.mjs",
     "scripts/msg-tabs-browser.test.mjs",