wicked-garden 12.53.1 → 12.53.2

package/.claude-plugin/marketplace.json

@@ -1 +1 @@
-{"name": "wicked-garden", "owner": {"name": "Mike Parcewski"}, "plugins": [{"name": "wicked-garden", "source": "./", "description": "Your coding agent already plans and swarms \u2014 Wicked Garden is the curated toolkit for what it can't: proof-not-claims gates, code links grep can't see, deterministic refactor, cross-session memory, multi-model second opinions (fallback seats labelled). Don't fight the harness; fill its gaps. The gate needs wicked-vault (a self-contained infra peer, installed directly) and re-derives through garden's built-in engine; estate/bus are opt-in layers (wicked-testing and wicked-brain are retired \u2014 QE ships in-catalog as the qe domain, memory lives in wicked-estate).", "version": "12.53.1"}], "version": "12.53.1"}
+{"name": "wicked-garden", "owner": {"name": "Mike Parcewski"}, "plugins": [{"name": "wicked-garden", "source": "./", "description": "Your coding agent already plans and swarms \u2014 Wicked Garden is the curated toolkit for what it can't: proof-not-claims gates, code links grep can't see, deterministic refactor, cross-session memory, multi-model second opinions (fallback seats labelled). Don't fight the harness; fill its gaps. The gate needs wicked-vault (a self-contained infra peer, installed directly) and re-derives through garden's built-in engine; estate/bus are opt-in layers (wicked-testing and wicked-brain are retired \u2014 QE ships in-catalog as the qe domain, memory lives in wicked-estate).", "version": "12.53.2"}], "version": "12.53.2"}

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "wicked-garden",
-  "version": "12.53.1",
+  "version": "12.53.2",
   "description": "Your coding agent's harness already plans and swarms; Wicked Garden is the curated toolkit for what it can't do alone. Proof, not claims \u2014 gates re-derive 'done' through the internal loom engine (fail-closed, independently attested via wicked-vault), so a self-asserted pass can't lie its way green. Relationships grep can't see \u2014 the wicked-estate code graph + injected bus/dispatch/capability/archetype edges power blast-radius & lineage. Plus deterministic multi-file refactor (wicked-patch), cross-session memory + knowledge (the mem domain over wicked-estate), multi-model second opinions (fallback seats labelled) (jam:council), portable expertise as on-demand skill-refs, and evidence-gated testing (the in-catalog qe domain). It reads the shape of your work to apply the right rigor \u2014 steering, not a pipeline \u2014 then gets out of the way. The compiler stamps a self-contained evidence gate into any repo that runs with no wicked-garden installed. Don't fight the harness; fill its gaps. The evidence gate requires wicked-vault, a self-contained infra peer wicked-garden installs directly; wicked-bus is an opt-in layer \u2014 install what you'll use, the toolkit works without the rest.",
   "wicked_vault_version": "^0.5.0",
   "wicked_ledger_version": "^0.6.0",

package/CHANGELOG.md

@@ -2,6 +2,11 @@
 
 ## [Unreleased]
 
+## [12.53.2] — 2026-10-11
+
+### Fixed
+- **qe accept runs in one turn inside a governed unit (PR #1291, #1290).** With `WICKED_RUN_ID` set, `wicked-garden-qe` accept runs writer → executor → reviewer inline in one turn, with no sub-agent dispatch, and ends only on the recorded verdict. A claude QE seat no longer ends its turn on the writer's test plan.
+
 ## [12.53.1] — 2026-10-11
 
 ### Fixed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wicked-garden",
-  "version": "12.53.1",
+  "version": "12.53.2",
   "type": "module",
   "description": "Curated toolkit for what AI coding agents can't do alone: evidence-gated work, codegraph relationships, deterministic multi-file refactor, multi-model second opinions, and cross-session memory. Installs as a Claude Code plugin.",
   "keywords": [

package/skills/qe/refs/accept.md

@@ -87,6 +87,24 @@ invocation.)
 - `--phase review` — review existing evidence
 - `--json` — emit JSON envelope
 
+## Governed unit (`WICKED_RUN_ID` set): one turn, inline
+
+A governed wicked-crew unit (`WICKED_RUN_ID` is set) is ONE headless turn: whatever you print
+last is the unit's reply, and the engine reads its `VERDICT:` line. So, on every seat:
+
+- Run writer → executor → reviewer **inline, in this one turn**. Carry out each hand-off below
+  yourself: open the worker skill (Skill tool, or its SKILL.md from your catalog), do its steps,
+  and come back here. Do not dispatch an `Agent` / `Task` sub-agent or a fork. A headless unit has
+  none, and a forked result returns to nobody.
+- A worker's output (test plan, evidence report) is an **intermediate artifact**: save it under
+  `{EVIDENCE_DIR}` (`test-plan.md`, `evidence.json`) and continue to the next phase. Never end
+  your reply on it.
+- Never end the turn before step 6 has written the verdict row and your reply's last line is
+  `VERDICT: PASS` or `VERDICT: FAIL`. If a step fails, still finish: record FAIL with
+  `reason: inconclusive — <why>` and print that verdict line.
+- Reviewer isolation is evidence-only dispatch here: judge from the scenario, plan and evidence
+  files, never from what you saw while executing.
+
 ## Instructions
 
 ### Preflight: Validate Input
@@ -170,9 +188,9 @@ repo under audit, etc.) could otherwise inject instruction-looking prose
 writer's instruction turn. The writer has `allowed-tools: Read` so it can
 open the scenario itself.
 
