wicked-garden 12.55.0 → 12.55.1

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.55.0"}], "version": "12.55.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, 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.55.1"}], "version": "12.55.1"}

package/.claude-plugin/plugin.json

@@ -1,8 +1,8 @@
 {
   "name": "wicked-garden",
-  "version": "12.55.0",
+  "version": "12.55.1",
   "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_vault_version": ">=0.8.0",
   "wicked_ledger_version": "^0.6.0",
   "wicked_bus_version": "^2.0.0",
   "author": {

package/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 ## [Unreleased]
 
+## [12.55.1] — 2026-10-15
+
+### Fixed
+- **Bump the `wicked-vault` peer floor to `>= 0.8.0` and drop stale "unreleased manifest-2.1 twin" notes (garden#1309).** `.claude-plugin/plugin.json` now declares `"wicked_vault_version": ">=0.8.0"` (replacing `"^0.5.0"`, whose `0.x` caret excluded every later minor), in lockstep with `scripts/loom/manifest.py` (`version_pin="0.8"`) and every `<!-- vault-floor -->` doc/skill restatement. `VAULT_RELEASE_REQUIREMENT` in `scripts/qe/lib/vault-evidence.mjs` and the QE docs/help strings now point to `npm i -g wicked-vault@latest` (the manifest-2.1 twin shipped in 0.7.0; 0.8.0 is the current floor).
+- **The plugin's Python range stops below 3.15 until its dependencies ship 3.15 wheels.** `pydantic-core` (via `pydantic`) has no CPython 3.15 wheel. A 3.15 default interpreter (the macOS GitHub runners and Homebrew `python@3.15`) made `uv sync` build it from source with Rust, which fails without a toolchain. That blocked wicked-crew's first skills publish (its release smoke S02 on macOS, and any 3.15-only host without Rust). `requires-python` is now `>=3.10,<3.15` (uv.lock relocked at the same lock revision), so uv picks or downloads a 3.14. Lift the bound once pydantic-core publishes cp315 wheels.
+
 ## [12.55.0] — 2026-10-14
 
 ### Added
@@ -1129,7 +1135,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.55.0...HEAD
+[Unreleased]: https://github.com/mikeparcewski/wicked-garden/compare/v12.55.1...HEAD
+[12.55.1]: https://github.com/mikeparcewski/wicked-garden/compare/v12.55.0...v12.55.1
 [12.55.0]: https://github.com/mikeparcewski/wicked-garden/compare/v12.54.0...v12.55.0
 [12.54.0]: https://github.com/mikeparcewski/wicked-garden/compare/v12.53.3...v12.54.0
 [12.53.3]: https://github.com/mikeparcewski/wicked-garden/compare/v12.53.2...v12.53.3

package/CONTRIBUTING.md

@@ -29,7 +29,7 @@ uv run pytest tests/ -x
 
 **For offline CI and dev environments without the wicked-vault peer only.**
 
-wicked-vault (npm, ≥ 0.5.0 <!-- vault-floor -->, install `npm i -g wicked-vault`)
+wicked-vault (npm, ≥ 0.8.0 <!-- vault-floor -->, install `npm i -g wicked-vault`)
 is the one required peer (the loom engine is built into the garden; bus is an
 opt-in layer). The garden's produces-gates re-derive
 evidence through the built-in loom engine — `scripts/qe/vault_gate.py` runs

package/README.md

@@ -86,7 +86,7 @@ Then, in a Claude Code session:
 **One required peer, the rest opt-in.** The evidence gate is the floor we won't fake, so it needs one external peer — setup blocks without it:
 
 ```bash
-npm i -g wicked-vault          # wicked-vault (≥ 0.5.0), the honest-evidence backend the gate re-derives against
+npm i -g wicked-vault          # wicked-vault (≥ 0.8.0), the honest-evidence backend the gate re-derives against
 ```
 
 > The gate/resolve engine (formerly the separate `wicked-loom` package) is now **absorbed in-package** as of v12.27.0 (`scripts/loom/`) — nothing extra to install. The gate re-hashes recorded evidence and re-runs its verifier through that engine; a false "tests pass" is **rejected**, a missing backend **fails closed**.
@@ -170,7 +170,7 @@ Full author guide: [`docs/extending.md`](docs/extending.md).
 
 ## Requirements
 
-A coding-agent harness ([Claude Code](https://docs.anthropic.com/en/docs/claude-code/overview) ≥ 1.0 for the plugin surface; the peers + compiled gate are harness-agnostic) · Python 3.9+ (stdlib-only hooks) · Node + `npx` · the gate's one required peer (`wicked-vault` ≥ 0.5.0) plus opt-in layers (`wicked-estate` · `wicked-bus`).
+A coding-agent harness ([Claude Code](https://docs.anthropic.com/en/docs/claude-code/overview) ≥ 1.0 for the plugin surface; the peers + compiled gate are harness-agnostic) · Python 3.9+ (stdlib-only hooks) · Node + `npx` · the gate's one required peer (`wicked-vault` ≥ 0.8.0) plus opt-in layers (`wicked-estate` · `wicked-bus`).
 
 ## License
 

package/docs/extending.md

@@ -51,7 +51,7 @@ A complete working example (used as garden's own e2e fixture):
       ]
     }
   ],
-  "peers": { "wicked-garden": ">=12.0.0", "wicked-vault": ">=0.5.0" },
+  "peers": { "wicked-garden": ">=12.0.0", "wicked-vault": ">=0.8.0" },
   "provenance": { "source": "https://github.com/acme/acme-seo-pack", "publisher": "acme" }
 }
 ```

package/docs/required-peers.md

@@ -18,7 +18,7 @@ works.
 
 | Peer | What it does | Install |
 |------|--------------|---------|
-| **wicked-vault** | The honest-evidence backend the gate re-derives against: record → re-hash + re-run the verifier → cross-check. Never trusts a cached status. | `npm i -g wicked-vault` — puts the `wicked-vault` binary on PATH (optionally run `wicked-vault-install` afterwards to copy the vault skills into your AI CLIs). Declared floor: **≥ 0.5.0** <!-- vault-floor --> (on 0.4.x or older, upgrade with `npm i -g wicked-vault@latest` — the peer registry's health probe, `loom doctor` / the peer-health command, reports a below-floor vault as `drift` and fails its check). Resolved at runtime via `WICKED_VAULT_BIN` → config → `PATH` → `node_modules` → `npx wicked-vault`. |
+| **wicked-vault** | The honest-evidence backend the gate re-derives against: record → re-hash + re-run the verifier → cross-check. Never trusts a cached status. | `npm i -g wicked-vault` — puts the `wicked-vault` binary on PATH (optionally run `wicked-vault-install` afterwards to copy the vault skills into your AI CLIs). Declared floor: **≥ 0.8.0** <!-- vault-floor --> (below 0.8.0, upgrade with `npm i -g wicked-vault@latest` — the peer registry's health probe, `loom doctor` / the peer-health command, reports a below-floor vault as `drift` and fails its check). Resolved at runtime via `WICKED_VAULT_BIN` → config → `PATH` → `node_modules` → `npx wicked-vault`. |
 
 The core skill's `setup` action (`/wicked-garden-core setup`) **blocks** without
 it — a toolkit whose headline is "done is re-derived, not asserted" cannot ship
@@ -35,7 +35,7 @@ single source of truth; every doc restatement of the number is tagged with a
 `<!-- vault-floor -->` marker (README's bash-comment restatement can't carry an
 HTML comment, so grep the number too). **To bump the floor:** change
 `manifest.py` + `plugin.json`, then
-`grep -rn "vault-floor\|0\.5\.0" README.md CONTRIBUTING.md docs/ skills/` and
+`grep -rn "vault-floor\|0\.8\.0" README.md CONTRIBUTING.md docs/ skills/` and
 update every tagged restatement in the same commit.
 
 ## The built-in gate engine (loom) — nothing to install

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wicked-garden",
-  "version": "12.55.0",
+  "version": "12.55.1",
   "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/pyproject.toml

@@ -7,7 +7,11 @@ name = "wicked-garden"
 # not bump it — PEP 621 requires a value, so it is pinned to the placeholder 0.0.0 (mirrored in uv.lock).
 version = "0.0.0"
 description = "AI-Native SDLC delivered as a single Claude Code plugin"
-requires-python = ">=3.10"
+# <3.15 (garden 12.55.1): pydantic-core (via pydantic) ships no CPython 3.15 wheel yet, so a 3.15
+# default interpreter (macOS runners and Homebrew since 2026-10) made `uv sync` build it from source
+# with Rust — which fails without a toolchain, blocking crew's first skills publish. With the bound,
+# uv picks (or downloads) a 3.14. Lift it once pydantic-core publishes cp315 wheels.
+requires-python = ">=3.10,<3.15"
 dependencies = [
     "rapidfuzz>=3.0",
     "aiofiles>=23.0",

package/schemas/wicked-pack.schema.json

@@ -107,7 +107,7 @@
     },
     "peers": {
       "type": "object",
-      "description": "Peer version floors (extension-contract gap 6), e.g. {\"wicked-garden\": \">=12.29.0\", \"wicked-vault\": \">=0.5.0\"}. Checked FAIL-OPEN: violations are surfaced at SessionStart and by `pack floors`, never blocked on.",
+      "description": "Peer version floors (extension-contract gap 6), e.g. {\"wicked-garden\": \">=12.29.0\", \"wicked-vault\": \">=0.8.0\"}. Checked FAIL-OPEN: violations are surfaced at SessionStart and by `pack floors`, never blocked on.",
       "additionalProperties": { "type": "string", "pattern": "^(>=|\\^)\\s*\\d+\\.\\d+\\.\\d+$" }
     },
     "provenance": {

package/scripts/_pack_registry.py

@@ -28,7 +28,7 @@ skills tree. There is NO signing — the hashes detect post-registration drift,
 they do not prove authorship. See docs/extending.md "Trust model".
 
 Peer floors (gap 6, fail-open): a pack may declare ``peers`` —
-``{"wicked-garden": ">=12.29.0", "wicked-vault": ">=0.5.0"}``.
+``{"wicked-garden": ">=12.29.0", "wicked-vault": ">=0.8.0"}``.
 ``check_peer_floors()`` compares floors against what is actually installed
 and returns violations as data. It NEVER raises and never blocks: an
 unprobeable peer reports status "unknown", not a violation.

package/scripts/loom/manifest.py

@@ -94,10 +94,11 @@ PEERS: dict = {
         name="vault",
         npm_package="wicked-vault",
         env_var="WICKED_VAULT_BIN",
-        # 0.5 floor (Phase 6c): vault >= 0.5.0 stamps bus events with the qe
-        # domain (0.4 floor was the hard-gate attest baseline). Keep this
-        # MAJOR.MINOR floor in lockstep with plugin.json's ``wicked_vault_version``.
-        version_pin="0.5",
+        # 0.8 floor: the manifest-2.1 twin the QE evidence flow needs shipped
+        # in 0.7.0, and 0.8.0 enforces contract pins and re-validates
+        # attestations. Keep this MAJOR.MINOR floor in lockstep with
+        # plugin.json's ``wicked_vault_version``.
+        version_pin="0.8",
         # wicked-vault is a DIRECT infra peer, published from its own repo
         # (mikeparcewski/wicked-vault): self-contained, zero runtime deps. Install
         # it directly. ``npm i -g wicked-vault``

package/scripts/qe/lib/gate.mjs

@@ -73,10 +73,10 @@
  *   - A bundle that failed manifest validation (downgraded above) is NOT
  *     vaulted — the downgraded INCONCLUSIVE verdict records with
  *     `vault: {skipped}` instead (never freeze a nonconforming bundle).
- *   - Release dependency: needs the wicked-vault manifest-2.1 twin —
- *     UNRELEASED (npm 0.6.0 predates it). Until the next wicked-vault
- *     release, `WICKED_QE_VAULT_PKG` must point at a local checkout of
- *     wicked-vault main; a pre-2.1 vault is refused fail-closed.
+ *   - Release dependency: needs wicked-vault >= 0.8.0 (the manifest-2.1 twin
+ *     shipped in 0.7.0; garden's floor is 0.8.0). An older vault is refused
+ *     fail-closed — upgrade with `npm i -g wicked-vault@latest` (or set
+ *     `WICKED_QE_VAULT_PKG` to point at a specific 0.8.0+ install).
  */
 
 import { existsSync, readdirSync, readFileSync } from "node:fs";
@@ -339,7 +339,8 @@ export async function runGate({ projectId, runId, verdict, verdictSummary, ratio
   // 2c. TH-17: resolve wicked-vault up front when vault integrity was asked
   //     for — fail fast (exit 3) on an unresolvable or pre-2.1 vault, BEFORE
   //     anything is written anywhere. The refusal message carries the release
-  //     dependency (the manifest-2.1 twin is unreleased; npm 0.6.0 predates it).
+  //     dependency (the manifest-2.1 twin shipped in 0.7.0; floor is 0.8.0 —
+  //     upgrade with `npm i -g wicked-vault@latest`).
   const wantsVault = Boolean(vaultRecord || vaultEntry);
   let vaultModule = null;
   if (wantsVault) {
@@ -556,8 +557,9 @@ Optional:
                             (content-addressed) and attest the verdict as the reviewer's
                             opinion; the verdicts row carries vault_payload_sha. REFUSES
                             unredacted bundles (TH-19 ordering) — exit 3, nothing recorded.
-                            Needs the wicked-vault manifest-2.1 twin (unreleased; set
-                            WICKED_QE_VAULT_PKG to a wicked-vault main checkout until then)
+                            Needs wicked-vault >= 0.8.0 (the manifest-2.1 twin shipped in
+                            0.7.0; upgrade with \`npm i -g wicked-vault@latest\`, or set
+                            WICKED_QE_VAULT_PKG to a specific 0.8.0+ install)
   --vault-entry <id>        TH-17: link an already-vaulted bundle instead of recording;
                             re-derived fail-closed before the verdict is recorded
   --vault-actor <id>        Recording (worker) identity for --vault-record (default: qe-runner)

package/scripts/qe/lib/vault-evidence.mjs

@@ -44,12 +44,10 @@
  *
  * RELEASE DEPENDENCY (documented, enforced by `resolveVaultModule`):
  * this flow needs the wicked-vault manifest-2.1 twin (`validateManifest` +
- * `CLAIM_LEVELS` exports — on wicked-vault main, UNRELEASED as of
- * 2026-08-30; npm wicked-vault 0.6.0 predates it and its vendored schema
- * rejects every 2.1 bundle). Until the next wicked-vault release, point
- * `WICKED_QE_VAULT_PKG` at a local checkout of wicked-vault main (or
- * `npm link` it); a pre-2.1 vault is refused fail-closed, never silently
- * degraded.
+ * `CLAIM_LEVELS` exports, shipped in wicked-vault 0.7.0; garden's floor is
+ * 0.8.0). An older vault is refused fail-closed, never silently degraded —
+ * upgrade with `npm i -g wicked-vault@latest` (or set `WICKED_QE_VAULT_PKG`
+ * to point at a specific wicked-vault 0.8.0+ install).
  *
  * CLI (from the target repo's root):
  *   node vault-evidence.mjs record   --evidence-dir <dir> [--repo-root <dir>]
@@ -75,10 +73,9 @@ import { scanForSecrets, compileExtraPatterns } from "../runner/src/redact.mjs";
 
 /** The one-line release dependency, stamped on every pre-2.1 refusal. */
 export const VAULT_RELEASE_REQUIREMENT =
-  "wicked-vault with the manifest-2.1 twin (validateManifest + CLAIM_LEVELS) is required — " +
-  "on wicked-vault main but UNRELEASED (npm 0.6.0 predates it and rejects 2.1 bundles). " +
-  "Until the next wicked-vault release: set WICKED_QE_VAULT_PKG to a local checkout of " +
-  "wicked-vault main, or `npm link wicked-vault` from one.";
+  "wicked-vault >= 0.8.0 is required (the manifest-2.1 twin, validateManifest + CLAIM_LEVELS, " +
+  "shipped in 0.7.0) — upgrade with `npm i -g wicked-vault@latest`, or set WICKED_QE_VAULT_PKG " +
+  "to a wicked-vault 0.8.0+ install.";
 
 /** Typed refusal so callers (gate.mjs, tests) can tell WHY the write was refused. */
 export class VaultEvidenceError extends Error {
@@ -116,9 +113,9 @@ function esmEntryForPackage(resolvedFile) {
 
 /**
  * Capability gate: is this module a wicked-vault WITH the manifest-2.1 twin?
- * npm 0.6.0 has record/attest/verify but NOT validateManifest/CLAIM_LEVELS —
- * that is the unreleased seam this flow depends on (see
- * VAULT_RELEASE_REQUIREMENT). Exported for tests.
+ * The twin (`validateManifest` + `CLAIM_LEVELS`) shipped in wicked-vault 0.7.0
+ * and garden's floor is 0.8.0; an older vault without those exports is refused
+ * fail-closed (see VAULT_RELEASE_REQUIREMENT). Exported for tests.
  */
 export function checkVaultCapability(mod) {
   if (!mod || typeof mod !== "object") return { ok: false, reason: "not a module" };
@@ -135,8 +132,8 @@ export function checkVaultCapability(mod) {
 
 /**
  * Resolve the wicked-vault module, fail-closed on capability:
- *   1. `WICKED_QE_VAULT_PKG` env — path to a wicked-vault package dir (or its
- *      entry file). The documented bridge until the next vault release.
+ *   1. `WICKED_QE_VAULT_PKG` env — optional pointer to a specific wicked-vault
+ *      package dir (or its entry file).
  *   2. bare `import("wicked-vault")` (global / hoisted install).
  *   3. the target repo's node_modules (cwd-anchored resolution).
  * A resolved-but-pre-2.1 vault is a refusal, not a fallback.
@@ -551,9 +548,10 @@ Subcommands:
             Re-derive the bundle months later: vault hashes + every artifact
             re-hashed on disk. Exit 1 on ANY divergence.
 
-wicked-vault resolution: WICKED_QE_VAULT_PKG (local checkout — required until
-the next wicked-vault release ships the manifest-2.1 twin) → global install →
-the repo's node_modules. A pre-2.1 vault is refused fail-closed.
+wicked-vault resolution: WICKED_QE_VAULT_PKG (optional pointer to a specific
+wicked-vault 0.8.0+ install) → global install → the repo's node_modules. An
+older vault without the manifest-2.1 twin (shipped in 0.7.0; floor 0.8.0) is
+refused fail-closed — upgrade with \`npm i -g wicked-vault@latest\`.
 
 Exit codes: 0 ok · 1 rederive divergence · 3 refusal / usage / system error.
 `;

package/scripts/qe/runner/README.md

@@ -218,12 +218,11 @@ the reviewer's grade appended as an opinion attestation — see
 --vault-record`. The vault payload is `manifest.json` (content-addressed; it
 binds every artifact's sha256), so a campaign PASS re-derives months later.
 **Release dependency:** the flow needs the wicked-vault manifest-2.1 twin
-(`validateManifest` + `CLAIM_LEVELS`) — on wicked-vault main, **unreleased**
-(npm 0.6.0 predates it and its vendored schema rejects 2.1 bundles). Until
-the next wicked-vault release, set `WICKED_QE_VAULT_PKG` to a local checkout
-of wicked-vault main (or `npm link` one); a pre-2.1 vault is refused
-fail-closed. The `th17-vault-evidence` tests skip with that exact message
-when no 2.1 vault is resolvable.
+(`validateManifest` + `CLAIM_LEVELS`), which shipped in wicked-vault 0.7.0;
+garden's floor is 0.8.0. An older vault is refused fail-closed — upgrade with
+`npm i -g wicked-vault@latest` (or set `WICKED_QE_VAULT_PKG` to point at a
+specific wicked-vault 0.8.0+ install). The `th17-vault-evidence` tests skip
+with that message when no 2.1-capable vault is resolvable.
 
 ## Tests
 

package/scripts/qe/runner/test/th17-vault-evidence.test.mjs

@@ -15,11 +15,11 @@
  *      refusal happens in code, not in docs.
  *
  * Release dependency (documented in vault-evidence.mjs): these tests need
- * the wicked-vault manifest-2.1 twin, which is on wicked-vault main but
- * UNRELEASED (npm 0.6.0 predates it). Until the next wicked-vault release,
- * set WICKED_QE_VAULT_PKG to a local checkout of wicked-vault main; without
- * one the vault-dependent tests SKIP with that exact message (the pure
- * mapping/capability tests still run).
+ * the wicked-vault manifest-2.1 twin (shipped in wicked-vault 0.7.0;
+ * garden's floor is 0.8.0). An older vault is refused fail-closed — upgrade
+ * with `npm i -g wicked-vault@latest` (or set WICKED_QE_VAULT_PKG to point
+ * at a specific 0.8.0+ install); without one the vault-dependent tests SKIP
+ * with that message (the pure mapping/capability tests still run).
  */
 
 import test from "node:test";
@@ -149,7 +149,7 @@ test("checkVaultCapability: a pre-2.1 vault is refused WITH the release requirem
   const r = checkVaultCapability(pre21);
   assert.equal(r.ok, false);
   assert.equal(r.pre21, true);
-  assert.match(r.reason, /UNRELEASED/);
+  assert.match(r.reason, /0\.8\.0/);
   assert.match(r.reason, /WICKED_QE_VAULT_PKG/);
   // and a non-vault module is a different refusal (not "release the vault")
   const notVault = checkVaultCapability({ record: fn });

package/skills/archetype/refs/incident.md

@@ -76,7 +76,7 @@ confirming the bleeding stopped. Don't skip to followup before resolve.
 2. **Confirm the bleeding stopped.** Watch the same dashboards that
    surfaced the incident. Don't declare mitigated based on logs alone.
 3. Record the mitigation as re-derivable evidence (vault present;
-   **wicked-vault ≥ 0.5.0** <!-- vault-floor -->):
+   **wicked-vault ≥ 0.8.0** <!-- vault-floor -->):
    `wicked-vault record --scope <scope> --phase incident --claim mitigation
    --kind mitigation-check --source "<the symptom-check command>"
    --criteria "symptom check passes post-mitigation"
@@ -106,7 +106,7 @@ confirming the bleeding stopped. Don't skip to followup before resolve.
 2. Use `wicked-garden-qe-incident-to-scenario-synthesizer` to convert the
    incident into a regression scenario that would catch the same break.
 3. Track action items in github. Don't bury them in a Slack thread.
-4. Record the docs evidence (vault present; **wicked-vault ≥ 0.5.0** <!-- vault-floor -->):
+4. Record the docs evidence (vault present; **wicked-vault ≥ 0.8.0** <!-- vault-floor -->):
    `wicked-vault record --scope <scope> --phase incident --claim rca
    --kind doc --artifact docs/postmortems/INC-{N}.md
    --criteria "required RCA sections present"

package/skills/archetype/refs/migrate.md

@@ -83,7 +83,7 @@ them mid-cutover. Absent? Discover it the usual way — and consider
    the old shape.
 3. Land + deploy expand. Don't combine with backfill.
 4. Record the **shape-change** as re-derivable evidence (vault present;
-   **wicked-vault ≥ 0.5.0** <!-- vault-floor -->):
+   **wicked-vault ≥ 0.8.0** <!-- vault-floor -->):
    `wicked-vault record --scope <scope> --phase migrate --claim shape-change
    --kind schema-state --source "<migration-applied verification>"
    --criteria "<the post-condition>" --verifier exit_code_eq:0

package/skills/archetype/refs/modernize.md

@@ -141,7 +141,7 @@ core's fail-closed build. See `skills/domain/SKILL.md`.
 2. Harden the result with `code-modernization:modernize-harden` (security/CVEs,
    error handling) before it carries traffic.
 3. Record the parity proof as re-derivable evidence (vault present; **wicked-vault
-   ≥ 0.5.0** <!-- vault-floor -->):
+   ≥ 0.8.0** <!-- vault-floor -->):
    `wicked-vault record --scope <scope> --phase modernize --claim parity-proof
    --kind differential --source "<the differential harness command>"
    --criteria "old(input) == new(input) on seeded data" --verifier exit_code_eq:0

package/skills/archetype/refs/review.md

@@ -121,7 +121,7 @@ in three domains").
 4. Append to the audit log with `wicked-garden run scripts/qe/verdict_audit.py append`
    so the verdict is replayable.
    Then record both produces as re-derivable evidence (vault present;
-   **wicked-vault ≥ 0.5.0** <!-- vault-floor -->):
+   **wicked-vault ≥ 0.8.0** <!-- vault-floor -->):
    `wicked-vault record --scope <scope> --phase review --claim verdict
    --kind verdict --source "<verdict.json>" --criteria "<the bar>"
    --verifier exit_code_eq:0 --actor "${WICKED_VAULT_ACTOR:-garden-prove}"

package/skills/archetype/refs/specify.md

@@ -62,7 +62,7 @@ proceed past validate without explicit user agreement on the AC set.
 4. Keep ACs minimal — 3–7 is the sweet spot. More than 10 means you're
    treating ACs as design.
 5. Record the AC artifact as re-derivable evidence (vault present;
-   **wicked-vault ≥ 0.5.0** <!-- vault-floor -->):
+   **wicked-vault ≥ 0.8.0** <!-- vault-floor -->):
    `wicked-vault record --scope <scope> --phase specify
    --claim smart-acceptance-criteria --kind spec-doc
    --artifact <path/to/requirements.md>

package/skills/core/refs/setup.md

@@ -97,7 +97,7 @@ npx wicked-vault --version 2>/dev/null || echo "MISSING"
 ```
 
 - `MISSING` → blocking. wicked-vault is the evidence backend every archetype gate re-derives against — without it, "done" can only be self-asserted. Show "wicked-vault is not installed. wicked-garden requires it as a direct infra peer (sibling to wicked-bus)." **INTERACTIVE mode**: native prompt header "wicked-vault Required", options "Install now (Required)" = "Run: npm i -g wicked-vault" / "Exit setup" = "Cancel — I'll install manually and re-run". **PLAIN_TEXT mode**: present numbered options and STOP. If install: run `npm i -g wicked-vault` (puts the `wicked-vault` binary on PATH) and confirm the CLI resolves with `npx wicked-vault --version`. On failure, show stderr and exit with manual instructions (`npm i -g wicked-vault`). If exit: "Run `npm i -g wicked-vault` then restart by invoking the wicked-garden-core skill's `setup` action."
-- Version string → compare it against the declared peer floor **≥ 0.5.0** <!-- vault-floor --> (single source: `scripts/loom/manifest.py` `version_pin`, lockstep with plugin.json `wicked_vault_version`). **Below the floor** (e.g. `0.4.5`) → tell the user to upgrade: "wicked-vault {version} is below the floor 0.5.0 — peer health checks (`loom doctor` / peer-health) report it as drift and fail. Upgrade: `npm i -g wicked-vault@latest`." At or above (e.g. `0.6.0`) → show "wicked-vault {version} — ready." Then verify the garden can resolve it for gating: `wicked-garden run scripts/qe/vault_gate.py resolve` should report `resolvable: true`. If `installed: false` (resolving only via npx), suggest `npm i -g wicked-vault` for faster gate latency — recommended, not a hard block.
+- Version string → compare it against the declared peer floor **≥ 0.8.0** <!-- vault-floor --> (single source: `scripts/loom/manifest.py` `version_pin`, lockstep with plugin.json `wicked_vault_version`). **Below the floor** (e.g. `0.7.0`) → tell the user to upgrade: "wicked-vault {version} is below the floor 0.8.0 — peer health checks (`loom doctor` / peer-health) report it as drift and fail. Upgrade: `npm i -g wicked-vault@latest`." At or above (e.g. `0.8.0`) → show "wicked-vault {version} — ready." Then verify the garden can resolve it for gating: `wicked-garden run scripts/qe/vault_gate.py resolve` should report `resolvable: true`. If `installed: false` (resolving only via npx), suggest `npm i -g wicked-vault` for faster gate latency — recommended, not a hard block.
 
 ### 2.7 Verify wicked-bus (Recommended — audit-trail layer)
 
@@ -304,7 +304,7 @@ wicked-garden is ready!
 Storage:         Local (DomainStore)
 wicked-estate:   {"ready (binary present)" or "MISSING — memory/context layer degraded"}
 wicked-bus:      {"ready (skills installed)" or "MISSING — install required"}
-wicked-vault:    {version e.g. "0.6.0 — ready" or "MISSING — install required" or "{version} — below the 0.5.0 floor, upgrade required"}
+wicked-vault:    {version e.g. "0.8.0 — ready" or "MISSING — install required" or "{version} — below the 0.8.0 floor, upgrade required"}
 loom engine:     {"ready (internal — scripts/loom/)" or "MISSING — garden installation problem"}
 Onboarding:      {Full | Quick scout | Skipped}
 Directories:     {paths onboarded}

package/skills/qe/refs/campaign-grading.md

@@ -216,10 +216,10 @@ wicked-garden run scripts/qe/lib/gate.mjs \
   ```
 
 - **Release dependency:** needs the wicked-vault **manifest-2.1 twin**
-  (`validateManifest` + `CLAIM_LEVELS`) — merged on wicked-vault main,
-  **unreleased** (npm 0.6.0 predates it). Until the next wicked-vault
-  release, set `WICKED_QE_VAULT_PKG` to a local checkout of wicked-vault
-  main; a pre-2.1 vault is refused fail-closed, never silently degraded.
+  (`validateManifest` + `CLAIM_LEVELS`), which shipped in wicked-vault 0.7.0;
+  garden's floor is **0.8.0**. An older vault is refused fail-closed, never
+  silently degraded — upgrade with `npm i -g wicked-vault@latest` (or set
+  `WICKED_QE_VAULT_PKG` to point at a specific 0.8.0+ install).
 
 ## Wiring context
 

package/skills/qe/refs/evidence.md

@@ -279,7 +279,7 @@ Rules, all fail-closed:
 3. **Grades are opinions, not re-derivable facts**: `attest` appends, never
    edits; the vault refuses a self-grade (evaluator = recording actor) and
    a grade over a tampered artifact.
-4. **Release dependency**: needs the wicked-vault manifest-2.1 twin —
-   on wicked-vault main, **unreleased** (npm 0.6.0 predates it). Until the
-   next wicked-vault release, set `WICKED_QE_VAULT_PKG` to a local checkout
-   of wicked-vault main; a pre-2.1 vault is refused with that message.
+4. **Release dependency**: needs the wicked-vault manifest-2.1 twin
+   (shipped in wicked-vault 0.7.0; garden's floor is **0.8.0**). An older
+   vault is refused fail-closed — upgrade with `npm i -g wicked-vault@latest`
+   (or set `WICKED_QE_VAULT_PKG` to point at a specific 0.8.0+ install).

package/uv.lock

@@ -1,6 +1,6 @@
 version = 1
 revision = 3
-requires-python = ">=3.10"
+requires-python = ">=3.10, <3.15"
 
 [[package]]
 name = "aiofiles"