wicked-garden 12.46.0 → 12.47.0

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, real multi-model second opinions. 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.46.0"}], "version": "12.46.0"}
+{"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, real multi-model second opinions. 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.47.0"}], "version": "12.47.0"}

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "wicked-garden",
-  "version": "12.46.0",
+  "version": "12.47.0",
   "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), real multi-model second opinions (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.4.0",

package/CHANGELOG.md

@@ -2,6 +2,11 @@
 
 ## [Unreleased]
 
+## [12.47.0] — 2026-10-09
+
+### Changed
+- **governed-worker evaluator rule E4: "the same as X" is judged on values, from both sides (wicked-garden#1253, PR #1254).** For an acceptance item that says the new work matches an existing surface ("the form's posture", "the same body as the launch form"), the evaluator derives the value X actually produces — from X's own code path or the run's recorded output — quotes it with `file:line` beside the new code's value for the same inputs, and compares them. Field presence, a matching label or a creator-pinned test value is never the evidence; a difference is a Critical, and an underived X-side value is not a PASS. The rule carries the S19a case (`before:1` pinned by the creator vs the form's `before:2`) as its worked FAIL example, and the review archetype's assess step points parity items at it.
+
 ## [12.46.0] — 2026-10-09
 
 ### Fixed
@@ -1006,7 +1011,8 @@ through `v9.2.18`. Major themes across that span:
 
 For each of those releases, see the corresponding tag in git history.
 
-[Unreleased]: https://github.com/mikeparcewski/wicked-garden/compare/v12.46.0...HEAD
+[Unreleased]: https://github.com/mikeparcewski/wicked-garden/compare/v12.47.0...HEAD
+[12.47.0]: https://github.com/mikeparcewski/wicked-garden/compare/v12.46.0...v12.47.0
 [12.46.0]: https://github.com/mikeparcewski/wicked-garden/compare/v12.45.0...v12.46.0
 [12.45.0]: https://github.com/mikeparcewski/wicked-garden/compare/v12.44.0...v12.45.0
 [12.44.0]: https://github.com/mikeparcewski/wicked-garden/compare/v12.43.0...v12.44.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wicked-garden",
-  "version": "12.46.0",
+  "version": "12.47.0",
   "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/archetype/refs/review.md

@@ -74,7 +74,14 @@ in three domains").
    the artifact as the argument; on Claude Code this is the Skill tool, on any other seat
    open the named skill from your catalog and run it inline, keeping its output separate
    from yours, then continue here.
-3. For high-stakes reviews, run a council via the
+3. **Parity items compare values (garden#1253).** For every item that says the
+   work matches an existing surface ("the same as the form", "like the Desk
+   row"), derive the value that surface produces — from its own code path or
+   the run's recorded output — and quote it beside the new code's value, both
+   with `file:line`. Presence of the field, or a test the author wrote pinning
+   a value, is not evidence; a difference is a blocker (the governed-worker
+   floor's rule E4).
+4. For high-stakes reviews, run a council via the
    `wicked-garden-jam-council` skill — independent multi-model verdicts
    catch what a single reviewer misses.
 

package/skills/governed-worker/SKILL.md

@@ -106,6 +106,21 @@ verdict with reasons. You are output-only.
 - **E3 — Every verdict item is in scope** unless a human ruling strikes it by
   name. A creator's deferral, a "follow-up" note or a sendback that drops an item
   does not remove it; judge it, or cite the ruling that struck it.
+- **E4 — "The same as X" is judged on VALUES, from both sides.** For an
+  acceptance item that says the new work matches an existing surface ("the
+  form's posture", "the same body as the launch form", "like the Desk row"),
+  derive the value X actually produces: read X's own code path, or the run's
+  recorded output (its launch body, its event), and quote it with `file:line`.
+  Then quote the new code's value the same way — for the SAME inputs (the same
+  choice, the same launch) — and compare the two. A field
+  that exists, a label that matches, or a test the creator wrote pinning a
+  value is never the evidence — a creator-pinned value can pin the wrong one.
+  Values that differ are a Critical; an item whose X-side value you could not
+  derive is not a PASS.
+  Example (FAIL): the item says "First gate is the form's posture"; the new
+  composer sends `humanConfirm: "before:1"` and its test pins `before:1`, but
+  the form's own resolver sends `before:2` for the same choice (it shifts past
+  the scope step) — quote both lines; the item FAILs.
 
 Method: read the outcome and design, then the changed files; for each, ask
 whether it follows the design, whether tests cover the key paths, and whether
@@ -169,6 +184,7 @@ Rules cite the acceptance-program findings that motivated them.
 | E1 | F-RC1-060, F-RC1-062, F-RC1-071, F-RC2-037 |
 | E2 | program rule — the floor provisions |
 | E3 | garden#1223 (companion to wicked-core#760) |
+| E4 | garden#1253 (S19a: `before:1` vs the form's `before:2`, passed on presence) |
 | N1 | F-RC2-038 |
 
 History: the `crew-implementer`, `crew-reviewer` and `crew-researcher` fork-agent definitions