opencode-goal-plugin 0.1.7 → 0.1.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,10 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.1.8 — 2026-05-18
4
+
5
+ - Harden `--max-minutes` fallback arithmetic when mixed with millisecond duration overrides.
6
+ - Clarify plugin-default config merging and goal-text trust guidance.
7
+
3
8
  ## 0.1.7 — 2026-05-18
4
9
 
5
10
  - Accept bare final-line `goal:complete` and `goal:blocked` markers in addition to canonical bracketed markers, matching observed model output during smoke testing.
package/README.md CHANGED
@@ -124,7 +124,7 @@ Override any limit for a single goal:
124
124
 
125
125
  ### Plugin-level defaults
126
126
 
127
- Pass options when registering the plugin to change the defaults for all goals:
127
+ Pass options when registering the plugin to change the defaults for all goals. To combine with the `goal` command, merge this plugin entry into the config shown above.
128
128
 
129
129
  ```json
130
130
  {
package/SECURITY.md CHANGED
@@ -21,4 +21,4 @@ Relevant security-sensitive areas include:
21
21
  - incorrect command or hook handling across OpenCode versions
22
22
  - leakage of goal text through logs or status output
23
23
 
24
- The goal text is wrapped in `<goal_objective>` tags and the closing tag is escaped before insertion. Other structural tags used in continuation prompts (`<goal_continuation>`, `<progress_budget>`, etc.) are not escaped. Crafted goal text containing those literal strings would close the tag early in the plaintext prompt; the model treats it as text rather than structure, so the practical risk for a local single-user tool is negligible.
24
+ The goal text is wrapped in `<goal_objective>` tags and the closing tag is escaped before insertion. Other structural tags used in continuation prompts (`<goal_continuation>`, `<progress_budget>`, etc.) are not escaped. Crafted goal text containing those literal strings would close the tag early in the plaintext prompt; the model treats it as text rather than structure, so the practical risk for a local single-user tool is negligible. Do not paste untrusted third-party text into a goal; treat goal text as if you typed it directly into the assistant.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "opencode-goal-plugin",
3
- "version": "0.1.7",
3
+ "version": "0.1.8",
4
4
  "description": "Session-scoped /goal workflow for OpenCode.",
5
5
  "type": "module",
6
6
  "main": "./src/goal-plugin.js",
@@ -219,7 +219,11 @@ function parseGoalArguments(args, defaults) {
219
219
  continue
220
220
  }
221
221
  if (part === "--max-minutes") {
222
- if (nextIsValue) { options.maxDurationMs = toPositiveInteger(next, options.maxDurationMs / 60000) * 60000; i += 1 }
222
+ if (nextIsValue) {
223
+ options.maxDurationMs =
224
+ toPositiveInteger(next, Math.ceil(options.maxDurationMs / 60000)) * 60000
225
+ i += 1
226
+ }
223
227
  continue
224
228
  }
225
229
  if (part === "--max-tokens") {