@opencode_weave/weave - npm Package Compare versions

Comparing version 0.7.6-preview.3 to 0.7.6

dist/features/builtin-commands/templates/start-work.d.ts

@@ -1,1 +0,1 @@
-export declare const START_WORK_TEMPLATE = "You are being activated by the /start-work command to execute a Weave plan.\n\n## Your Mission\nRead and execute the work plan, completing each unchecked task until every checkbox is checked.\n\nExecution is non-terminal while any `- [ ]` task remains.\nDo not stop, ask what to do next, or wait for acknowledgment while unchecked tasks remain.\n\n## Startup Procedure\n\n1. **Check for active work state**: Read `.weave/state.json` to see if there's a plan already in progress.\n2. **If resuming**: The system has injected context below with the active plan path and progress. Read the plan file, find the first unchecked `- [ ]` task, and continue from there.\n3. **If starting fresh**: The system has selected a plan and created work state. Read the plan file and begin from the first unchecked task.\n\n## Execution Loop\n\nFor each unchecked `- [ ]` task in the plan:\n\n1. **Read** the task description, acceptance criteria, and any references\n2. **Execute** the task \u2014 write code, run commands, create files as needed\n3. **Verify** the work \u2014 run tests, check for errors, validate acceptance criteria\n4. **Mark complete** \u2014 use the Edit tool to change `- [ ]` to `- [x]` in the plan file\n5. **Report progress** \u2014 \"Completed task N/M: [title]\"\n6. **Continue immediately** \u2014 find the next unchecked task and begin it without waiting for user acknowledgment\n\n## Rules\n\n- Work through tasks **top to bottom** unless dependencies require a different order\n- **Verify every task** before marking it complete\n- A progress update is **not** a stopping point\n- Do **not** ask the user what to do next while unchecked tasks remain\n- Do **not** mention final review or final summary while unchecked tasks remain\n- If the current task is blocked, document the reason and move to the next unchecked task that is not blocked\n- Stop only when:\n  1. all checkboxes are checked, or\n  2. the user explicitly tells you to stop, or\n  3. every remaining unchecked task is truly blocked\n- After all tasks are complete, run any required post-execution review and then report a final summary";
+export declare const START_WORK_TEMPLATE = "You are being activated by the /start-work command to execute a Weave plan.\n\n## Your Mission\nRead and execute the work plan, completing each unchecked task until every checkbox is checked.\n\nExecution is non-terminal while any `- [ ]` task remains.\nDo not stop, ask what to do next, or wait for acknowledgment while unchecked tasks remain.\n\n## Startup Procedure\n\n1. **Check for active work state**: Read `.weave/state.json` to see if there's a plan already in progress.\n2. **If resuming**: The system has injected context below with the active plan path and progress. Read the plan file, find the first unchecked `- [ ]` task, and continue from there.\n3. **If starting fresh**: The system has selected a plan and created work state. Read the plan file and begin from the first unchecked task.\n\n## Execution Loop\n\nFor each unchecked `- [ ]` task in the plan:\n\n1. **Read** the task description, acceptance criteria, and any references\n2. **Execute** the task \u2014 write code, run commands, create files as needed\n3. **Verify** the work \u2014 run tests, check for errors, validate acceptance criteria\n4. **Mark complete** \u2014 use the Edit tool to change `- [ ]` to `- [x]` in the plan file\n5. **Report progress** \u2014 \"Completed task N/M: [title]\"\n6. **Continue immediately** \u2014 find the next unchecked task and begin it without waiting for user acknowledgment\n\n## Rules\n\n- Work through tasks **top to bottom** unless dependencies require a different order\n- **Verify every task** before marking it complete\n- A progress update is **not** a stopping point\n- Do **not** ask the user what to do next while unchecked tasks remain\n- Do **not** mention terminal validation, review, reviewers, final summary, completion, or post-execution steps while unchecked tasks remain\n- If asked what to do now while unchecked tasks remain, answer with only the immediate next execution action\n- Keep mid-plan responses to one sentence or one short bullet\n- If the current task is blocked, document the reason and move to the next unchecked task that is not blocked\n- Stop only when:\n  1. all checkboxes are checked, or\n  2. the user explicitly tells you to stop, or\n  3. every remaining unchecked task is truly blocked\n- When all tasks are complete, switch to terminal-state behavior";

package.json

 {
   "name": "@opencode_weave/weave",
-  "version": "0.7.6-preview.3",
+  "version": "0.7.6",
   "description": "Weave — lean OpenCode plugin with multi-agent orchestration",
@@ -5,0 +5,0 @@ "author": "Weave",

New alerts

Long strings

Supply chain risk

Contains long string literals, which may be a sign of obfuscated or packed code.

URL strings

Supply chain risk

Package contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.

Fixed alerts

Long strings

Supply chain risk

Contains long string literals, which may be a sign of obfuscated or packed code.

URL strings

Supply chain risk

Package contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.

Improved metrics

Total package byte prevSize

548043

0.14%

Lines of code

13934

0.06%

No dependency changes