opencode-gbuild 0.9.0 → 0.9.1

package/README.md

@@ -73,8 +73,8 @@ The npm package is published from this directory:
 One translation note: OpenCode plugins can't register agents, so where the Claude plugin spawns its
 bundled `gbuild-implementer`/`gbuild-reviewer`/`gbuild-auditor` agents, the OpenCode skills dispatch the
 built-in `general` subagent instead. For the implementer and reviewer the prompt is run's dispatch
-prompt as written, prefixed with `Read <Agent file> and follow it.`, where `<Agent file>` is the
-prompt's own `Agent file:` path; the auditor gets `Read <plugin>/agents/gbuild-auditor.md and follow
+prompt with its `Agent file: <path>.` field moved to the front as `Read <path> and follow it.`, so the
+path appears once; the auditor gets `Read <plugin>/agents/gbuild-auditor.md and follow
 it.` followed by exactly what the review skill passes it. The agent's text is never pasted into the
 prompt. The review is still a fresh, isolated agent — never the implementer.
 

package/agents/gbuild-implementer.md

@@ -9,7 +9,8 @@ You are implementing one gbuild node. Your prompt is a single line of paths:
 gbuild node `<slug>`. Store: <DB>. Worktree: <worktree>. Feature branch: <BRANCH>. Agent file: <plugin>/agents/gbuild-implementer.md.
 ```
 
-On OpenCode the prompt starts with `Read <agent file> and follow it.`, followed by that line.
+On OpenCode the `Agent file:` field moves to the front instead: the prompt starts with
+`Read <agent file> and follow it.`, followed by that line without its `Agent file:` field.
 
 Everything else — the node's title, type, acceptance, inputs, outputs, the failed criteria of a
 previous attempt, and notes left by earlier agents — is in the store, and you read it yourself. The
@@ -19,7 +20,8 @@ bullet. Do the work for real, and make the result file honest.
 
 ## PATHS
 
-- `<plugin>` — the agent-file path from your prompt minus `/agents/gbuild-implementer.md` (the
+- `<plugin>` — the agent-file path from your prompt (the `Agent file:` field, or the path in the
+  `Read … and follow it.` sentence on OpenCode) minus `/agents/gbuild-implementer.md` (the
   directory two levels above this file). Every script below is in `<plugin>/cypher/`. Always derive it
   from the prompt; no plugin-root environment variable is set for you.
 - `<feature>` — the path segment right before `/db` in `<DB>` (`…/gbuild/<feature>/db`).

package/agents/gbuild-reviewer.md

@@ -20,9 +20,11 @@ Your prompt is one line of paths and nothing else:
 gbuild node `<slug>`. Store: <DB>. Worktree: <worktree>. Feature branch: <BRANCH>. Agent file: <plugin>/agents/gbuild-reviewer.md.
 ```
 
-On OpenCode the prompt starts with `Read <agent file> and follow it.`, followed by that line.
+On OpenCode the `Agent file:` field moves to the front instead: the prompt starts with
+`Read <agent file> and follow it.`, followed by that line without its `Agent file:` field.
 
