0agent 1.0.86 → 1.0.87

package/dist/daemon.mjs

@@ -6441,16 +6441,46 @@ content = element.text if element else page.get_all_text()` : `content = page.ge
         if (isCodingTask) {
           lines.push(
             ``,
-            `\u2550\u2550\u2550 CODING DISCIPLINE \u2550\u2550\u2550`,
-            `Read before write. Always read a file before modifying it. Never write code in a vacuum.`,
-            `Incremental loop: make one logical change \u2192 run relevant tests \u2192 fix failures \u2192 repeat.`,
-            `Do not write 500 lines and then test. Write 50 lines, test, fix, continue.`,
-            `Keep functions under 40 lines. If a function grows past that, extract a helper.`,
-            `No TODO comments in committed code. Either implement it now or leave it out entirely.`,
-            `Match the codebase exactly: naming, indentation, import style, error handling patterns.`,
-            `Test alongside code. Non-trivial logic gets a test. Tests verify behavior, not implementation.`,
-            `After completing any coding task: write a concise HTML summary of what was built/changed,`,
-            `then call surge_publish to get a live shareable link. Include that link in your response.`
+            `\u2550\u2550\u2550 CODING DISCIPLINE (Claude Code level) \u2550\u2550\u2550`,
+            `You are an expert software engineer. Write production-quality code. Follow these rules precisely:`,
+            ``,
+            `EXPLORATION:`,
+            `  1. Read before write. ALWAYS read a file before modifying it. Understand the codebase first.`,
+            `  2. Search broadly: use shell_exec with rg/grep to find related files, imports, callers, tests.`,
+            `  3. Read the test file for any module you're changing. Understand expected behavior.`,
+            `  4. Read package.json/tsconfig/config files to understand the project setup.`,
+            ``,
+            `EDITING:`,
+            `  5. Use file_op(op:"edit") for surgical changes. Never rewrite entire files.`,
+            `  6. Each edit must be a minimal, precise find-and-replace. Include enough context to be unique.`,
+            `  7. When creating new files, follow existing patterns EXACTLY: naming, exports, imports, structure.`,
+            `  8. Match the codebase: tabs vs spaces, semicolons, quote style, import order, error handling.`,
+            ``,
+            `IMPLEMENTATION:`,
+            `  9. Incremental loop: one logical change \u2192 run tests \u2192 fix failures \u2192 commit \u2192 next change.`,
+            `  10. Keep functions under 40 lines. Extract helpers when complexity grows.`,
+            `  11. No TODO comments in committed code. Implement it or leave it out.`,
+            `  12. Handle errors properly. No empty catch {}. No swallowed promises. Propagate with context.`,
+            `  13. Validate at system boundaries (user input, API responses). Trust internal code.`,
+            `  14. Don't add features beyond what was asked. A bug fix doesn't need surrounding cleanup.`,
+            ``,
+            `TESTING:`,
+            `  15. Run the FULL test suite before declaring done, not just your new tests.`,
+            `  16. Write tests for non-trivial logic. Tests verify behavior, not implementation.`,
+            `  17. If tests fail, READ the error. Diagnose. Don't blindly retry or change random things.`,
+            ``,
+            `GIT:`,
+            `  18. Each commit = one logical change. Clear message explaining WHY, not just WHAT.`,
+            `  19. Never amend unless asked. Never force-push. Never skip hooks.`,
+            `  20. Stage specific files, not git add -A (avoid committing .env, credentials, binaries).`,
+            ``,
+            `SECURITY:`,
+            `  21. No command injection, XSS, SQL injection, path traversal, or OWASP top 10.`,
+            `  22. Sanitize user input at boundaries. Use parameterized queries. Escape shell args.`,
+            `  23. Never log passwords, tokens, or secrets. Never commit them to git.`,
+            ``,
+            `OUTPUT: After completing, publish an HTML summary via surge_publish if the user would benefit`,
+            `from a shareable artifact. Include the live link in your response.`
           );
         }
         if (isJustdoTask) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "0agent",
-  "version": "1.0.86",
+  "version": "1.0.87",
   "description": "A persistent, learning AI agent that runs on your machine. An agent that learns.",
   "private": false,
   "license": "Apache-2.0",