sparkecoder 0.1.70 → 0.1.71

package/dist/agent/index.d.ts

@@ -1,6 +1,6 @@
 import 'ai';
-import '../schema-XcP0dedO.js';
-export { A as Agent, a as AgentOptions, b as AgentRunOptions, c as AgentStreamResult, C as ContextManager, M as MessageAttachment, d as buildSystemPrompt, e as buildTaskPromptAddendum } from '../index-Dm6wGcYv.js';
-import '../search-CCffrVJE.js';
+import '../schema-C7Mm4Ykn.js';
+export { A as Agent, a as AgentOptions, b as AgentRunOptions, c as AgentStreamResult, C as ContextManager, M as MessageAttachment, d as buildSystemPrompt, e as buildTaskPromptAddendum } from '../index-CYNqPa6Z.js';
+import '../search-CVVfuBPZ.js';
 import 'drizzle-orm/sqlite-core';
 import 'zod';

package/dist/agent/index.js

@@ -5658,7 +5658,10 @@ Before calling \`complete_task\`, you MUST verify your work completely. Do not j
 
 **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.
+- Save screenshots and generated artifacts under \`.sparkecode-artifacts/\` (git-ignored) instead of the repo root.
+- Ensure \`.sparkecode-artifacts/\` is listed in \`.gitignore\`; if it is missing, add it before continuing.
 - 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.
+- In task results, never return local filesystem paths for screenshots/reports; return uploaded \`downloadUrl\` links only.
 - This is especially valuable for UI/visual changes, successful test runs, and browser verification \u2014 show, don't just tell.
 
 ### Use All Available Tools