-`<plugin>` is the directory two levels above the agent-file path (the path minus
+`<plugin>` is the directory two levels above the agent-file path — the `Agent file:` field, or the
+path in the `Read … and follow it.` sentence on OpenCode (the path minus
 `/agents/gbuild-reviewer.md`). Never rely on `${CLAUDE_PLUGIN_ROOT}` here; derive it from the path.
 `<INBOX>` is the inbox directory beside `<DB>`: the `<DB>` path with its trailing `/db` replaced by
 `/inbox`. You fetch everything else yourself, in this order:

package/index.ts

@@ -38,8 +38,8 @@ instructions above:
   registered agents here. When the instructions say to spawn one, dispatch the
   built-in \`general\` subagent instead:
   - \`gbuild-implementer\` / \`gbuild-reviewer\`: the prompt is run's dispatch
-    template as written, prefixed with \`Read <Agent file> and follow it.\`,
-    where \`<Agent file>\` is the template's own \`Agent file:\` path
+    template with its closing \`Agent file: <path>.\` field moved to the front
+    as \`Read <path> and follow it.\` — the path appears once
     (\`${join(root, "agents", "gbuild-implementer.md")}\` /
     \`${join(root, "agents", "gbuild-reviewer.md")}\`).
   - \`gbuild-auditor\`: send

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "opencode-gbuild",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "description": "OpenCode plugin for gbuild — graph-native task planning and execution with concurrent fan-out, per-node review, and durable checkpoints.",
   "type": "module",
   "license": "MIT",

package/reference/checklist.md

@@ -30,7 +30,11 @@ fails means revise the graph (with Cypher), not add a caveat in prose.
     `retry` everywhere without thinking about it.
 12. **`model_tier` is `strong` only where judgement, not throughput, is the bottleneck** — see
     `reference/cost-model.md`.
-13. **The graph, run end to end with every node passing review, actually reaches `destination`.** Read
+13. **No `research`, `decision` or `verify` node's acceptance requires a file change.** Those nodes edit
+    no files (`graph-format.md`); an ADR, doc or other file a decision implies belongs to a `code` node
+    reading the decision's outputs. `validate.cypher` can't see this — acceptance is free text — so check
+    each one.
+14. **The graph, run end to end with every node passing review, actually reaches `destination`.** Read
     the `Feature` node's `destination` property back against the node set: if every node completed, is
     the feature actually done? A graph that's internally consistent but doesn't add up to the
     destination is still wrong.

package/reference/graph-format.md

@@ -88,13 +88,19 @@ serves is `SATISFIES` edges, not a property.
 
 | type       | label      | produces                                                              |
 | ---------- | ---------- | -------------------------------------------------------------------- |
-| `research` | `Research` | findings — an answer to a question, cited                             |
-| `decision` | `Decision` | a choice made and recorded, with the alternatives it ruled out         |
+| `research` | `Research` | findings — an answer to a question, cited, as output values            |
+| `decision` | `Decision` | a choice and the alternatives it ruled out, as output values           |
 | `code`     | `Code`     | a coherent, reviewable change, committed                               |
 | `test`     | `Test`     | coverage for behavior a `code` node landed, when genuinely separable  |
 | `verify`   | `Verify`   | a check on another node's output — never the same agent, never self  |
 | `chore`    | `Chore`    | mechanical work with no behavior change                                |
 
+**`research`, `decision` and `verify` nodes edit no files.** They get no worktree of their own — `run`
+gives them the feature worktree read-only — and deliver only through their `OUTPUT` values. When a
+choice or a finding must also land in the repo (an ADR, a doc), chart a `code` node that reads those
+outputs through `FROM` and commits the file. A `chore` would fail `orphan-chore` unless something
+depends on it.
+
 **`acceptance` must be concrete** — checkable by a fresh context with no other information. Not
 "looks correct" or "works well": name a file, a command's exit code, a specific behavior, or a literal
 output value.

package/skills/plan/SKILL.md

@@ -117,6 +117,9 @@ For each GbuildNode decide (full model in `graph-format.md`):
 
 - `slug` — kebab-case, immutable; what skills and the store key on. `title` — what the user reads.
 - `type` — `research | decision | code | test | verify | chore`, plus the matching PascalCase label.
+  `research`, `decision` and `verify` nodes get no worktree and edit no files — they deliver through
+  their `OUTPUT` values only. Anything that must land in the repo (an ADR, a doc, a config file) belongs
+  to a `code` node that reads those outputs through `FROM`.
 - **`OUTPUT` fields** — every node declares at least one, each with a precise `shape`
   (`<integer>`, `<list of changed file paths>`, `<commit sha>`). Values will be scalars or lists of
   scalars; for anything nested, the shape says it is a JSON-encoded string.