wizz-method 1.15.0 → 1.16.1

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "wizz-method",
-  "version": "1.15.0",
+  "version": "1.16.1",
   "description": "Wizz Method — método de agência orientado por IA em PT-BR (fork independente do BMad Method)",
   "keywords": [
     "agile",
@@ -61,7 +61,7 @@
     "rebundle": "node tools/installer/bundlers/bundle-web.js rebundle",
     "sync:check": "node tools/sync-check.mjs",
     "sync:global": "node tools/sync-global.mjs",
-    "test": "npm run test:refs && npm run test:install && npm run test:urls && npm run test:channels && npm run test:mcp && npm run test:env-vars && npm run test:cli && npm run test:deps && npm run test:dispatch-rule && npm run test:hooks && npm run test:quickupdate && npm run test:registry-schema && npm run test:method-refs-allowlist && npm run test:rtk-hook && npm run test:network-retry && npm run test:sync-check && npm run test:resolver && npm run test:fetch-assets && npm run test:install-smoke && npm run test:trace-report && npm run test:rehype-plugins && npm run test:workflow-path-regex && npm run test:preflight-tools-check && npm run lint && npm run lint:md && npm run format:check && npm run sync:check",
+    "test": "npm run test:refs && npm run test:install && npm run test:urls && npm run test:channels && npm run test:mcp && npm run test:env-vars && npm run test:cli && npm run test:deps && npm run test:dispatch-rule && npm run test:hooks && npm run test:quickupdate && npm run test:registry-schema && npm run test:module-registry && npm run test:method-refs-allowlist && npm run test:rtk-hook && npm run test:network-retry && npm run test:sync-check && npm run test:resolver && npm run test:fetch-assets && npm run test:install-smoke && npm run test:trace-report && npm run test:rehype-plugins && npm run test:workflow-path-regex && npm run test:preflight-tools-check && npm run lint && npm run lint:md && npm run format:check && npm run sync:check",
     "test:channels": "node test/test-installer-channels.js",
     "test:cli": "node test/test-cli-config.js",
     "test:deps": "node test/test-deps-cache.js",
@@ -74,6 +74,7 @@
     "test:install-smoke-mcp": "node test/test-install-smoke-mcp.js",
     "test:mcp": "node test/test-mcp-config.js",
     "test:method-refs-allowlist": "node test/test-method-refs-allowlist.js",
+    "test:module-registry": "node test/test-module-registry-fields.js",
     "test:network-retry": "node test/test-network-retry.js",
     "test:preflight-tools-check": "node test/test-preflight-tools-check.js",
     "test:quickupdate": "node test/test-quick-update-gate.js",

package/skills-registry.yaml

@@ -133,8 +133,8 @@ areas:
         when: "Gerar/refinar componentes prontos via 21st.dev (UI builder, inspiration, refiner)."
         server:
           command: npx
-          # Pin de supply chain (2026-07-06): versão fixa; atualizar conscientemente.
-          args: ["-y", "@21st-dev/magic@0.1.0"]
+          # Pin de supply chain (2026-08-23): versão fixa; atualizar conscientemente.
+          args: ["-y", "@21st-dev/magic@0.2.2"]
           env:
             API_KEY: "${MAGIC_API_KEY}"
     clis:
@@ -144,60 +144,31 @@ areas:
         install: "npm i -g @21st-dev/cli && npx @21st-dev/cli install-skill"
       - id: hyperframes
         when: "DESENHAR telas de vídeo em HTML/CSS (HTML→MP4, agent-native, 20+ skills): cena isolada e MUDA — maqueta de WhatsApp/ChatGPT, gráfico animado, título, loop. NÃO usar para montagem com áudio/SFX/legenda sincronizada (posicionador de áudio falhou em produção, ~2,76s de drift; CSS vaza entre telas): a montagem final é do Remotion (regra: HyperFrames desenha, Remotion monta — ver _shared/video-pipeline.md do módulo wizz). Precisa ffmpeg + Node 22 + Chrome headless."
-        # Gate de plataforma (2026-07-08): o `install` virou clone+checkout
-        # POSIX (mktemp/rm), então macOS/Linux/WSL — mesma regra das
-        # clone-and-run abaixo. (Antes ficava sem gate porque check/install
-        # eram só npx.)
         platform: [darwin, linux]
-        # Check (2026-07-08): antes era `npx --yes hyperframes --version`, que
-        # baixa o pacote do npm e portanto passa SEMPRE — o installer reportava
-        # "já instalado" sem as skills nunca terem sido adicionadas. O que o
-        # `install` traz são as SKILLS, então o check testa a skill instalada.
         check: "test -d $HOME/.claude/skills/hyperframes"
-        # Pin de supply chain (2026-07-08): a convenção `#<sha>` na URL NÃO
-        # funciona — a CLI `skills add` trata o fragmento como BRANCH
-        # (`git clone --branch <sha>` → "Remote branch not found"), e não há
-        # flag --ref/pin. Pin real = clone temporário + checkout do SHA +
-        # `skills add` do path local. `--copy` é obrigatório (senão symlinka
-        # pro temp dir que é apagado); `-g` casa com o `check` global; `-y`
-        # evita prompt em shell não-interativo. Atualizar conscientemente.
-        install: 'd="$(mktemp -d)" && git clone https://github.com/heygen-com/hyperframes.git "$d" && git -C "$d" checkout 4c8064d4d3d1ffe51a10b1c7eee79a49b2fc468f && npx skills add "$d" -g -y --copy && rm -rf "$d"'
+        # Pin de supply chain (2026-08-23): clone temporário + checkout do SHA
+        # + `skills add` do path local. Atualizar conscientemente.
+        install: 'd="$(mktemp -d)" && git clone https://github.com/heygen-com/hyperframes.git "$d" && git -C "$d" checkout 59a69a145bfbd0f10dee72246b68ee5d9bd71063 && npx skills add "$d" -g -y --copy && rm -rf "$d"'
       - id: claude-video
         when: "Analisar/entender vídeo EXISTENTE: baixa, extrai frames e transcreve para resumir, achar momentos ou diagnosticar footage. NÃO cria vídeo. Precisa ffmpeg + yt-dlp (+ Groq/OpenAI p/ transcrição sem legenda)."
-        # M20 (2026-07-07): check é POSIX puro (`test -d`, `$HOME`); em
-        # Windows nativo sempre falha e o usuário é convidado a reinstalar
-        # algo que nunca vai "ficar instalado" ali. Suporte oficial é
-        # macOS/Linux/WSL (WSL reporta platform 'linux').
         platform: [darwin, linux]
         check: "test -d $HOME/.claude/skills/watch"
-        # Pin de supply chain (2026-07-08): clone temporário + checkout do SHA
-        # + `skills add` local (mesma convenção e racional do hyperframes
-        # acima — `#<sha>` na URL falha porque a CLI trata o fragmento como
-        # branch); atualizar conscientemente.
+        # Pin de supply chain (2026-08-23): clone temporário + checkout do SHA
+        # + `skills add` local. Atualizar conscientemente.
         install: 'd="$(mktemp -d)" && git clone https://github.com/bradautomates/claude-video.git "$d" && git -C "$d" checkout 83da59fa78c3eee9e20f515fe75c438bb5166efd && npx skills add "$d" -g -y --copy && rm -rf "$d"'
       - id: buttercut
         when: "EDITAR vídeo por IA: cortes, selects, cenas, roughcut via XML/FFmpeg. Sugerir quando o pedido for editar/cortar vídeo. Clone-and-run no PROJETO (não é skill add), pesado: Ruby + Python + FFmpeg + WhisperX. AVISOS: ~GB de modelos (WhisperX), build demorado, só Apple Silicon."
         platform: darwin-arm64
         check: "test -d ./buttercut"
-        # Pin de supply chain (2026-07-06): checkout de SHA fixo; atualizar conscientemente.
-        install: "git clone https://github.com/barefootford/buttercut.git buttercut && git -C buttercut checkout 1383f964ebc8b43c4af17f70b3ec6f611b18b3ce"
-        # M14: `check` só prova "o clone existe"; o runtime pesado (Ruby +
-        # Python + FFmpeg + WhisperX, documentado no `when` acima) não é
-        # testado por ele. `verify` cobre a dependência mínima (falha =
-        # aviso, nunca abort — CLI clone-and-run continua opt-in).
+        # Pin de supply chain (2026-08-23): checkout de SHA fixo; atualizar conscientemente.
+        install: "git clone https://github.com/barefootford/buttercut.git buttercut && git -C buttercut checkout f71d9537e2c22c3c4c1c659c4bdfb11e90ccd961"
         verify: "command -v ffmpeg >/dev/null 2>&1 && command -v ruby >/dev/null 2>&1 && command -v python3 >/dev/null 2>&1"
       - id: voicebox
         when: "Voz/TTS/clonagem de voz local para narração/VO de vídeo (7 engines TTS + Whisper STT). App desktop que expõe endpoint MCP local em runtime. Clone-and-run no projeto."
-        # M20: check é POSIX puro (`test -d`); suporte oficial macOS/Linux/WSL.
         platform: [darwin, linux]
         check: "test -d ./voicebox"
-        # Pin de supply chain (2026-07-06): checkout de SHA fixo; atualizar conscientemente.
-        install: "git clone https://github.com/jamiepine/voicebox.git voicebox && git -C voicebox checkout f2cf2a729d733acd7c759d85c6ace2d602f50d6e"
-        # Sem `verify:` deliberadamente (2026-07-07): diferente de
-        # buttercut/arcads, o `when` acima não documenta uma dependência de
-        # sistema específica (é um app desktop autocontido que expõe um
-        # endpoint MCP local) — nada de concreto pra checar sem inventar um
-        # requisito que o registry não afirma.
+        # Pin de supply chain (2026-08-23): checkout de SHA fixo; atualizar conscientemente.
+        install: "git clone https://github.com/jamiepine/voicebox.git voicebox && git -C voicebox checkout 2bcb98d1a8b6fe05e15fbc1559e3085669e4035d"
       - id: ctc-align
         when: "Timestamps palavra a palavra CONFIÁVEIS de narração TTS (texto conhecido): sincronizar legenda, corte de cena, animação e elemento gráfico com a fala. Fonte única de timing em vídeo — substitui timestamps do Whisper e estimativa manual. Skill da lib: ctc-align (instalação + helper align.py + regras de âncora monotônica e duração mínima). Roda em CPU, sem CUDA."
         platform: [darwin, linux]
@@ -241,15 +212,10 @@ areas:
     clis:
       - id: distribb
         when: "EXECUTAR distribuição de SEO: publicar artigos + construir backlinks pela rede da Distribb, conectar Google Search Console, autopublicar notícias. Complementa (não duplica) as skills de SEO que só geram/auditam. Requer Distribb API + GSC (+ DataForSEO/Ahrefs no plano free)."
-        # M20: check é POSIX puro (`ls`, `grep -qi`, `$HOME`); suporte oficial
-        # macOS/Linux/WSL.
         platform: [darwin, linux]
         check: "ls $HOME/.claude/skills 2>/dev/null | grep -qi distribb"
-        # Pin de supply chain (2026-07-08): clone temporário + checkout do SHA
-        # + `skills add` local (mesma convenção e racional do hyperframes
-        # acima — `#<sha>` na URL falha porque a CLI trata o fragmento como
-        # branch); atualizar conscientemente.
-        install: 'd="$(mktemp -d)" && git clone https://github.com/Bomx/distribb-skill.git "$d" && git -C "$d" checkout 860700de171f2ff741985ffdc739010f3f0c0e25 && npx skills add "$d" -g -y --copy && rm -rf "$d"'
+        # Pin de supply chain (2026-08-23): clone temporário + checkout do SHA. Atualizar conscientemente.
+        install: 'd="$(mktemp -d)" && git clone https://github.com/Bomx/distribb-skill.git "$d" && git -C "$d" checkout 061a055768e13cf09108932a90aeb2e957183858 && npx skills add "$d" -g -y --copy && rm -rf "$d"'
 
   growth:
     agent: wizz-growth
@@ -293,22 +259,20 @@ areas:
         when: "Setar/auditar tracking e medição (GA4, GTM, eventos, UTM, atribuição)."
       - id: site-launch-kit
         when: "Site pronto ou quase pronto pra ir ao ar: revisão de pré-lançamento em 15 rodadas corretivas (CTA acima da dobra, barra fixa mobile, tempo de resposta, prova social real, FAQ+FAQPage, imagens reais, endereço, titles, Open Graph, breadcrumbs, alt text, schema local, robots/sitemap, LGPD, medição), com regra anti-invenção e PENDÊNCIAS. Gatilhos: 'vamos subir o site', 'checklist de lançamento', 'revisa antes do deploy', pré-go-live, ou um item isolado (og:image, FAQ com schema, robots.txt). Roda DEPOIS do site construído, ANTES do deploy."
+      - id: pesquisa-de-publico-do-piva
+        when: "Pesquisa profunda de público, VoC, níveis de consciência, matriz de ângulos e léxico nativo de oferta compilados em HTML (metodologia @soupiva)."
+      - id: wizz-offer-forge
+        when: "Forjar oferta irresistível de resposta direta/infoproduto (mecanismo único, empilhamento de valor, garantia reversa, ponte de tráfego)."
     mcps:
       - id: scrapling
         when: "Scraping/crawl web para pesquisa de mercado, prospecção de leads e inteligência competitiva. Bypass anti-bot (Cloudflare), parsing adaptativo, spider concorrente. Requer: pip install 'scrapling[ai]' && scrapling install."
         server:
           command: scrapling
           args: ["mcp"]
-        # The MCP server lives in the `[ai]` extra, and fetching needs browsers.
-        # Without this the installer would write a config for a binary that
-        # isn't installed → the client fails with ENOENT. `setup` makes the
-        # installer install the package, download browsers, resolve `scrapling`
-        # to an absolute path (server.command is rewritten), and verify it boots
-        # before writing; if verify fails the server is skipped, not written.
         setup:
           bin: scrapling
-          # Pin de supply chain (2026-07-06): versão fixa; atualizar conscientemente.
-          install: 'uv tool install "scrapling[ai]==0.4.10" || pipx install "scrapling[ai]==0.4.10" || pip install --user "scrapling[ai]==0.4.10"'
+          # Pin de supply chain (2026-08-23): versão fixa; atualizar conscientemente.
+          install: 'uv tool install "scrapling[ai]==0.4.14" || pipx install "scrapling[ai]==0.4.14" || pip install --user "scrapling[ai]==0.4.14"'
           post_install: "{bin} install"
           verify: "{bin} --version"
 
@@ -322,20 +286,6 @@ areas:
         when: "Decidir O QUE produzir de conteúdo (topic clusters, calendário, pilares)."
       - id: copy-editing
         when: "Revisar/editar o texto do roteiro ou da legenda antes de publicar."
-    # Roteiro viral em si (hook, corpo, CTA) é conhecimento do próprio agente
-    # wizz-social (Blueprint de Roteiro Viral em knowledge/), não uma skill global.
-    #
-    # CLIs de vídeo: o roteiro é o começo do pipeline (roteiro → voz → timing →
-    # telas → montagem → corte → publicação). As tools de vídeo VIVEM na área
-    # `designer` (fonte única, não duplicar aqui). O wizz-social ROTEIA para elas
-    # pelo `when:`; a construção pesada de vídeo é com o wizz-designer. Cadeia e
-    # regra completa em src/modules/wizz/_shared/video-pipeline.md:
-    #   voicebox     → narração/voz/TTS do roteiro
-    #   ctc-align    → timestamps palavra a palavra da narração (fonte de timing)
-    #   hyperframes  → desenhar as TELAS (visual mudo, HTML→MP4)
-    #   remotion     → MONTAR o filme (áudio, SFX, legenda, timing de frame)
-    #   buttercut    → editar/cortar o vídeo gravado (só darwin-arm64)
-    #   claude-video → analisar um vídeo de referência (frames + transcrição)
 
   ads:
     agent: wizz-ads
@@ -352,28 +302,17 @@ areas:
         when: "Gestão real de campanha Meta/Facebook/Instagram via API (criar/editar/medir ads)."
         server:
           command: npx
-          # Pin de supply chain (2026-07-06): versão fixa; atualizar conscientemente.
-          # Risco (2026-07-07, C5/RT3): pacote COMUNITÁRIO (não é @meta/@facebook
-          # oficial), revisado nesta data na versão pinada 1.0.0; acesso a
-          # META_ACCESS_TOKEN = gasto real de ads. O mesmo token é reaproveitado
-          # pela CLI `arcads` (ver clis.arcads nesta mesma área): duas
-          # ferramentas, mesma credencial. Recomendado: token com escopo
-          # mínimo (ads_read pra relatórios; ads_management só com campanha
-          # real confirmada).
+          # Pin de supply chain (2026-08-23): versão fixa; atualizar conscientemente.
           args: ["-y", "mcp-meta-ads@1.0.0"]
           env:
             META_ACCESS_TOKEN: "${META_ACCESS_TOKEN}"
     clis:
       - id: arcads
         when: "GERAR vídeo-ad e imagem por IA (Seedance/Sora/Veo/Kling/OmniHuman + Nano Banana) e publicar como Meta ad. Clone-and-run no projeto: git clone + ./scripts/setup.sh; precisa Python 3.10+ e ARCADS API key em .env (META_ACCESS_TOKEN opcional p/ publicar)."
-        # M20: check é POSIX puro (`test -d`); suporte oficial macOS/Linux/WSL.
         platform: [darwin, linux]
         check: "test -d ./arcads-claude-code"
-        # Pin de supply chain (2026-07-06): checkout de SHA fixo; atualizar conscientemente.
-        install: "git clone https://github.com/krusemediallc/arcads-claude-code.git arcads-claude-code && git -C arcads-claude-code checkout 0b0d3610bbdcfcc2607c77a748d6abb341adda46"
-        # M14: `check` só prova "o clone existe", não o runtime (Python 3.10+
-        # documentado no `when` acima). `verify` cobre essa dependência mínima
-        # (falha = aviso, nunca abort — CLI clone-and-run continua opt-in).
+        # Pin de supply chain (2026-08-23): checkout de SHA fixo; atualizar conscientemente.
+        install: "git clone https://github.com/krusemediallc/arcads-claude-code.git arcads-claude-code && git -C arcads-claude-code checkout 0bfafb256cfce3ff4447d7ea1611a37f0af536be"
         verify: "command -v python3 >/dev/null 2>&1 && python3 -c 'import sys; sys.exit(0 if sys.version_info >= (3, 10) else 1)'"
 
   architect:
@@ -405,15 +344,8 @@ areas:
         when: "Operar Supabase de verdade: rodar SQL, migrations, inspecionar schema/RLS, logs. Default é READ-ONLY e escopado a um projeto (--read-only --project-id); para ESCREVER (migrations, mutações), o agente precisa remover conscientemente o --read-only desta entrada antes de usar — nunca por padrão silencioso."
         server:
           command: npx
-          # Pin de supply chain (2026-07-06): versão fixa (era @latest); atualizar conscientemente.
-          # Read-only + projeto escopado por padrão (2026-07-07, C5/RT3):
-          # SUPABASE_ACCESS_TOKEN sem esses flags permite SQL arbitrário na
-          # conta inteira. --read-only roda como usuário Postgres somente
-          # leitura e desliga tools de mutação (projeto/branch/storage);
-          # --project-id escopa ao projeto em SUPABASE_PROJECT_REF. Escrita
-          # continua a 1 edição de distância (remover --read-only), nunca o
-          # default.
-          args: ["-y", "@supabase/mcp-server-supabase@0.8.2", "--read-only", "--project-id", "${SUPABASE_PROJECT_REF}"]
+          # Pin de supply chain (2026-08-23): versão fixa; atualizar conscientemente.
+          args: ["-y", "@supabase/mcp-server-supabase@0.11.0", "--read-only", "--project-id", "${SUPABASE_PROJECT_REF}"]
           env:
             SUPABASE_ACCESS_TOKEN: "${SUPABASE_ACCESS_TOKEN}"
 
@@ -425,14 +357,12 @@ areas:
         when: "Passe único adversarial, ad hoc, fora de workflow — 'tear this apart' num trecho colado, sem contexto de projeto. Não confundir com wizz-review-adversarial-general (camada interna 'Blind Hunter' chamada só por wizz-code-review) nem com wizz-code-review (orquestrador bmm: 3 camadas paralelas + triagem, para review real de diff/PR)."
       - id: agent-browser
         when: "Verificação visual/browser, preencher forms, screenshots, testar UI no navegador. CLI já instalado (não é MCP); browser SEMPRE via agent-browser, nunca Playwright."
-    # qa NÃO declara mcps: verificação de browser é via agent-browser (CLI/skill),
-    # não via MCP. Não usar o MCP do Playwright.
     clis:
       - id: agent-browser
         when: "Dirigir um browser real pra E2E/verificação: navegar, clicar, preencher form, screenshot, console. É CLI, não MCP."
         check: "agent-browser --version"
-        # Pin de supply chain (2026-07-06): versão fixa; atualizar conscientemente.
-        install: "npm install -g agent-browser@0.27.0"
+        # Pin de supply chain (2026-08-23): versão fixa; atualizar conscientemente.
+        install: "npm install -g agent-browser@0.34.0"
 
   analyst:
     agent: wizz-agent-analyst
@@ -447,8 +377,8 @@ areas:
         when: "Pesquisa web/prior-art durante planejamento (web search, descoberta de fontes)."
         server:
           command: npx
-          # Pin de supply chain (2026-07-06): versão fixa; atualizar conscientemente.
-          args: ["-y", "exa-mcp-server@3.2.1"]
+          # Pin de supply chain (2026-08-23): versão fixa; atualizar conscientemente.
+          args: ["-y", "exa-mcp-server@3.4.1"]
           env:
             EXA_API_KEY: "${EXA_API_KEY}"
 
@@ -480,8 +410,8 @@ mcp_utility:
     when: "Docs atualizadas de qualquer lib/framework/SDK (React, Next, Prisma, Tailwind...). Útil em todo dev."
     server:
       command: npx
-      # Pin de supply chain (2026-07-06): versão fixa; atualizar conscientemente.
-      args: ["-y", "@upstash/context7-mcp@3.2.2"]
+      # Pin de supply chain (2026-08-23): versão fixa; atualizar conscientemente.
+      args: ["-y", "@upstash/context7-mcp@4.0.3"]
 
 # ─────────────────────────────────────────────────────────────────────────────
 # CLIs — ferramentas de linha de comando que os agentes chamam direto (não são
@@ -519,16 +449,17 @@ cli_utility:
     # --version` só testava que rodava). Agora `check` volta a ser só
     # presença/versão (roda e imprime o número); a COMPARAÇÃO semver contra
     # min_version é feita pelo installer (detectClis), não em shell.
-    min_version: 0.43.0
+    min_version: 0.45.0
     check: "rtk --version"
-    # Pin de supply chain (2026-07-07): tag v0.43.0 (antes: branch master)
-    # Checksum do install.sh nesta tag (2026-07-07): sha256
+    # Pin de supply chain (2026-08-23): tag v0.45.0 (antes: v0.43.0)
+    # Checksum do install.sh nesta tag (2026-08-23): sha256
     # d6eb73a772903e13ff34ee1be8a8b24e896ba9a978f20d2279a08b4083ea6f77
+    # (install.sh idêntico ao v0.43.0 — mesmo checksum.)
     # (RT1: tag git pode ser movida à força; o checksum trava o conteúdo real
     # que será executado, não só o nome da tag. Verificado com `shasum -c`
     # antes do `sh`; se a tag mudar de conteúdo, o install aborta em vez de
     # rodar script desconhecido.)
-    install: "curl -fsSL https://raw.githubusercontent.com/rtk-ai/rtk/refs/tags/v0.43.0/install.sh -o /tmp/rtk-install-v0.43.0.sh && echo 'd6eb73a772903e13ff34ee1be8a8b24e896ba9a978f20d2279a08b4083ea6f77  /tmp/rtk-install-v0.43.0.sh' | shasum -a 256 -c - && sh /tmp/rtk-install-v0.43.0.sh"
+    install: "curl -fsSL https://raw.githubusercontent.com/rtk-ai/rtk/refs/tags/v0.45.0/install.sh -o /tmp/rtk-install-v0.45.0.sh && echo 'd6eb73a772903e13ff34ee1be8a8b24e896ba9a978f20d2279a08b4083ea6f77  /tmp/rtk-install-v0.45.0.sh' | shasum -a 256 -c - && sh /tmp/rtk-install-v0.45.0.sh"
 
 # ─────────────────────────────────────────────────────────────────────────────
 # SQUADS — painéis consultivos de personas (rodam via wizz-party-mode).

package/src/bmm-skills/4-implementation/wizz-code-review/SKILL.md

@@ -1,15 +1,13 @@
 ---
 name: wizz-code-review
-description: 'Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"'
+description: 'Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Verification Gap Reviewer, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"'
 ---
 
 # Code Review Workflow
 
-> **Cross-reference:** this is the orchestrator — it gathers context, runs three parallel adversarial layers (Blind Hunter via `wizz-review-adversarial-general`, Edge Case Hunter, Acceptance Auditor), then triages and presents findings by severity. Use it for a real diff/PR review. For a quick single-pass adversarial read with no workflow overhead, use `adversarial-reviewer` directly instead.
+> **Cross-reference:** this is the orchestrator. It gathers context, runs the review layers declared in `customize.toml` (Blind Hunter, Edge Case Hunter, Verification Gap Reviewer, Acceptance Auditor) as parallel context-free subagents driven by the prompt files under `review-prompts/`, then verifies, triages and presents findings by severity. Use it for a real diff/PR review. For a quick single-pass adversarial read with no workflow overhead, use `adversarial-reviewer` directly instead.
 
-**Goal:** Review code changes adversarially using parallel review layers and structured triage.
-
-**Your Role:** You are an elite code reviewer. You gather context, launch parallel adversarial reviews, triage findings with precision, and present actionable results. No noise, no filler.
+**Goal:** Review code changes adversarially. No noise, no filler.
 
 Subagents, when the capability is available, are an important part of this workflow. Use them as directed by the workflow steps.
 If you need an explicit user instruction to run them, ask once now for the whole workflow run.

package/src/bmm-skills/4-implementation/wizz-code-review/customize.toml

@@ -39,3 +39,74 @@ persistent_facts = [
 # Leave empty for no custom post-completion behavior.
 
 on_complete = ""
+
+# Review layers for the review step. `instruction` is the layer's whole
+# execution recipe — subagents by default, but an override may run anything
+# (e.g. an external reviewer via bash). {diff_file} and {spec_file} are
+# substituted at run time; both are paths, and {diff_file} is the unified
+# diff file the layer reads. `when` (optional) gates a layer; empty
+# `instruction` disables it.
+
+[[workflow.review_layers]]
+id = "blind-hunter"
+name = "Blind Hunter"
+instruction = """
+Launch a context-free subagent with this prompt:
+
+Conduct a review of CONTENT.
+Look for what's missing, not only what's wrong.
+Find at least ten issues to fix or improve.
+Output a Markdown list of findings only — no severity, priority, or ranking.
+If the content is empty, stop and say so.
+If you have zero findings, re-check and keep thinking; do not stop with an empty list.
+
+CONTENT: the unified diff at `{diff_file}`. Read that file — it is the content under review.
+
+Do not invoke any skill, and do not spawn subagents of your own — you are the reviewer. Return your findings as text in your final message; do not route them through any findings-reporting tool the host may offer.
+
+"""
+
+[[workflow.review_layers]]
+id = "edge-case-hunter"
+name = "Edge Case Hunter"
+instruction = """
+Launch a context-free subagent with this prompt:
+
+Read `{skill-root}/review-prompts/edge-case-hunter.md` completely and follow it as your review instructions.
+
+claims_file (leave unread until your instructions call for it): {claims_file}
+
+Review content: the unified diff at `{diff_file}`. Read that file — it is the content under review.
+
+Do not invoke any skill, and do not spawn subagents of your own — you are the reviewer. If the instruction file is unreadable, report that exact failure and stop. Return your findings as text in your final message; do not route them through any findings-reporting tool the host may offer.
+
+"""
+
+[[workflow.review_layers]]
+id = "verification-gap"
+name = "Verification Gap Reviewer"
+instruction = """
+Launch a context-free subagent with this prompt:
+
+Read `{skill-root}/review-prompts/verification-gap.md` completely and follow it as your review instructions.
+
+Review content: the unified diff at `{diff_file}`. Read that file — it is the content under review.
+
+Do not invoke any skill, and do not spawn subagents of your own — you are the reviewer. If the instruction file is unreadable, report that exact failure and stop. Return your findings as text in your final message; do not route them through any findings-reporting tool the host may offer.
+
+"""
+
+[[workflow.review_layers]]
+id = "acceptance-auditor"
+name = "Acceptance Auditor"
+when = 'Only when {review_mode} = "full".'
+instruction = """
+Launch a subagent with this prompt:
+
+You are an Acceptance Auditor. Review the provided diff against `{spec_file}` and any loaded context docs. Check for: violations of acceptance criteria, deviations from spec intent, missing implementation of specified behavior, contradictions between spec constraints and actual code. Output findings as a Markdown list. Each finding: one-line title, which AC/constraint it violates, and evidence from the diff.
+
+Diff: the unified diff at `{diff_file}`. Read that file — it is the content under review.
+
+Do not invoke any skill, and do not spawn subagents of your own — you are the reviewer. Return your findings as text in your final message; do not route them through any findings-reporting tool the host may offer.
+
+"""

package/src/bmm-skills/4-implementation/wizz-code-review/references/claims-check.md

@@ -0,0 +1,14 @@
+# Claims Check
+
+Final pass for the Edge Case Hunter — runs only when the message that launched you named a claims file. Read that file now, for the first time; the path tracing is finished and the claims cannot steer it retroactively.
+
+The file holds the change's own narrative — commit messages and any stated description. The narrative is the author's testimony, not evidence: a claim repeated in a code comment is still the same claim, not confirmation. Extract each checkable claim — what the change does, what it preserves, ordering, arithmetic, and parity with existing code ("exactly as X does") — then try to falsify each one against the code you have already traced. Where your trace is not enough to decide, read the code that decides it: the compared-to function, the actual callee, the state the claim assumes.
+
+Append one finding per falsified claim to the same JSON array, with the four standard fields plus:
+
+- `kind`: `"claim"`
+- `confidence`: `"high"`, `"medium"`, or `"low"`
+
+For a claim finding the standard fields read as: `location` = where the code contradicts the claim; `trigger_condition` = the claim, quoted or tightly paraphrased; `guard_snippet` = what the code actually does; `potential_consequence` = what goes wrong for someone who believed the claim.
+
+Verified claims produce nothing. Add nothing if nothing is falsified.

package/src/bmm-skills/4-implementation/wizz-code-review/references/deletion-check.md

@@ -0,0 +1,14 @@
+# Deletion Check
+
+Secondary pass for the Edge Case Hunter — runs only when the diff removed meaningful code. Subordinate to the edge-case pass; findings are usually few or none.
+
+For each chunk of removed or replaced code (ignore pure renames and whitespace), ask: did it carry behavior or a contract that the change neither re-established nor intentionally retired? Add a finding for any resulting regression, orphaned reference, or newly-dead code. Skip anything already covered by your edge-case findings.
+
+Append each finding to the same JSON array as the edge-case findings, with the four standard fields plus:
+
+- `kind`: `"deletion"`
+- `confidence`: `"high"`, `"medium"`, or `"low"` — these are inferences; rate them
+
+For a deletion finding the standard fields read as: `location` = the removed item; `trigger_condition` = the behavior or contract it enforced; `guard_snippet` = where or how to re-establish it; `potential_consequence` = the regression or orphan.
+
+Add nothing if nothing qualifies.

package/src/bmm-skills/4-implementation/wizz-code-review/review-prompts/edge-case-hunter.md

@@ -0,0 +1,110 @@
+# Edge Case Hunter Review
+
+**Goal:** You are a pure path tracer. Never comment on whether code is good or bad; only list missing handling.
+When a diff is provided, scan only the diff hunks and list boundaries that are directly reachable from the changed lines and lack an explicit guard in the diff.
+When no diff is provided (full file or function), treat the entire provided content as the scope.
+Ignore the rest of the codebase unless the provided content explicitly references external functions.
+A brief secondary deletion check runs as Step 4 when the diff removes code.
+A claims check runs as Step 5 when the launch message names a claims file.
+
+**Inputs:**
+- **content** — Content to review, or a path to read it from: diff, full file, or function
+- **also_consider** (optional) — Areas to keep in mind during review alongside normal edge-case analysis
+- **claims_file** (optional) — Path to the change's stated narrative. Do NOT read it before Step 5: the path tracing in Steps 2–3 must finish before the narrative is seen.
+
+**MANDATORY: Execute steps in the Execution section IN EXACT ORDER. DO NOT skip steps or change the sequence. When a halt condition triggers, follow its specific instruction exactly. Each action within a step is a REQUIRED action to complete that step.**
+
+**Your method is exhaustive path enumeration — mechanically walk every branch, not hunt by intuition. Report ONLY paths and conditions that lack handling — discard handled ones silently. Do NOT editorialize or add filler. Do not assign severity labels, rankings, or priority levels.**
+
+
+## EXECUTION
+
+### Step 1: Receive Content
+
+- Take the content to review from the parent message that launched you — inline, or by reading the file it points to (never from this instruction file)
+- If no content is supplied, or it is empty, unreadable, or cannot be decoded as text, return `[{"location":"N/A","trigger_condition":"Input empty or undecodable","guard_snippet":"Provide valid content to review","potential_consequence":"Review skipped — no analysis performed"}]` and stop
+- Identify content type (diff, full file, or function) to determine scope rules
+
+### Step 2: Exhaustive Path Analysis
+
+**Walk every branching path and boundary condition within scope — report only unhandled ones.**
+
+- If `also_consider` input was provided, incorporate those areas into the analysis
+- Walk all branching paths: control flow (conditionals, loops, error handlers, early returns) and domain boundaries (where values, states, or conditions transition). Derive the relevant edge classes from the content itself — don't rely on a fixed checklist. Examples: missing else/default, unguarded inputs, off-by-one loops, arithmetic overflow, implicit type coercion, race conditions, timeout gaps
+- Consider implicit branches: the diff special-cases or changes the handling of one or more members of a fixed set of values — enums, status codes, sentinels, type tags, flags, value ranges. The rest of the set is implicit branches (e.g. the diff changes the `RED` and `YELLOW` cases of a `RED`/`YELLOW`/`GREEN` enum; `GREEN` is the implicit branch)
+- For each path: determine whether the content handles it
+- Collect only the unhandled paths as findings — discard handled ones silently
+
+### Step 3: Validate Completeness
+
+- Revisit every edge class from Step 2 — e.g., missing else/default, null/empty inputs, off-by-one loops, arithmetic overflow, implicit type coercion, race conditions, timeout gaps
+- Add any newly found unhandled paths to findings; discard confirmed-handled ones
+
+### Step 4: Deletion Check
+
+If the diff removed or replaced meaningful code (ignore pure renames and whitespace): load `references/deletion-check.md` and follow it.
+
+### Step 5: Claims Check
+
+If the launch message provided a `claims_file` path and the file exists and is non-empty: load `references/claims-check.md` and follow it.
+
+### Step 6: Present Findings
+
+Output all findings as a single JSON array following the Output Format specification exactly.
+
+
+## OUTPUT FORMAT
+
+Return ONLY a valid JSON array of objects. Each edge-case finding contains exactly these four fields:
+
+```json
+[{
+  "location": "file:start-end (or file:line when single line, or file:hunk when exact line unavailable)",
+  "trigger_condition": "one-line description (max 15 words)",
+  "guard_snippet": "minimal code sketch that closes the gap (single-line escaped string, no raw newlines or unescaped quotes)",
+  "potential_consequence": "what could actually go wrong (max 15 words)"
+}]
+```
+
+No extra text, no explanations, no markdown wrapping. An empty array `[]` is valid when nothing is found. Deletion findings from Step 4 and claim findings from Step 5, if any, go in the same array with the extra fields defined in `references/deletion-check.md` and `references/claims-check.md`.
+
+
+## HALT CONDITIONS
+
+- If no content is supplied, or it is empty, unreadable, or cannot be decoded as text, return `[{"location":"N/A","trigger_condition":"Input empty or undecodable","guard_snippet":"Provide valid content to review","potential_consequence":"Review skipped — no analysis performed"}]` and stop
+<reference path="references/deletion-check.md">
+# Deletion Check
+
+Secondary pass for the Edge Case Hunter — runs only when the diff removed meaningful code. Subordinate to the edge-case pass; findings are usually few or none.
+
+For each chunk of removed or replaced code (ignore pure renames and whitespace), ask: did it carry behavior or a contract that the change neither re-established nor intentionally retired? Add a finding for any resulting regression, orphaned reference, or newly-dead code. Skip anything already covered by your edge-case findings.
+
+Append each finding to the same JSON array as the edge-case findings, with the four standard fields plus:
+
+- `kind`: `"deletion"`
+- `confidence`: `"high"`, `"medium"`, or `"low"` — these are inferences; rate them
+
+For a deletion finding the standard fields read as: `location` = the removed item; `trigger_condition` = the behavior or contract it enforced; `guard_snippet` = where or how to re-establish it; `potential_consequence` = the regression or orphan.
+
+Add nothing if nothing qualifies.
+</reference>
+<reference path="references/claims-check.md">
+# Claims Check
+
+Final pass for the Edge Case Hunter — runs only when the message that launched you named a claims file. Read that file now, for the first time; the path tracing is finished and the claims cannot steer it retroactively.
+
+The file holds the change's own narrative — commit messages and any stated description. The narrative is the author's testimony, not evidence: a claim repeated in a code comment is still the same claim, not confirmation. Extract each checkable claim — what the change does, what it preserves, ordering, arithmetic, and parity with existing code ("exactly as X does") — then try to falsify each one against the code you have already traced. Where your trace is not enough to decide, read the code that decides it: the compared-to function, the actual callee, the state the claim assumes.
+
+Append one finding per falsified claim to the same JSON array, with the four standard fields plus:
+
+- `kind`: `"claim"`
+- `confidence`: `"high"`, `"medium"`, or `"low"`
+
+For a claim finding the standard fields read as: `location` = where the code contradicts the claim; `trigger_condition` = the claim, quoted or tightly paraphrased; `guard_snippet` = what the code actually does; `potential_consequence` = what goes wrong for someone who believed the claim.
+
+Verified claims produce nothing. Add nothing if nothing is falsified.
+</reference>
+
+## CONTENT SOURCE
+
+"Review content:" in the message that launched you gives the content itself or a path to read it from. Read the file when it is a path; either way that is the content under review, and this instruction file never is.