sparkecoder 0.1.66 → 0.1.67

package/dist/{schema-C7Mm4Ykn.d.ts → schema-XcP0dedO.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-CCffrVJE.d.ts}

@@ -15,12 +15,12 @@ interface BashToolOptions {
 }
 declare function createBashTool(options: BashToolOptions): ai.Tool<{
     background: boolean;
-    id?: string | undefined;
     input?: string | undefined;
+    id?: string | undefined;
     command?: 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

@@ -6191,12 +6191,18 @@ Before calling \`complete_task\`, you MUST verify your work completely. Do not j
 - If the task asked for multiple things, verify EACH one individually.
 - If something doesn't look right, fix it \u2014 don't complete with known issues.
 
+**Screenshot your completed work:**
+- After completing a task, take a screenshot of the result when it makes sense (UI changes browser pages, etc.). You can use the browser skill to do this.
+- Use \`upload_file\` to upload the screenshot and include the download URL in your task result so the user can see proof of what was done.
+- This is especially valuable for UI/visual changes, successful test runs, and browser verification \u2014 show, don't just tell.
+
 ### Use All Available Tools
 - **load_skill**: Load specialized skills/knowledge relevant to the task. Check what skills are available and use them.
 - **explore_agent**: Use for codebase exploration and understanding before making changes.
 - **code_graph**: Use to understand type hierarchies, references, and impact before refactoring.
 - **todo**: Track your progress on multi-step tasks so you don't miss steps.
 - **bash**: Full shell access \u2014 run builds, tests, dev servers, open browsers, curl endpoints, anything.
+- **upload_file**: Upload files (screenshots, reports, exports) to cloud storage. Use this to include screenshots of completed work in your task result \u2014 visual proof is very helpful.
 
 ### Output Schema
 The \`complete_task\` tool expects a \`result\` object matching this JSON Schema: