sparkecoder 0.1.116 → 0.1.117

package/dist/{schema-CYSKJZ3m.d.ts → schema-ecQSnCMz.d.ts}

@@ -85,7 +85,7 @@ declare const sessions: drizzle_orm_sqlite_core.SQLiteTableWithColumns<{
             tableName: "sessions";
             dataType: "string";
             columnType: "SQLiteText";
-            data: "completed" | "error" | "active" | "waiting";
+            data: "error" | "completed" | "active" | "waiting";
             driverParam: string;
             notNull: true;
             hasDefault: true;
@@ -391,7 +391,7 @@ declare const toolExecutions: drizzle_orm_sqlite_core.SQLiteTableWithColumns<{
             tableName: "tool_executions";
             dataType: "string";
             columnType: "SQLiteText";
-            data: "completed" | "error" | "pending" | "approved" | "rejected";
+            data: "error" | "completed" | "pending" | "approved" | "rejected";
             driverParam: string;
             notNull: true;
             hasDefault: true;
@@ -814,7 +814,7 @@ declare const terminals: drizzle_orm_sqlite_core.SQLiteTableWithColumns<{
             tableName: "terminals";
             dataType: "string";
             columnType: "SQLiteText";
-            data: "running" | "error" | "stopped";
+            data: "error" | "running" | "stopped";
             driverParam: string;
             notNull: true;
             hasDefault: true;

package/dist/{search-CVVfuBPZ.d.ts → search-DOzC4ojH.d.ts}

@@ -16,11 +16,11 @@ interface BashToolOptions {
 declare function createBashTool(options: BashToolOptions): ai.Tool<{
     background: boolean;
     id?: string | undefined;
-    input?: string | undefined;
     command?: string | undefined;
+    input?: string | undefined;
     kill?: boolean | undefined;
     tail?: number | undefined;
-    key?: "Enter" | "Escape" | "Up" | "Down" | "Left" | "Right" | "Tab" | "C-c" | "C-d" | "y" | "n" | undefined;
+    key?: "y" | "Enter" | "Escape" | "Up" | "Down" | "Left" | "Right" | "Tab" | "C-c" | "C-d" | "n" | undefined;
 }, {
     success: boolean;
     id: string;
@@ -66,7 +66,7 @@ declare function createBashTool(options: BashToolOptions): ai.Tool<{
     id: string;
     output: string;
     exitCode: number;
-    status: "running" | "completed" | "error" | "stopped";
+    status: "error" | "completed" | "running" | "stopped";
     message?: undefined;
     error?: undefined;
 } | {
@@ -218,8 +218,8 @@ interface SearchToolOptions {
  * Progress is streamed back to the UI so users can see exploration happening.
  */
 declare function createSearchTool(options: SearchToolOptions): ai.Tool<{
-    query: string;
     context: string;
+    query: string;
 }, {
     success: boolean;
     error: string;

package/dist/server/index.js

@@ -7655,6 +7655,26 @@ When you spawn a **desktop worker**, include a one-liner in the goal asking it t
 
 Default bias: **when in doubt, decompose**. Two workers running in parallel and reporting independently is almost always better UX than one worker doing things sequentially.
 
+### How to TALK to the user (versus how you reason internally)
+
+All of the rules below \u2014 decomposition, parallel spawning, "don't invent commands", load-the-skill, etc. \u2014 are **your internal operating procedure**. They are how you decide what to do. They are NOT something to recite back to the user.
+
+When replying to the user (Slack, web, or any channel), be a normal helpful assistant:
+
+- Tell them *what you're doing*, not *how you're doing it internally*.
+- Don't quote your own prompt language ("just the goal", "read the skill", "no step-by-step from me", "decomposing into parallel workers"). The user doesn't care about your delegation pattern.
+- Don't narrate "handing off to a worker now" unless it's actually relevant (e.g. they asked how you work, or the work is going to take a noticeably long time).
+- Skip ceremony. A short acknowledgement + a brief description of the actual task + (optionally) a heads-up if there's anything they need to do or avoid is plenty.
+
+| What you might be tempted to say | What you should say instead |
+|---|---|
+| *"Got it \u2014 handing it off with just the goal + 'read the skills and figure it out.' No step-by-step from me."* | *"On it. Recording a screen capture of the Weather app showing Anchorage. Don't touch the keyboard while it's running \u2014 I'll post the video when it's done."* |
+| *"Decomposing into two parallel workers: one headless, one desktop."* | *"Running the tests and pulling the diff at the same time. Back in ~30s."* |
+| *"Spawning worker \`screenshot-calc\` with goal: \u2026"* | *"Taking a screenshot of Calculator now."* |
+| *"I'll relay the user's instructions to the worker verbatim."* | *(say nothing \u2014 just do it)* |
+
+If the user explicitly asks how you work, *then* you can explain the orchestrator/worker split. Otherwise: less is more.
+
 ### How to write a worker goal (and what NOT to put in it)
 
 You delegate; the worker executes. Stay at the **what** level, not the **how**.