-Hand off to the `wicked-garden-qe-acceptance-test-writer` worker skill (it runs in an isolated context):
+Hand off to the `wicked-garden-qe-acceptance-test-writer` worker skill (an isolated context where the host forks one; inline in a governed unit):
 
-**Hand-off** — open the `wicked-garden-qe-acceptance-test-writer` skill with the brief below as the argument; on Claude Code this is the Skill tool, on any other seat open the named skill from your catalog and carry it out inline, then continue here.
+**Hand-off** — open the `wicked-garden-qe-acceptance-test-writer` skill with the brief below as the argument; on Claude Code this is the Skill tool, on any other seat open the named skill from your catalog; either way carry it out inline in this turn (no sub-agent), then continue here.
 
 ```markdown
 Generate an evidence-gated test plan for the acceptance scenario
@@ -195,20 +213,23 @@ at the path below.
 6. Map every success criterion to specific assertions.
 7. Flag any specification mismatches you discover.
 
-Return the complete test plan in the standard format.
+Produce the complete test plan in the standard format. It is an intermediate
+artifact of `qe accept`: hand it back and continue (garden#1290).
 
 ```
 
-If `--phase write`, stop here.
+Save the plan to `{EVIDENCE_DIR}/test-plan.md` (the reviewer reads it from there).
+
+If `--phase write`, stop here. Otherwise continue to step 3 in this same turn.
 
 ### 3. Phase: Execute (Evidence Collection)
 
 The run record was already created in step 0 so the evidence dir could derive
 from its UUID. Here we dispatch the executor against that dir.
 
-Hand off to the `wicked-garden-qe-acceptance-test-executor` worker skill (it runs in an isolated context):
+Hand off to the `wicked-garden-qe-acceptance-test-executor` worker skill (an isolated context where the host forks one; inline in a governed unit):
 
-**Hand-off** — open the `wicked-garden-qe-acceptance-test-executor` skill with the brief below as the argument; on Claude Code this is the Skill tool, on any other seat open the named skill from your catalog and carry it out inline, then continue here.
+**Hand-off** — open the `wicked-garden-qe-acceptance-test-executor` skill with the brief below as the argument; on Claude Code this is the Skill tool, on any other seat open the named skill from your catalog; either way carry it out inline in this turn (no sub-agent), then continue here.
 
 ```markdown
 Execute this test plan and collect evidence artifacts.
@@ -227,13 +248,14 @@ Execute this test plan and collect evidence artifacts.
 5. Continue to next step even if current step fails
 6. Record timestamps for every step
 
-Return the complete evidence report.
+Produce the complete evidence report. It is an intermediate artifact of
+`qe accept`: hand it back and continue (garden#1290).
 
 ```
 
 Update run status in DomainStore after execution.
 
-If `--phase execute`, stop here.
+If `--phase execute`, stop here. Otherwise continue to step 4 in this same turn.
 
 ### 4. Phase: Pre-Review Cold Context (Optional, pre-dispatch validated)
 
@@ -279,7 +301,7 @@ if (result.rejected) {
 
 Example safe query:
 
-**Hand-off** — open the `wicked-garden-mem` skill and run its `recall` action with `<scenario-category> test rules` as the query; on Claude Code this is the Skill tool, on any other seat open the named skill from your catalog and carry it out inline, then continue here.
+**Hand-off** — open the `wicked-garden-mem` skill and run its `recall` action with `<scenario-category> test rules` as the query; on Claude Code this is the Skill tool, on any other seat open the named skill from your catalog; either way carry it out inline in this turn (no sub-agent), then continue here.
 
 If the knowledge layer is absent, skip this phase entirely — no `context.md` is
 written and the reviewer still has everything it needs (scenario + plan +
@@ -291,7 +313,7 @@ evidence).
 It does NOT receive the executor's conversation, reasoning, or stdout/stderr directly.
 Pass paths, not content, where possible.
 
-**Hand-off** — open the `wicked-garden-qe-acceptance-test-reviewer` skill with the brief below as the argument; on Claude Code this is the Skill tool, on any other seat open the named skill from your catalog and carry it out inline, then continue here.
+**Hand-off** — open the `wicked-garden-qe-acceptance-test-reviewer` skill with the brief below as the argument; on Claude Code this is the Skill tool, on any other seat open the named skill from your catalog; either way carry it out inline in this turn (no sub-agent), then continue here.
 
 ```markdown
 Review the evidence against the test plan assertions.
@@ -314,9 +336,11 @@ flag as CONTEXT_CONTAMINATION and return `VERDICT: FAIL` with
 2. Read the test plan file at the path above
 3. Read evidence files from the evidence directory (including context.md if present)
 4. Evaluate each assertion against evidence
-5. End with one plain-text line `VERDICT: PASS` or `VERDICT: FAIL` as the LAST
-   line of your reply (never quote another VERDICT line); missing evidence or
-   CONTEXT_CONTAMINATION is FAIL with `reason: inconclusive — <why>`
+5. End the review with one plain-text line `VERDICT: PASS` or `VERDICT: FAIL`
+   (never quote another VERDICT line); missing evidence or
+   CONTEXT_CONTAMINATION is FAIL with `reason: inconclusive — <why>`. Hand the
+   review back: `qe accept` still writes the verdict (step 6) and prints that
+   line last (garden#1290)
 6. For any EQUIVALENT_TO_BASELINE assertion, also return the equivalence facet
    { baseline_ref, baseline_sha, method, diff_count, tolerance, matched } so the
    orchestrator can persist it on the verdict (see `verdict.equivalence`).
@@ -432,6 +456,9 @@ emitBusEvent('wicked.test.evidence.captured', {
 
 ### 7. Output
 
+The reply's LAST line is the reviewer's `VERDICT: PASS` or `VERDICT: FAIL`, printed
+only after step 6 wrote the verdict row. This is what ends the turn.
+
 **Without `--json`** — Present the full verdict:
 
 ```markdown

package/skills/qe-acceptance-test-executor/SKILL.md

@@ -133,6 +133,11 @@ python3 -c "import json,sys; sys.stdout.write(json.dumps({...}))" 2>/dev/null \
 
 ### 6. Compile Evidence Report
 
+**Opened from `qe accept`** (garden#1290): your evidence report is an intermediate artifact of that
+pipeline, not the end of the turn. Hand it back and the pipeline continues to the reviewer in the
+same turn. Never end the turn on it, above all in a governed unit (`WICKED_RUN_ID` set), where your
+last output is the unit's reply.
+
 Return a text evidence report with all captured data:
 
 ```markdown

package/skills/qe-acceptance-test-reviewer/SKILL.md

@@ -180,6 +180,9 @@ Review any specification notes from the test plan writer. Factor these into your
 ```markdown
 ## Overall Verdict
 
+**Opened from `qe accept`** (garden#1290): hand this review back and continue. `qe accept` writes the
+verdict row (its step 6) and then prints the `VERDICT:` line last; that, not this review, ends the turn.
+
 ### Status: {PASS | FAIL | PARTIAL | INCONCLUSIVE}
 
 ### Summary

package/skills/qe-acceptance-test-writer/SKILL.md

@@ -26,6 +26,11 @@ Your test plans are designed so that:
 
 You do NOT execute tests. You do NOT grade results. You produce test plans.
 
+**Opened from `qe accept`** (garden#1290): your test plan is an intermediate artifact of that
+pipeline, not the end of the turn. Hand it back and the pipeline continues to the executor in the
+same turn. Never end the turn on it, above all in a governed unit (`WICKED_RUN_ID` set), where your
+last output is the unit's reply.
+
 ## Why You Can Query Brain
 
 You have `Skill` access so you can query the knowledge layer (wicked-estate,