fmt: applied formatting

.gitattributes

@@ -1,7 +0,0 @@
-assets/config-template.yaml text eol=lf
-assets/hooks/*.sh text eol=lf
-assets/agents/** text eol=lf
-assets/functions/tools/* text eol=lf
-assets/functions/scripts/* text eol=lf
-assets/functions/utils/*.sh text eol=lf
-scripts/*.sh text eol=lf

.github/workflows/ci.yaml

@@ -3,7 +3,7 @@ name: CI
 on:
   pull_request:
     branches:
-    - '**'
+    - '*'
   push:
     branches:
     - main

.github/workflows/release.yaml

@@ -166,9 +166,6 @@ jobs:
             os: ubuntu-latest
             use-cross: true
             cargo-flags: ''
-          - target: aarch64-unknown-linux-gnu
-            os: ubuntu-24.04-arm
-            cargo-flags: ''
           - target: aarch64-apple-darwin
             os: macos-latest
             use-cross: true
@@ -256,7 +253,7 @@ jobs:
         run: echo "BUILD_CMD=cross" >> $GITHUB_ENV
 
       - name: Install latest LLVM/Clang
-        if: startsWith(matrix.os, 'ubuntu')
+        if: matrix.os == 'ubuntu-latest'
         run: |
           wget https://apt.llvm.org/llvm.sh
           chmod +x llvm.sh

.github/workflows/update-models.yaml

@@ -1,90 +0,0 @@
-name: Update models
-
-on:
-  schedule:
-    - cron: '0 */12 * * *'
-  workflow_dispatch:
-
-permissions:
-  contents: read
-
-concurrency:
-  group: update-models
-  cancel-in-progress: false
-
-defaults:
-  run:
-    shell: bash
-
-jobs:
-  update:
-    name: Update models
-
-    runs-on: ubuntu-latest
-
-    env:
-      RUSTFLAGS: --deny warnings
-
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          ssh-key: ${{ secrets.RELEASE_BOT_SSH_KEY }}
-          persist-credentials: true
-
-      - name: Install Rust Toolchain Components
-        uses: dtolnay/rust-toolchain@stable
-
-      - uses: Swatinem/rust-cache@v2
-
-      - name: Cache DuckDB Extensions
-        id: duckdb-extensions
-        uses: actions/cache@v4
-        with:
-          path: ~/.duckdb/extensions
-          key: duckdb-ext-ubuntu-latest-${{ hashFiles('Cargo.lock') }}
-
-      - name: Install DuckDB Extensions
-        if: steps.duckdb-extensions.outputs.cache-hit != 'true'
-        run: cargo test --all duckdb
-
-      - name: Write stub config
-        run: |
-          COYOTE_CONFIG_DIR="$(mktemp -d)"
-          printf 'clients:\n  - type: openai\n  - type: claude\n' > "$COYOTE_CONFIG_DIR/config.yaml"
-          echo "COYOTE_CONFIG_DIR=$COYOTE_CONFIG_DIR" >> "$GITHUB_ENV"
-
-      - name: Regenerate model catalog
-        run: cargo run --release -- --generate-models
-
-      - name: Detect catalog changes
-        id: diff
-        run: echo "changed=$(git diff --quiet models.yaml && echo false || echo true)" >> "$GITHUB_OUTPUT"
-
-      # The binary built by the regeneration step embedded the OLD models.yaml (the file
-      # was rewritten after that build), so rebuild before smoke-testing: cargo tracks
-      # include_str! inputs, making this a cheap incremental rebuild of the final crate.
-      - name: Rebuild with the refreshed catalog
-        if: steps.diff.outputs.changed == 'true'
-        run: cargo build --release
-
-      - name: Test
-        if: steps.diff.outputs.changed == 'true'
-        run: cargo test --all
-
-      - name: Smoke test the refreshed catalog
-        if: steps.diff.outputs.changed == 'true'
-        run: |
-          COUNT=$(./target/release/coyote --list-models | wc -l)
-          echo "Listed $COUNT chat models"
-          test "$COUNT" -ge 40
-
-      - name: Commit and push
-        if: steps.diff.outputs.changed == 'true'
-        run: |
-          git add models.yaml
-          git checkout -- .
-          git config user.name 'github-actions[bot]'
-          git config user.email '41898282+github-actions[bot]@users.noreply.github.com'
-          git commit -m 'chore: refresh generated model catalog [skip ci]'
-          git pull --rebase origin main
-          git push origin main

.gitignore

@@ -5,7 +5,4 @@
 .idea/
 /coyote.iml
 /.idea/
-.coyote/**
+.coyote
-.sisyphus/**
-.coyote-project.json
-.coyote/memory/

CHANGELOG.md

@@ -1,351 +1,3 @@
-## v0.10.3 (2026-09-15)
-
-### Feat
-
-- create a config alias for default_reasoning_level (to match some wording and make the config flexible)
-- support custom resource definitions for openai-compatible Oauth customization
-- Support specifying the compression model to use when compressing a session for greater cost controls
-- Added full cost tracking to Coyote and added it to the default right prompt
-- added support for input/output token cache cost tracking
-- Support persisting paused todo lists to sessions so users can exit and resume paused todo sessions; Also fixed a bug so todo list pausing is only supported when being used in a session since it typically requires multi-turn communication
-- Support token caching to reduce LLM costs in Anthropic models (not typically handled automatically by APIs)
-- **TASK-030**: callers escalate on GAUNTLET_REVIEW_INCOMPLETE instead of findings-routing
-- **TASK-032**: review-gauntlet incomplete-review machine line + ×N attempt details
-- **TASK-029**: review-gauntlet fault-only lane re-run loop
-- **TASK-028**: escalation_timeout 0 waits indefinitely and is the default
-- **graph**: stream llm-node completions so node timeout governs long generations
-- **TASK-023**: deep-research hardening — fail-safe scripts, fault fallbacks, pipeline notes
-- **TASK-020**: finding-verifier + step-runner fail-closed hardening
-- **TASK-019**: code-reviewer fail-closed review pipeline
-- **TASK-018**: review-gauntlet lane degradation + verification passthrough
-- **TASK-017**: adversary execution evidence + fail-closed routing
-- **TASK-016**: engine + test fixes from the Phase-1 re-review
-- **TASK-011**: traverse agent fallback edges in map peer-discovery BFS
-- **TASK-010**: add max_attempts to read-only agent lanes in bundled graphs
-- **TASK-009**: add fallback routing to agent nodes
-- **TASK-008**: add shared transient matcher and retry support to agent nodes
-- Fixed graph agents with new agent variable passing functionality
-- **graph**: warn when a declared variable is shadowed by an initial_state key
-- **agents**: advertise declared agent variables in agent__list_available
-- **agents**: allow passing agent variables to agent__spawn and agent__task_create
-- seed variables into initial graph state
-- Significant code review suite rewrite with improved graph agent features
-- let install commands remove files that have been removed from bundles, both internal and external
-- update the web_search_coyote tool to attempt to use the current model first then fallback to the configured model for web searches
-- expose the current coyote model to tools
-- removed temperature specification in deep-research and finding-verifier agents to make them more univerally usable
-- **graph**: thread the graph abort into llm nodes and tool execution
-- **graph**: abort a graph run on Ctrl-C from anywhere
-- **graph**: warn when an llm node's turn cap is disabled
-- **graph**: treat llm max_iterations: 0 as no turn cap
-- **graph**: warn when the visit cap is disabled
-- **graph**: treat max_loop_iterations: 0 as no visit cap
-- **graph**: warn when a timeout is disabled
-- **graph**: treat timeout: 0 as no wall-clock bound
-- **graph**: validate agent node inputs at load time
-- **graph**: seed a child graph agent's state from an agent node's inputs map
-- **graph**: validate map branch subgraphs instead of single branch nodes
-- **graph**: run map branches as per-item subgraph chains
-- **graph**: accept a `{{template}}` for a map node's `max_concurrency`
-- created the finding-verifier and whetstone agents for continuous code quality improvements
-- teammates flag enabling peer messaging between concurrent graph agent nodes
-- support explicit can_spawn_agents, max_concurrent_agents, and max_agent_depth keys in graph.yaml
-- support setting the tool_timeout in the main config file instead of only via an environment variable
-- Added new environment variable to force showing tool call logging when not in a tty
-
-### Fix
-
-- empty tool results can't cause errors in bedrock, claude, openai, or vertexai clients anymore
-- proper support for reasoning/thinking in bedrock models
-- **TASK-032**: enforce incomplete⇒BLOCKED structurally; anchor adversary degraded detection
-- **TASK-028**: pin example-doc wording; make not-found escalation hint match queue semantics
-- **TASK-028**: pin global-template exclusion, tighten timeout boundary test, reword stale hint
-- **adversary**: red verification runs block CONFORMS; re-derive timeout envelope; robust runner
-- **review-suite**: detect nested finding-verifier faults; harden render/fault markers
-- **review-gauntlet**: summary-line critical count, nested-fault hook, fail-closed lane fallback
-- **graph**: typed ApiStatusError transient classification; warn on bare output_schema
-- **review-suite**: mark example verification commands as placeholders; pin variable description and prompt note
-- **graph**: auto-merge only schema-declared keys from llm output
-- **review-suite**: pass verification_commands as a declared variable, never LLM-extracted from prose
-- **agents**: scrub GRAPH_STATE* from adversary verification commands; raise review-suite max_agent_depth
-- **adversary**: narrow died-marker predicate, degraded banner for died criteria, hermetic script tests
-- **adversary**: fail closed on PIPELINE-FAULT evidence regardless of status; pin bail-chain and validator shape
-- **adversary**: fail closed per criterion when check_criterion dies
-- **engine**: carry full error chain in llm node fault text
-- **TASK-020**: skip POSIX bash script tests on Windows
-- **TASK-020**: surface step-runner LLM-fault captures where the fallback lands
-- **TASK-019**: carry PIPELINE-FAULT prefix through verdict.py's crash guard
-- **TASK-018**: harden verdict_gate fault routing and widen default_lanes fallback
-- **TASK-017**: bound run_checks runtime and fail-close its node-level death
-- **tests**: collision-proof parser test temp files to deflake macOS CI
-- Don't infinitely compress a session once it passes a threshold when the threshold is close to the max token count
-- fix spinner ctrl-c early exit not clearing message and restoring cursor
-- **graph**: build peer retirement guards before spawning their tasks
-- **graph**: reject agents that ship both config.yaml and graph.yaml at load
-- **graph**: bound concurrency caps by the semaphore permit limit
-- **graph**: make turn-cap and template checks consistent across validation modes
-- **graph**: leave output absent after state_updates when it was absent before
-- **graph**: validate the whole max_concurrency template string
-- **graph**: reject as == output_key on map nodes
-- **graph**: inherit the session abort in agent-node children
-- **graph**: retire the teammate identity before structured extraction
-- **graph**: reject a literal max_concurrency of 0 instead of clamping it
-- **graph**: clear peer identity fields after every map chain step
-- **graph**: pick the map teammate identity name by BFS from the branch entry
-- **graph**: name the offending node type when a map branch reaches a disallowed node
-- **function**: build bundled bash tools without writing back to the source tree
-- **agents**: name the map-branch output key in deep-research and finding-verifier
-- **graph**: honor an explicit `output` key in state_updates
-- Fixed the bad formatting in the finding-verifier agent
-- properly anchored the role frontmatter regex so it doesn't catch in-instruction separators
-- support non-object tool result outputs for bedrock
-- exclude null bytes from fs_grep output on binaries
-- suppress subagent error and warning output to stderr/stdout
-
-### Refactor
-
-- **graph**: keep the ordered visit log test-only
-- **graph**: move the cfg(test) OUTPUT_KEY import into llm's test module
-- **graph**: drop the duplicated locator prefix from map chain step errors
-
-## v0.10.2 (2026-09-04)
-
-### Feat
-
-- added a clear line separator for the end of LLM turns to make it more clear where they are
-- sort models by release date
-- Improved the architect, explore, and sisyphus agents to have a team mode so they can all work in parallel as a team and updated the parallel-research skill to make explicit mention of this functionality
-- support auto continuation in subagents and prevent them from calling todo__pause
-- apply provider quirks to models created from a name
-- refresh the model catalog from live API data at runtime
-- generate the model catalog from live API data
-- add model catalog source adapters and merge engine
-- add hand-owned model quirks overlay
-- apply provider quirks to models created from a name
-- refresh the model catalog from live API data at runtime
-- generate the model catalog from live API data
-- add model catalog source adapters and merge engine
-- add hand-owned model quirks overlay
-- Improved the architect, explore, and sisyphus agents to have a team mode so they can all work in parallel as a team and updated the parallel-research skill to make explicit mention of this functionality
-- added tab completions to --update-bundle flag
-- added a dedicated config_dir output to coyote --info/.info
-
-### Fix
-
-- children subagents couldn't properly send messages to parent inboxes
-- --generate-models parsed before vault initialization
-- drive tool rounds iteratively instead of recursively to prevent stack overflow on long agentic turns to fix latent stack overflow recursion bug
-- session replays now include mid-turn messages so the full session gets replayed
-- resolve duplicate model ids by requested type
-- let ctrl-c interrupt blocking job and agent collects
-- skip terminal color-scheme queries in test builds
-- memoize quirk glob patterns and isolate concurrent override writes
-- memoize quirk glob patterns and isolate concurrent override writes
-- children subagents couldn't properly send messages to parent inboxes
-
-### Perf
-
-- probe models-override staleness in the background refresh task
-
-## v0.10.1 (2026-08-31)
-
-### Fix
-
-- make binary shims for custom tools cross-device compatible so users can't accidentally break sandboxes via `sbx cp ~/.config/coyote <sbx-name>:/home/agent/.config`
-
-## v0.10.0 (2026-08-29)
-
-### BREAKING CHANGE
-
-- invocations using --prompt <text> must switch to
---temp-role <text>; clap rejects the old flag loudly.
-
-### Feat
-
-- Support Linux ARM64 GNU
-- Note that duckdb RAG driver is unavailable on MUSL Linux builds when initializing a RAG so users know when using the binary, not just based on docs
-- updated coyote installation scripts to detect when gnu is installable
-- upgraded to v2 mixin schema
-- improved first-time run experience and included a templated configuration file that now has comments like the config.example.yaml so users don't have to go to the repo to see all the knobs
-- **TASK-005**: carry the quality bar through sisyphus and architect
-- **TASK-004**: reviewer routing — code-reviewer quality-bar resolution, domain linter pass, surface-skill routing, rigor folding; file-reviewer surface-skill whitelist + convention/correctness marker
-- **TASK-003**: add surface skills batch B — worker-review, iac-review, migration-review, cicd-review
-- **TASK-002**: add surface skills batch A — rest-api-review, cli-review, library-review
-- **TASK-001**: add rigor/surfaces declaration layer to planning skills
-- **repl**: color .info mcp-server verdicts and complete only running servers
-- **cli**: rename mcp_config asset category to mcp-config with snake_case alias
-- create a new probe agent to probe code verifications using usage-pattern testing
-- Add in the web_search_coyote tool where helpful
-- **mcp**: add .info mcp-server, .set mcp_tools, and filtered-server listing to the REPL
-- **mcp**: enforce per-server tool allowlists across runtime, jobs, agents, and graph nodes
-- **mcp**: add mcp_tools allowlist config surfaces across roles, sessions, agents, graphs, and skills
-- **mcp**: add per-server tool allowlist policy module and allowedTools config field
-- support mcp.json in the root of bundle repos as well as in the legacy functions directory
-- prefer ~/.config/coyote/mcp.json for the user-scope MCP config
-- claude and openai native web search via web_search_coyote
-- **jobs**: node-local job ownership and capability-gated job__* visibility
-- **graph**: support max_concurrent_jobs at the graph level
-- **jobs**: allow uncapped collect via full_result
-- **jobs**: exempt polling tools from loop tracker and hint on unchanged checks
-- **supervisor**: push agent completion notifications to the spawning context
-- **jobs**: push background-job completion notifications via per-context queue
-- inject background-jobs prompt guidance when jobs are enabled
-- add background job runner, job__* handlers, and start gates
-- generalize supervisor registry to TaskHandle enum with job scaffolding, kill discipline, and max_concurrent_jobs config
-- run an advisory observability pass after implementation in sisyphus
-- add an observability-review skill for post-implementation monitoring analysis
-- check under- and over-logging in the code review gate
-- calibrate logging registers in the code-writing agents
-- add a logging-discipline skill for calibrating log output to repo conventions
-- **cli**: rename --prompt to --temp-role
-- complete --filter and --force on the first .install argument
-- **mcp**: bound tool-result passthrough and surface resource audience annotations
-- **mcp**: add mcp_prompt meta-tool and harden prompt display rendering
-- **repl**: add .prompt command with live staged tab-completion
-- **mcp**: add mcp_read meta-tool for resource reads
-- **mcp**: gate meta-function emission on advertised server capabilities
-- **mcp**: add render.rs content policy (text paging, pattern filter, blob spill)
-- **mcp**: extend the server catalog to resources, templates, and prompts
-- complete --filter and --force on the first .install argument
-- run design interviews as grilling frontier rounds across the planning agents
-- add a grilling skill for frontier-round design interviews
-- add an on-demand architecture-reviewer agent for deepening scans
-- add a codebase-design skill with the deep-module design vocabulary
-- add a feedback-loop-first diagnosing-bugs skill to the coding suite
-- add a Fowler code-smell baseline to the code-review skill
-- flag duplicate helpers in code reviews with a repo-wide DRY check
-- add a transactional-integrity review skill to the code review gate
-- add an operational-history prior-art lane to the code-reviewer agent
-- support name=value macro arguments with variable tab completion
-- add --help guides to the .install and .uninstall REPL commands
-- expand owner/repo shorthand for --install with a --git-host flag
-- remove the deprecated --install-from flag and .install remote form
-- rename install flags and unify .install dispatch
-- add --uninstall and .uninstall for installed bundles
-- add --update-bundle with provenance-aware conflict handling
-- add --list-bundles and .list bundles with drift detection
-- record bundle provenance when installing from remote repos
-- add bundle provenance store
-- parse bundle manifests and capture resolved SHAs for remote installs
-- created a new comment-discipline skill for the built in sisyphus suite
-- created a dedicated git_command tool to tighten tool calling permissions in the git-master skill
-- Added a new security review step to the code writing quality gates
-- addressed review comments
-- add --no-workspace-macros opt-out for workspace macro loading
-- execute non-isolated macros on the live REPL context
-- surface macros as first-class custom commands in the REPL
-- add lazy macro resolver with two-dir discovery and per-macro states
-- add enabled_macros config field at global, role, agent, and session levels
-- add description and isolated fields to Macro struct
-- Dynamically detect RAG embedding model dimension for any given model
-- Support auto confirmation for gatekeeper agents
-- retry LLM API calls once after 401 by force-refreshing the OAuth token
-- identity-aware rejected-token marker for LLM OAuth cache
-- typed ApiStatusError carrying HTTP status through LLM client errors
-- per-request OAuth token injection with mid-session refresh for HTTP MCP servers
-- reason-specific warnings for MCP servers that fail OAuth at startup
-- Installed duckdb into the coyote image
-- Support managing MCP servers from the CLI directly
-- append new built-in rag__query function to RAG contexts to allow further querying by LLMs
-- support static file bundling with sbx-mixins
-- **rag**: offer the storage driver when an agent initializes its RAG
-- simplified the duckdb selection prompt
-- **rag**: let several Coyote processes query one duckdb RAG at once
-- **rag**: support string and UUID Qdrant point IDs
-- **rag**: create the API key secret inline in the attach wizard
-- let workflow rag nodes select a RAG driver
-- improved wording and heuristic detection for sisyphus suite of agents
-- upgraded to sbx kit v2 spec for improved integration
-- **rag**: add attach-only Qdrant provider, attach wizard and sandbox wiring
-- **rag**: add DuckDB provider behind the RAG driver abstraction
-- **rag**: add driver/attached fields, validation floors and force-reingest
-- **mcp**: send RFC 8707 resource indicator in OAuth flows
-- Added loaded indicators to .list tools/mcp-servers/skills
-- hide .recover from tab completions when no session is active
-- add a new .recover command for sessions to recover from errors
-- integrated the git-ssh-sign kit into the coyote sandbox kit
-
-### Fix
-
-- Harden install scripts: detect libssl3 without ldconfig on PATH, survive noexec tmp dirs, and guard against partial curl|bash execution
-- ldconfig on Debian-based distros lives in /usr/sbin
-- Prefer GNU linux builds in install scripts for duckdb support, and gate duckdb support on linux hosts that are MUSL until MUSL support is added
-- **mcp**: omit declared-but-empty prompt/resource capabilities from .info mcp-server
-- **mcp**: annotate declared-but-empty prompt/resource capabilities in .info mcp-server
-- also support the .continue edge case for session crashing checkpointing
-- checkpoint sessions that crash for easy resuming
-- job__check ring buffer also collects file output for LLM_OUTPUT as well as stdout
-- **tools**: interactive-shell semantics and stderr capture in execute_command
-- **function**: gate test-only declaration appender behind cfg(test)
-- **graph**: gate unix-only test imports behind cfg(unix)
-- harden job runner lifecycle and whitelist conformance
-- **function**: floor tool-output truncation cut to a UTF-8 char boundary
-- **supervisor**: make agent__check a pure status probe that never consumes the handle
-- **supervisor**: surface finished-but-uncollected tasks in turn-end guardrail
-- fix grep "binary" errors when searching UTF-8 files with unicode characters like some of the Coyote source
-- **bundles**: harden the install pipeline for cross-platform correctness
-- **mcp**: harden the spill path for cross-platform correctness
-- **repl**: offer prompts in .list tab completion and rename its listing helpers
-- **mcp**: gate unix-only spill permission APIs for windows builds
-- harden the bundle lifecycle per code review
-- address code review findings on the bundle lifecycle
-- reserve category names, confirm fork-name collisions, report secrets on uninstall
-- make bundle provenance portable to Windows
-- user__ask should have been renamed to user__select in graph agent user interaction invocations
-- support tab completions for graph-based agents with variables as well as standard agents
-- surface macro parse errors on top-level invocation
-- render .list macros as a comfy-table instead of fixed-width columns
-- drain crossterm characters in zellij in kitty contexts to prevent DA1 responses from entering prompt
-- drain tty input when displaying inquire prompts to prevent unintentional escapes
-- breaking iwe MCP server changes with newest version
-- improved handling of non service-specific secrets using sbx custom-secrets
-- include tool output to LLM_OUTPUT in errors as well as stderr
-- prevent tmp-overwriting
-- Corrected a rare edge case on how tool files are generated during parallel executions
-- cosmetic fix after improved bash tool handling
-- Improved subagent escalation handling
-- latent parsing bugs in fs_patch and argc
-- Prevent infinite hangs in coder agent and implement timeouts for LLM API calls and interactive tools
-- allow nested italics inside bold spans in markdown renderer
-- properly handle OAuth refreshes
-- correct newline removal from fs_write and fs_patch
-- detect duplicate tool call IDs client-side before sending to Claude
-- **rag**: warn when a duckdb store is empty but files are indexed
-- **rag**: keep a local Qdrant off an ambient proxy
-- keep loopback and LAN traffic off an ambient proxy
-- **rag**: stop routing Qdrant requests through an ambient proxy
-- **rag**: treat a zero min_score as no floor on Qdrant searches
-- **rag**: address Copilot review findings on the driver abstraction
-- **rag**: delete the DuckDB write-ahead log alongside the store
-- **sandbox**: discover agent-scoped RAG mixin sidecars
-- **rag**: stop the attach wizard from silently accepting an empty collection
-- **rag**: fail loudly when a RAG's vault secret is missing
-- **rag**: serialize DuckDB extension installs to stop a Windows race
-- **rag**: emit an sbx kit v2 mixin and declare RAG credentials to the proxy
-- **rag**: install DuckDB vss and fts extensions when they are missing
-- don't output thinking blocks for claude-based models
-- additional edge case fix for duplicate tool call IDs in anthropic API calls
-- removed temperature modifier in librarian agent to mitigate invisible errors
-- strip reasoning blocks for structured LLM output in graph agents
-- prevent rare duplicate tool call IDs in long running claude prompts
-- agents inherit global reasoning effort if unset
-
-### Refactor
-
-- **function**: finish supervisor-to-agent vocabulary migration
-- **function**: rename agent-tool symbols out of supervisor vocabulary
-- Modified the naming of several generalized supervisor values
-- pulled out some imports to clean up the MCP render module a bit
-- **mcp**: centralize meta-function prefix predicates and fix list_tools pagination
-- Refactored some bundle const locations
-- drop the .install remote migration hint
-- drop the --install-from tombstone entirely
-- render .list agents and .list skills as comfy-tables
-- **rag**: discover driver_config secrets by grammar, not field name
-- **rag**: drop the hardcoded embedding model hint from attach
-- **rag**: interpolate every driver_config value, not just api_key
-- **rag**: extract RagProvider trait and add YamlProvider
-
 ## v0.8.3 (2026-08-03)
 
 ### Fix

CREDITS.md

@@ -1,16 +1,5 @@
 # Credits
 
-## Matt Pocock's Skills
-
-The bundled `diagnosing-bugs`, `codebase-design`, and `grilling` skills, the
-`architecture-reviewer` agent, and the code smell baseline in the bundled
-`code-review` skill are adapted from
-[mattpocock/skills](https://github.com/mattpocock/skills) by Matt Pocock,
-licensed under the MIT License. The smell definitions trace back to Martin
-Fowler's *Refactoring* (ch. 3); the deep-module vocabulary builds on John
-Ousterhout's *A Philosophy of Software Design* and Michael Feathers'
-*Working Effectively with Legacy Code*.
-
 ## AIChat
 Coyote originally started as a fork of the fantastic
 [AIChat CLI](https://github.com/sigoden/aichat). The initial goal was simply

Cargo.toml

@@ -1,9 +1,9 @@
 [package]
 name = "coyote-ai"
-version = "0.10.3"
+version = "0.8.3"
 edition = "2024"
 authors = ["Alex Clarke <alex.j.tusa@gmail.com>"]
-description = "The batteries-included runtime for LLMs"
+description = "An all-in-one, batteries included LLM CLI Tool"
 keywords = ["chatgpt", "llm", "cli", "ai", "repl"]
 homepage = "https://github.com/Dark-Alex-17/coyote"
 repository = "https://github.com/Dark-Alex-17/coyote"
@@ -51,13 +51,7 @@ textwrap = "0.16.0"
 ansi_colours = "1.2.2"
 eventsource-stream = "0.2.3"
 log = "0.4.28"
-log4rs = { version = "1.4.0", features = [
+log4rs = { version = "1.4.0", features = ["file_appender", "rolling_file_appender", "compound_policy", "fixed_window_roller", "size_trigger"] }
-  "file_appender",
-  "rolling_file_appender",
-  "compound_policy",
-  "fixed_window_roller",
-  "size_trigger",
-] }
 shell-words = "1.1.0"
 sha2 = "0.10.8"
 unicode-width = "0.2.0"
@@ -90,7 +84,7 @@ duct = "1.0.0"
 argc = "1.23.0"
 strum_macros = "0.27.2"
 indoc = "2.0.6"
-rmcp = { version = "3.1.2", features = [
+rmcp = { version = "1.5.0", features = [
   "client",
   "transport-child-process",
   "transport-streamable-http-client-reqwest",
@@ -119,7 +113,14 @@ qrcode = "0.14"
 
 [dependencies.reqwest]
 version = "0.13.3"
-features = ["json", "multipart", "stream", "form", "socks", "rustls"]
+features = [
+  "json",
+  "multipart",
+  "stream",
+  "form",
+  "socks",
+  "rustls",
+]
 default-features = false
 
 [dependencies.syntect]
@@ -138,15 +139,9 @@ arboard = { version = "3.3.0", default-features = false, features = [
 [target.'cfg(not(any(target_os = "linux", target_os = "android", target_os = "emscripten")))'.dependencies]
 arboard = { version = "3.3.0", default-features = false }
 
-[target.'cfg(unix)'.dependencies]
-libc = "0.2"
-
 [dev-dependencies]
-ctor = "1.0.13"
 pretty_assertions = "1.4.0"
-rmcp = { version = "3.1.2", features = ["server"] }
 serial_test = "3"
-tokio = { version = "1.34.0", features = ["test-util"] }
 
 [[bin]]
 name = "coyote"

Dockerfile

@@ -99,7 +99,7 @@ LABEL com.docker.sandboxes="templates" \
       com.docker.sandboxes.flavor="shell-docker" \
       com.docker.sandboxes.start-docker="true" \
       org.opencontainers.image.title="coyote" \
-      org.opencontainers.image.description="The batteries-included runtime for LLMs: Shell Assistant, CLI & REPL mode, RAG, AI tools & agents, MCP servers, skills, and macros." \
+      org.opencontainers.image.description="An all-in-one, batteries-included LLM CLI tool: Shell Assistant, CLI & REPL mode, RAG, AI tools & agents, MCP servers, skills, and macros." \
       org.opencontainers.image.source="https://github.com/Dark-Alex-17/coyote" \
       org.opencontainers.image.version="${COYOTE_VERSION}"
 

README.md

@@ -1,4 +1,4 @@
-# Coyote: The batteries-included runtime for LLMs
+# Coyote: All-in-one, batteries-included LLM CLI Tool
 
 ![Test](https://github.com/Dark-Alex-17/coyote/actions/workflows/ci.yaml/badge.svg)
 [![crates.io link](https://img.shields.io/crates/v/coyote-ai.svg)](https://crates.io/crates/coyote-ai)
@@ -6,18 +6,14 @@
 ![Crate.io downloads](https://img.shields.io/crates/d/coyote-ai?label=Crate%20downloads)
 [![GitHub Downloads](https://img.shields.io/github/downloads/Dark-Alex-17/coyote/total.svg?label=GitHub%20downloads)](https://github.com/Dark-Alex-17/coyote/releases)
 ![Docker pulls](https://img.shields.io/docker/pulls/darkalex17/coyote?label=Docker%20downloads)
-[![License: AGPL v3](https://img.shields.io/badge/License-AGPL_v3-blue.svg)](https://github.com/Dark-Alex-17/coyote/blob/main/LICENSE)
+[![License: AGPL v3](https://img.shields.io/badge/License-AGPL_v3-blue.svg)](./LICENSE)
 
-Coyote is an **all-in-one, batteries-included LLM runtime** for building, running, and interacting with AI from your terminal.
+Coyote is an all-in-one, batteries-included, LLM CLI tool featuring Shell Assistant, CLI & REPL Mode, RAG, AI Tools & 
-It brings together a Shell Assistant, CLI & REPL modes, RAG, tools, agents, MCP, skills, sandboxes, multi-agent workflows, and
+Agents, and More.
-more in a single runtime.
-
-Coyote comes ready to use with built-in agents, roles, macros, and tools, so you can get started without assembling an AI
-stack from scratch. When you want to extend it, entire bundles of agents, roles, macros, tools, MCP servers, and other
-configurations can be installed directly from any Git repository.
-
-See [Bundles](https://github.com/Dark-Alex-17/coyote/wiki/Bundles) to learn how to create, install, and share Coyote bundles.
 
+It is designed to include a number of useful agents, roles, macros, and more so users can get up and running with Coyote 
+in as little time as possible. You can also install entire bundles of agents, roles, macros, tools, and MCP servers from 
+any git repository. See [Sharing Configurations](https://github.com/Dark-Alex-17/coyote/wiki/Sharing-Configurations) for more information.
 
 ![Agent example](https://raw.githubusercontent.com/wiki/Dark-Alex-17/coyote/images/agents/sql.gif)
 
@@ -27,7 +23,7 @@ Coming from [AIChat](https://github.com/sigoden/aichat)? Follow the [migration g
 * [AIChat Migration Guide](https://github.com/Dark-Alex-17/coyote/wiki/AIChat-Migration): Coming from AIChat? Follow the migration guide to get started.
 * [Installation](#install): Install Coyote
 * [Getting Started](#getting-started): Get started with Coyote by doing first-run setup steps.
-* [Bundles](https://github.com/Dark-Alex-17/coyote/wiki/Bundles): Install bundles of agents, roles, skills, macros, tools, and MCP servers from any git repo, and share your own. Bundles are Coyote's equivalent of plugins in other CLI agents.
+* [Sharing Configurations](https://github.com/Dark-Alex-17/coyote/wiki/Sharing-Configurations): Install bundles of agents, roles, macros, tools, and MCP servers from any git repo, and share your own.
 * [REPL](https://github.com/Dark-Alex-17/coyote/wiki/REPL): Interactive Read-Eval-Print Loop for conversational interactions with LLMs and Coyote.
   * [Custom REPL Prompt](https://github.com/Dark-Alex-17/coyote/wiki/REPL-Prompt): Customize the REPL prompt to provide useful contextual information.
 * [Vault](https://github.com/Dark-Alex-17/coyote/wiki/Vault): Securely store and manage sensitive information such as API keys and credentials.
@@ -39,14 +35,8 @@ Coming from [AIChat](https://github.com/sigoden/aichat)? Follow the [migration g
         * [Create Custom TypeScript Tools](https://github.com/Dark-Alex-17/coyote/wiki/Custom-Tools#custom-typescript-based-tools)
         * [Create Custom Bash Tools](https://github.com/Dark-Alex-17/coyote/wiki/Custom-Bash-Tools)
             * [Bash Prompt Utilities](https://github.com/Dark-Alex-17/coyote/wiki/Bash-Prompt-Helpers)
-* [First-Class MCP Server Support](https://github.com/Dark-Alex-17/coyote/wiki/MCP-Servers): Easily connect and interact with MCP servers for advanced functionality. Coyote supports all three MCP capabilities: tools, resources, and prompts.
+* [First-Class MCP Server Support](https://github.com/Dark-Alex-17/coyote/wiki/MCP-Servers): Easily connect and interact with MCP servers for advanced functionality.
-    * Models interact with each server through a compact set of capability-gated meta-tools: `mcp_search`/`mcp_describe` for discovery across tools, resources, and prompts, `mcp_invoke` for tool calls, `mcp_read` for paged and regex-filterable resource reads, and `mcp_prompt` for server-defined prompts. Binary content is spilled to disk instead of inlined, and oversized tool results are bounded before they reach the model.
+* [Macros](https://github.com/Dark-Alex-17/coyote/wiki/Macros): Automate repetitive tasks and workflows with Coyote "scripts" (macros).
-    * Invoke server prompts yourself with `.prompt <server> <name> [key=value ...]` in the REPL, with live staged tab-completion (servers, then prompt names, then `key=` arguments), and discover them with `.list prompts`.
-* [Macros](https://github.com/Dark-Alex-17/coyote/wiki/Macros): Automate repetitive tasks and workflows with Coyote "scripts" (macros). Macros are Coyote's custom commands: invoke any macro directly by name (e.g. `.review main`), with tab-completion, right alongside the built-in REPL commands.
-    * Give a macro a `description` (shown in `.list macros` and completions) and set `isolated: false` to run its steps on the live session, exactly as if you typed them. Note that non-isolated steps are recorded in the session, and mutating steps (`.role`, `.model`, ...) persist after the macro ends, by design. Steps are fail-fast: an error aborts the remaining steps, but completed steps' effects remain. A non-isolated macro step cannot invoke another macro, and a `.exit` step never exits the REPL.
-    * Commit project-specific macros to `.coyote/macros/` in your repo. They shadow same-named global macros (opt out with `--no-workspace-macros`).
-    * Pass variables positionally or by name: leading `name=value` args set declared variables directly (letting earlier variables keep their defaults), and remaining args fill the rest in order. Tab completion after a macro name lists each variable with its description and default.
-    * Scope which macros are invocable with `enabled_macros` in the global config, a role, an agent, or a session (most specific wins; an empty list disables all macros), and toggle at runtime with `.macro enable|disable <name>`.
 * [RAG](https://github.com/Dark-Alex-17/coyote/wiki/RAG): Retrieval-Augmented Generation for enhanced information retrieval and generation.
 * [Sessions](https://github.com/Dark-Alex-17/coyote/wiki/Sessions): Manage and persist conversational contexts and settings across multiple interactions.
 * [Memory](https://github.com/Dark-Alex-17/coyote/wiki/Memory): Persistent file-based memory that survives across sessions. Bootstrap with `coyote --init-memory [global|workspace]`.
@@ -55,14 +45,11 @@ Coming from [AIChat](https://github.com/sigoden/aichat)? Follow the [migration g
 * [Skills](https://github.com/Dark-Alex-17/coyote/wiki/Skills): Modular knowledge or capability packs the LLM can load and unload mid-conversation. Multiple skills compose; instructions stack, tools and MCPs union.
 * [Agents](https://github.com/Dark-Alex-17/coyote/wiki/Agents): Leverage AI agents to perform complex tasks and workflows, including sub-agent spawning, teammate messaging, and user interaction tools.
     * [Graph Agents](https://github.com/Dark-Alex-17/coyote/wiki/Graph-Agents): Define an agent as a declarative, YAML-driven workflow. A directed graph of typed nodes (LLM calls, scripts, approvals, user input, RAG retrieval, sub-agent spawns).
-* [Background Jobs](https://github.com/Dark-Alex-17/coyote/wiki/Background-Jobs): Run long tool calls (builds, test suites, slow MCP calls) in the background with the `job__*` tools while the model keeps working, and completion arrives as a push notification.
-* [Hooks](https://github.com/Dark-Alex-17/coyote/wiki/Hooks): Run your own fire-and-forget commands when lifecycle events fire. Turns, tools, LLM requests, agents, sub-agent escalations, and more (26 events). Perfect for desktop notifications, activity logging, and downstream automation; hooks never block Coyote or change its behavior.
 * [Todo System](https://github.com/Dark-Alex-17/coyote/wiki/TODO-System): Built-in task tracking for improved LLM reliability with smaller models.
 * [Environment Variables](https://github.com/Dark-Alex-17/coyote/wiki/Environment-Variables): Override and customize your Coyote configuration at runtime with environment variables.
 * [Client Configurations](https://github.com/Dark-Alex-17/coyote/wiki/Clients): Configuration instructions for various LLM providers.
     * [Authentication (API Key & OAuth)](https://github.com/Dark-Alex-17/coyote/wiki/Clients#authentication): Authenticate with API keys or OAuth for subscription-based access.
     * [Patching API Requests](https://github.com/Dark-Alex-17/coyote/wiki/Patches): Learn how to patch API requests for advanced customization.
-* [Dynamic Model Catalog](https://github.com/Dark-Alex-17/coyote/wiki/Model-Catalog): Coyote's model catalog (context windows, pricing, capabilities) is generated from live API data, refreshed automatically in the background, and mirrorable for air-gapped setups. New models show up without waiting for a release.
 * [Custom Themes](https://github.com/Dark-Alex-17/coyote/wiki/Themes): Change the look and feel of Coyote to your preferences with custom themes.
 * [History](#history): A history of how Coyote came to be.
 
@@ -84,7 +71,7 @@ Coyote requires the following tools to be installed on your system:
     * **npm:** `npm i -g @ast-grep/cli`
     * Optional: if `ast-grep` is not installed, the `ast_grep` tool reports it and agents fall back to `fs_grep`
 * [duckdb](https://duckdb.org/) (for fast, local RAGs)
-    * `curl https://install.duckdb.org | bash`
+    * `curl https://install.duckdb.org | sh`
 
 These tools are used to provide various functionalities within Coyote, such as document processing, JSON manipulation,
 etc., and they are used within agents and tools.
@@ -269,7 +256,7 @@ coyote | Out-String | Invoke-Expression
 
 ### Shell Integration
 You can integrate Coyote's Shell Assistant into your shell for enhanced command-line assistance. Add the code in the
-corresponding [shell integration script](https://github.com/Dark-Alex-17/coyote/tree/main/scripts/shell-integration) to your shell. Then, you can invoke Coyote to convert natural language to 
+corresponding [shell integration script](./scripts/shell-integration) to your shell. Then, you can invoke Coyote to convert natural language to 
 shell commands by pressing `Alt-e`. For example:
 
 ```shell
@@ -287,7 +274,7 @@ coyote --info | grep 'config_file' | awk '{print $2}'
 ```
 
 The configuration file consists of a number of settings. To see a full example configuration file with every setting
-defined, refer to the [example configuration file](https://github.com/Dark-Alex-17/coyote/blob/main/config.example.yaml).
+defined, refer to the [example configuration file](./config.example.yaml).
 
 ### Default LLM
 The following settings are available to configure the default LLM that is used when you start Coyote, and its
@@ -341,7 +328,7 @@ The appearance of Coyote can be modified using the following settings:
 
 Coyote began as a fork of [AIChat CLI](https://github.com/sigoden/aichat) and has since evolved into an independent project.
 
-See [CREDITS.md](https://github.com/Dark-Alex-17/coyote/blob/main/CREDITS.md) for full attribution and background.
+See [CREDITS.md](./CREDITS.md) for full attribution and background.
 
 ---
 
@@ -352,11 +339,11 @@ See [CREDITS.md](https://github.com/Dark-Alex-17/coyote/blob/main/CREDITS.md) fo
 
 ## License
 
-Coyote is licensed under the [GNU Affero General Public License v3.0](https://github.com/Dark-Alex-17/coyote/blob/main/LICENSE)
+Coyote is licensed under the [GNU Affero General Public License v3.0](./LICENSE)
 (AGPL-3.0-only).
 
 Coyote began as a fork of [AIChat](https://github.com/sigoden/aichat)
 (Copyright (c) sigoden), which is licensed under the MIT License. Substantial
 portions of Coyote are derived from AIChat and remain available under the MIT
-License, preserved in [LICENSE-MIT](https://github.com/Dark-Alex-17/coyote/blob/main/LICENSE-MIT). See [NOTICE](https://github.com/Dark-Alex-17/coyote/blob/main/NOTICE) and
+License, preserved in [LICENSE-MIT](./LICENSE-MIT). See [NOTICE](./NOTICE) and
-[CREDITS.md](https://github.com/Dark-Alex-17/coyote/blob/main/CREDITS.md) for details.
+[CREDITS.md](./CREDITS.md) for details.

assets/agents/adversary/README.md

@@ -1,16 +1,5 @@
 # Adversary
 
-> [!IMPORTANT]
-> **v2: now a GRAPH agent.** The plan's acceptance criteria are extracted into a list and the graph
-> fans out ONE fresh-context verification branch per criterion — partial coverage ("checked 8 of 12")
-> is structurally impossible. Each verdict passes a deterministic contract gate (MET requires
-> evidence including a proving test; no test = at best PARTIAL), a holistic ADDITIVE-only pass hunts
-> absence/scope-drift/substitution/gamed-tests, and the CONFORMS/DIVERGES sentinel is computed by a
-> script (missing plan = DIVERGES, fail-closed). The conformance doctrine below is structurally
-> enforced: CONFORMS requires ALL MET + zero holistic complaints + zero pipeline faults +
-> zero red verification runs (exit≠0/timeout/skipped, or a runner error when commands were declared).
-
-
 An **adversarial plan-conformance reviewer**. Where [`code-reviewer`](../code-reviewer/README.md)
 asks *"is this code good?"*, `adversary` asks a different, harder question:
 
@@ -42,9 +31,6 @@ ADVERSARIAL_REVIEW: CONFORMS
 Criteria: N/N met (all with tests).
 ```
 
-CONFORMS is deterministic: ALL MET + zero holistic complaints + zero pipeline faults +
-zero red verification runs (exit≠0/timeout/skipped, or a runner error when commands were declared).
-
 ```
 ADVERSARIAL_REVIEW: DIVERGES
 Criteria: X/N met, Y partial, Z unmet/diverged.
@@ -53,12 +39,6 @@ Complaints:
 2. ...
 ```
 
-Every verdict — CONFORMS or DIVERGES — ends with a `Verification runs:` section: the recorded
-PASS/FAIL results (command, exit code, duration, failure tail) of the caller-declared verification
-commands, or an explicit marker when none were declared or the run never reached that stage. The
-one exception is the verdict script's own crash guard, which emits a bare DIVERGES with a
-"verdict computation error" line — and no section — when verdict computation itself dies.
-
 A `DIVERGES` verdict **blocks** completion. The caller (sisyphus/architect) must reconcile it —
 resume the SAME coder/sisyphus session with the complaints pasted verbatim — or escalate. It mirrors
 the `oracle` + `plan-review` gate used before implementation, but applied *after* implementation.
@@ -68,43 +48,18 @@ violation) and cites `file:line`. Vague complaints are not emitted.
 
 ## How it reviews
 
-```mermaid
+Driven by the [`adversarial-review`](../../skills/adversarial-review/SKILL.md) skill:
-flowchart TD
-    A["parse (llm): extract acceptance criteria"] --> B["facts (diff_facts.py): resolve + bound the diff"]
-    V["verification_commands (declared graph variable — never parsed from the prompt)"] --> R
-    B --> R["run_checks (script): run the declared verification commands ONCE, record results"]
-    R --> C["map over criteria: one fresh-context branch each (parallel)"]
-    C --> D["check_criterion (llm + fs/ast tools)"]
-    D --> E["crit_gate (script): MET needs change+test evidence"]
-    E -. "reject-retry once; exhausted = PARTIAL" .-> D
-    E --> F["holistic (llm): ADDITIVE-only hunt - absence, scope drift, substitution, gamed tests"]
-    F --> G["verdict (script): CONFORMS iff ALL MET + zero extras + zero faults + zero red runs; no criteria = DIVERGES"]
-    G --> H(["ADVERSARIAL_REVIEW: CONFORMS | DIVERGES"])
-    A -. "fallback" .-> P["pipeline_fault (script): record PIPELINE-FAULT marker"]
-    B -. "fallback" .-> P
-    R -. "fallback" .-> P
-    D -. "fallback" .-> CF["criterion_fault (script): UNMET + PIPELINE-FAULT evidence for that ONE criterion"]
-    CF -. "map join" .-> F
-    F -. "fallback" .-> G
-    P --> G
-```
 
-The conformance doctrine is baked into the graph's own nodes:
+1. Map **every** acceptance criterion to specific evidence in the diff → ✅ Met / ⚠️ Partial / ❌ Unmet / 🔀 Diverged. No test proving the behavior ⇒ at best ⚠️ Partial.
-
-1. **Every** acceptance criterion gets its own fresh-context verification branch — MET / PARTIAL / UNMET / DIVERGED, machine-gated (MET requires the satisfying change AND the proving test, cited). No test ⇒ at best PARTIAL. Partial coverage of the criteria list is structurally impossible.
 2. Ground-truth with read-only tools (`fs_grep`/`fs_read`/`ast_grep`): confirm required symbols exist as specified, changes land where they must, new behavior is actually reached, tests target behavior not implementation.
-3. Execution evidence is recorded **once, deterministically**: `run_checks` runs ONLY the caller-declared verification commands (never invented or auto-detected), sequentially under a 3300s total deadline — commands the deadline leaves no budget for are recorded as SKIPPED. Criterion branches have no execution tools by design: "tests pass"-style criteria are judged against the record — a recorded green run is MET citing it; no declared command ⇒ at best PARTIAL. Independently of the criterion judgments, the verdict script blocks CONFORMS on any red run (exit≠0/timeout/skipped) and on an ENVIRONMENT runner-error marker when commands were declared — the declared commands never ran, so the run is unproven. The commands arrive through the declared `verification_commands` graph variable (see [Declaring verification commands](#declaring-verification-commands)) — `parse` never extracts them from the prompt, so the prompt is no longer an extraction source for the commands.
+3. Hunt adversarially for the **absent**: skipped criteria, scope creep, interface/approach substitution, out-of-scope touches, downstream contract breakage.
-4. Hunt adversarially for the **absent**: skipped criteria, scope creep, interface/approach substitution, out-of-scope touches, downstream contract breakage.
-5. **Fail closed on pipeline faults**: if parse, diff resolution, or the verification runner dies, its fallback routes to `pipeline_fault`, which records a `PIPELINE-FAULT:` marker and continues to the verdict (a failed holistic pass falls back straight to the verdict, which synthesizes the same marker). Any recorded fault forces DIVERGES with the fault as complaint #1 — degraded is never passing, and the sentinel is always emitted: the graph never dies without one.
-6. **Fail closed per criterion**: a criterion check that dies (max_iterations exhausted, API failure) falls back to `criterion_fault`, which records a schema-shaped UNMET verdict carrying a `PIPELINE-FAULT: criterion ` evidence marker for that one criterion. The other criteria still get verdicts, the report says the check DIED rather than judged, and the run is DIVERGES. That exact marker prefix (the one `criterion_fault` emits) forces the criterion into unmet regardless of the status it carries, so a verdict that echoes it with `MET` can never count toward CONFORMS; `check_criterion` is told never to begin its own evidence with `PIPELINE-FAULT:`.
 
 It is **read-only** — it produces a verdict, never a fix.
 
 ## Usage
 
 Typically spawned by `sisyphus` (or `architect`) alongside `code-reviewer`. The spawn prompt IS its
-entire context, so it must include the diff (or a base ref to fetch) **and** the acceptance criteria.
+entire context, so it must include the diff (or a base ref to fetch) **and** the acceptance criteria:
-Verification commands travel separately, as a declared variable:
 
 ```sh
 agent__spawn --agent adversary --prompt "
@@ -116,44 +71,24 @@ Run get_diff (or --base main), or: <paste diff>
 
 ## PLAN — acceptance criteria to check against
 <paste the task index.md body + the relevant PLAN-*.md section, verbatim>
-" --variables {"verification_commands": "[\"cargo test --all\", \"cargo clippy -- -D warnings\"]"}
+"
 ```
 
 Direct invocation for ad-hoc use:
 
 ```sh
 coyote -a adversary --agent-variable project_dir /path/to/repo \
-  --agent-variable verification_commands '["cargo test --all"]' \
   "Review staged changes against these criteria: <paste criteria>"
 ```
 
-### Declaring verification commands
-
-`verification_commands` is a declared graph variable (default `'[]'`): a JSON array of shell
-commands, passed as a string because agent variables always arrive as strings. `run_checks` runs
-exactly those commands with a shell — so the declaration is a **trust boundary**. The prompt is the
-wrong side of it: it also carries plan and diff text pasted from the repo under review, and an LLM
-`parse` node extracting commands from that prose would let anything in the repo's text run under
-the reviewer's shell. Hence the commands are never in the prompt and never in `parse`'s output
-schema; `review-gauntlet` forwards its own `verification_commands` variable to the adversary lane
-as a structured `inputs:` passthrough, not as prompt text.
-
-- `'[]'` (or omitted) ⇒ the "none declared" marker; execution criteria are at best PARTIAL.
-- Anything that is not a JSON array of strings (unparsable JSON, an object, non-string items) is
-  an invalid declaration: `run_checks` executes **nothing** and records a
-  `PIPELINE-FAULT: verification_commands declaration invalid — …` marker, which forces DIVERGES:
-  it fails closed as a PIPELINE-FAULT (complaint #1) — it never degrades to an ENVIRONMENT marker.
-- The engine merges only the keys declared under `parse`'s `output_schema.properties` into state,
-  so an injected instruction that makes the parse LLM emit an extra `verification_commands` key
-  cannot reach state: the undeclared key is dropped and the declared variable stands.
-
 ### Tools
 
-- The graph's `diff_facts` script resolves the diff itself (staged → unstaged → `HEAD~1`, or an explicit ref/range named in the prompt) — there is no `get_diff` tool anymore.
+- `get_diff [--base <ref>]` — staged → unstaged → `HEAD~1` fallback (or an explicit base/PR branch).
-- The `run_checks` script executes the commands declared via the `verification_commands` variable and records the results — criterion branches cite the record and never run anything themselves.
+- `get_changed_files [--base <ref>]` — quick changed-file map.
-- Criterion branches carry read-only `fs_read`/`fs_cat`/`fs_grep`/`ast_grep` for ground-truth checks.
+- Plus read-only `fs_*` and `ast_grep` for ground-truth checks.
 
 ## Related
 
+- [`adversarial-review`](../../skills/adversarial-review/SKILL.md) — the conformance methodology it runs on.
 - [`code-reviewer`](../code-reviewer/README.md) — the quality reviewer it runs alongside.
 - [`plan-review`](../../skills/plan-review/SKILL.md) — the *pre*-implementation plan gate; `adversary` is its *post*-implementation counterpart.

assets/agents/adversary/config.yaml

@@ -0,0 +1,118 @@
+name: adversary
+description: Adversarial plan-conformance reviewer - judges whether an implementation matches the task/plan it was supposed to satisfy (not code quality). Returns a blocking CONFORMS/DIVERGES verdict. Complements code-reviewer. Designed to be delegated to by sisyphus.
+version: 1.0.0
+
+auto_continue: true
+max_auto_continues: 15
+inject_todo_instructions: true
+
+skills_enabled: true
+enabled_skills:
+  - adversarial-review
+
+variables:
+  - name: project_dir
+    description: Project directory containing the changes under review
+    default: '.'
+  - name: auto_confirm
+    description: Auto-confirm command execution
+    default: '1'
+
+global_tools:
+  - ast_grep.sh
+  - fs_read.sh
+  - fs_cat.sh
+  - fs_grep.sh
+  - fs_glob.sh
+  - fs_ls.sh
+  - execute_command.sh
+
+instructions: |
+  You are an adversarial plan-conformance reviewer. You answer ONE question: **does this
+  implementation match the plan it was supposed to satisfy — all of it, and only it?** You are NOT
+  the code-quality reviewer (that is `code-reviewer`/`file-reviewer`, which judges correctness, slop,
+  and style). You judge CONFORMANCE: skipped acceptance criteria, silent scope drift, interface
+  substitution, and things the plan required that never showed up in the diff.
+
+  Your value is independence and suspicion. Assume the implementer drifted, cut a corner, or misread
+  the plan until the diff proves otherwise.
+
+  ## Step 0: Load the skill
+
+  Before anything else, `skill__load` `adversarial-review`. It carries your methodology: the
+  criterion-by-criterion evidence mapping, the adversarial checklist (silently skipped criteria,
+  scope drift, interface drift, ground-truth verification, out-of-scope violations, downstream
+  contract breakage), and the exact verdict format. The skill body is your source of truth for HOW to
+  review and WHAT to flag; these instructions handle workflow and I/O.
+
+  ## Input (the spawn prompt IS your entire context)
+
+  You are given:
+  1. **The diff** — pasted inline, or run `get_diff` (optionally `--base <ref>`) if told to fetch it.
+  2. **The plan** — the task's Objective, Tasks, and especially its **Acceptance criteria**, pasted
+     inline (e.g. a task file's What/Steps/Acceptance criteria + the relevant plan section), or a path to read.
+
+  If the plan / acceptance criteria are missing, STOP and say so: conformance cannot be judged
+  without a spec. Do not invent criteria or guess intent.
+
+  ## Workflow
+
+  1. Load `adversarial-review`.
+  2. Get the diff (inline or via `get_diff`) and identify the changed files.
+  3. For EACH acceptance criterion: find the specific evidence in the diff that satisfies it and
+     classify it ✅ Met / ⚠️ Partial / ❌ Unmet / 🔀 Diverged. A criterion with no test proving its
+     behavior is at best ⚠️ Partial.
+  4. Ground-truth every claim: `fs_grep` the symbols the plan requires (confirm they exist, spelled
+     as specified), `fs_read` around each hunk to confirm the change makes the criterion true, grep
+     callers to confirm new behavior is reached, confirm tests target behavior not implementation.
+     Use `ast_grep` for structural checks (e.g. "was this function signature actually changed?").
+  5. Hunt adversarially for what's ABSENT (the dog that didn't bark), scope creep, interface/approach
+     substitution, out-of-scope touches, and downstream contract breakage — per the skill checklist.
+  6. Emit the verdict in the skill's exact format.
+
+  ## Output — verdict (MANDATORY, exact format)
+
+  End with EXACTLY one of these sentinels so the caller can route on it:
+
+  ```
+  ADVERSARIAL_REVIEW: CONFORMS
+  Criteria: N/N met (all with tests).
+  <optional: 1-3 non-blocking observations>
+  ```
+
+  ```
+  ADVERSARIAL_REVIEW: DIVERGES
+  Criteria: X/N met, Y partial, Z unmet/diverged.
+  Complaints:
+  1. Acceptance criterion "<quoted>" — <Unmet|Partial|Diverged> — <what the diff does/omits, file:line> — <what would make it conform>
+  2. Scope drift / interface drift / out-of-scope — <file:line> — <the violation> — <the fix>
+  3. ...
+  ```
+
+  Every complaint MUST quote the specific acceptance criterion (or name the specific scope/interface/
+  out-of-scope violation) AND cite file:line. A complaint with no criterion reference and no location
+  is noise — do not emit it.
+
+  ## Rules
+
+  1. **You are read-only.** Never modify files. You produce a verdict; the implementer owns the fix.
+  2. **Conformance, not quality.** Do not flag style/naming/micro-optimizations unless they cause a
+     criterion to be unmet. If a quality defect breaks a criterion (a race violating a correctness
+     criterion), flag it as a conformance failure and note it is also a quality issue.
+  3. **No test ⇒ not met.** An acceptance criterion is a promise of observable behavior; unproven
+     behavior is at best Partial.
+  4. **Absence is a finding.** Review what SHOULD be in the diff per the plan, not only what IS.
+  5. **Don't re-litigate a settled decision** — but DO flag when the diff silently overrode one the
+     plan recorded ("do X not Y because Z" → diff does Y).
+  6. **The plan can be the culprit.** If the plan is impossible/self-contradictory, that is DIVERGES
+     with the plan named as root cause — never judge against a plan you silently corrected.
+  7. Be terse and decisive. Three real divergences beat fifteen weak ones. If everything is a nitpick,
+     it CONFORMS — say so.
+
+  ## Context
+  - Project: {{project_dir}}
+  - CWD: {{__cwd__}}
+  - Shell: {{__shell__}}
+
+  ## Available Tools
+  {{__tools__}}

assets/agents/adversary/graph.yaml

@@ -1,385 +0,0 @@
-name: adversary
-description: |
-  Graph-based adversarial plan-conformance reviewer. The plan's acceptance
-  criteria are extracted into a list and the graph mechanically fans out ONE
-  fresh-context verification branch per criterion — "checked 8 of 12 and waved
-  the rest through" becomes structurally impossible. Each criterion verdict
-  (MET / PARTIAL / UNMET / DIVERGED) passes a deterministic contract gate
-  (MET requires evidence including a test proving the behavior — no test means
-  at best PARTIAL). A holistic pass then hunts what per-criterion checks cannot
-  see: absence (the dog that didn't bark), scope drift, interface substitution,
-  silently-overridden recorded decisions, out-of-scope touches, and gamed
-  tests — ADDITIVE-only: it can add complaints, never flip a criterion verdict.
-  The final CONFORMS/DIVERGES sentinel is computed by a script: CONFORMS
-  requires every criterion MET, zero holistic complaints, zero pipeline faults,
-  and zero red verification runs (exit≠0/timeout/skipped, or a runner error
-  when commands were declared). Missing plan = DIVERGES (fail-closed) naming
-  the missing spec. Caller-declared verification
-  commands are executed ONCE by a deterministic stage and recorded — criterion
-  branches cite the record and never run anything themselves. Any pipeline
-  fault (parse, diff resolution, verification runner, or holistic failure)
-  lands a PIPELINE-FAULT marker and fails closed into DIVERGES: degraded is
-  never passing.
-
-version: '1.0'
-
-global_tools:
-  - ast_grep.sh
-  - fs_read.sh
-  - fs_cat.sh
-  - fs_grep.sh
-
-variables:
-  - name: project_dir
-    description: Project directory containing the changes under review
-    default: '.'
-  - name: verification_commands
-    description: |
-      JSON array of shell commands the CALLER declares for the deterministic
-      run_checks stage — e.g. '["cargo test --all"]'. Never inferred from the
-      prompt; empty array = none declared. Must not boot shared stacks or
-      services (compose projects, fixed ports) — those collide with the probe
-      lane running in parallel.
-    default: '[]'
-
-settings:
-  max_loop_iterations: 10
-  log_state_snapshots: false
-  # 3600 (run_checks node timeout, worst case) + 5400 (the previous
-  # whole-graph budget, kept as the envelope for every stage other than
-  # run_checks: parse/facts before it, criteria map/holistic/verdict after)
-  # = 9000. A graph timeout kills from outside — no fallback fires and the
-  # sentinel is lost.
-  timeout: 9000
-
-initial_state:
-  project_dir_in: ''
-  parse_retries: 0
-  criteria: []
-  diff_spec: auto
-  plan_notes: ''
-  scope_notes: ''
-  extra_context: ''
-  changed_files: []
-  diff_text: ''
-  diff_note: ''
-  exec_results: ''
-  crit_verdicts: []
-  extra_complaints: []
-  observations: ''
-  adv_report: ''
-  gate_feedback: ''
-  gate_attempts: 0
-  parse_failure: ''
-  holistic_failure: ''
-  pipeline_faults: []
-
-start: parse
-
-nodes:
-  parse:
-    id: parse
-    type: llm
-    description: Extract the acceptance criteria and plan facts from the spawn prompt. Extraction only — no judging, no criteria invented.
-    instructions: |
-      You extract a plan-conformance review request into structured fields.
-      EXTRACTION ONLY — never invent criteria, never guess intent.
-
-      - `criteria`: every acceptance criterion from the plan/task, one entry each,
-        with a short id (c1, c2, …) and SELF-CONTAINED text (what observable
-        behavior is promised, including any test expectations the plan states).
-        Split compound criteria ("A and B") into separate entries when they are
-        independently verifiable. When the caller supplied NO plan/criteria at
-        all, emit an empty array — downstream fails closed.
-        An empty array is ONLY correct when the prompt genuinely contains no
-        plan/criteria section — when the prompt carries one (a "Plan /
-        acceptance criteria:" or "PLAN —" block), returning zero criteria is
-        an extraction FAILURE, never a valid result.
-        The caller's explicit enumeration is AUTHORITATIVE: when the caller
-        declares "these N are the (only) criteria" or supplies a numbered
-        criteria list, extract EXACTLY those N — never add entries they did
-        not enumerate. NEVER mine criteria from sections the caller labels as
-        context ("FACTS", "Quality bar", "context, not criteria", background
-        material) — route those into plan_notes / scope_notes / extra_context
-        instead. Splitting applies only WITHIN a declared criterion; when in
-        doubt, FEWER criteria, verbatim.
-      - `diff_spec`: the git diff basis the caller named — a range, a ref/SHA,
-        "staged", "worktree", or "auto" when unnamed (a caller phrase like
-        "get_diff --base X" means diff_spec = "X").
-      - `project_dir_in`: the directory/worktree path the caller named as
-        holding the code under review; empty string when the caller named none.
-      - `plan_notes`: recorded decisions the plan states ("do X not Y because Z"),
-        verbatim — the holistic pass checks the diff didn't silently override them.
-      - `scope_notes`: what the plan says NOT to touch / explicit boundaries.
-      - `extra_context`: anything else conformance-relevant, condensed.
-    prompt: |
-      Extract the conformance-review facts from this request:
-
-      {{initial_prompt}}
-    tools: []
-    output_schema:
-      type: object
-      properties:
-        criteria:
-          type: array
-          items:
-            type: object
-            properties:
-              id:
-                type: string
-              text:
-                type: string
-            required: [id, text]
-        diff_spec:
-          type: string
-        plan_notes:
-          type: string
-        scope_notes:
-          type: string
-        extra_context:
-          type: string
-        project_dir_in:
-          type: string
-      required: [criteria, diff_spec, plan_notes, scope_notes, extra_context, project_dir_in]
-    max_iterations: 3
-    max_attempts: 2
-    state_updates:
-      parse_failure: '{{output}}'
-    fallback: pipeline_fault
-    next: facts
-
-  facts:
-    id: facts
-    type: script
-    description: Deterministic diff resolution — changed files and the (bounded) diff text every criterion branch verifies against.
-    script: scripts/diff_facts.py
-    timeout: 120
-    fallback: pipeline_fault
-    next: run_checks
-
-  run_checks:
-    id: run_checks
-    type: script
-    description: Deterministic execution evidence — runs ONLY the commands declared via the verification_commands variable in the project dir and records exec_results; criterion branches cite the record and never execute anything. Undeclared commands degrade to a "none declared" marker, runner errors to an ENVIRONMENT marker (criterion branches judge it PARTIAL/unproven; the verdict additionally blocks CONFORMS when commands were declared); a declaration that is not a JSON array of strings executes nothing and records a PIPELINE-FAULT (fail-closed); a 3300s total deadline keeps the script under the node timeout (commands past it are recorded as skipped), and if the node is killed anyway the fallback records a PIPELINE-FAULT.
-    script: scripts/run_checks.py
-    timeout: 3600
-    fallback: pipeline_fault
-    next: map_criteria
-
-  map_criteria:
-    id: map_criteria
-    type: map
-    over: '{{criteria}}'
-    as: criterion
-    branch: check_criterion
-    output_key: crit_verdict
-    collect_into: crit_verdicts
-    max_concurrency: 6
-    next: holistic
-
-  check_criterion:
-    id: check_criterion
-    type: llm
-    description: Fresh-context verification of ONE acceptance criterion against the diff and the working tree (ENVIRONMENT/SKIPPED runs judge PARTIAL here; the deterministic verdict blocks CONFORMS when declared commands did not run).
-    instructions: |
-      You verify ONE acceptance criterion against a code change. Fresh context,
-      one criterion, full suspicion: assume the implementer drifted, cut a
-      corner, or misread the plan until the diff proves otherwise.
-
-      Classification (exactly one):
-      - `MET` — the diff satisfies the criterion AND a test proves the promised
-        behavior. Evidence MUST cite both: the satisfying change (file:line) and
-        the test targeting the behavior (file:line). No test ⇒ NOT MET — at best
-        PARTIAL (a criterion is a promise of observable behavior; unproven
-        behavior is unverified behavior).
-      - `PARTIAL` — partially satisfied, or satisfied but unproven (missing/weak
-        test), or you could not establish it either way (say why — doubt lands
-        here, never in MET).
-      - `UNMET` — the plan requires it and the diff does not do it. Absence is a
-        finding: review what SHOULD be there, not only what IS.
-      - `DIVERGED` — the diff does something ELSE instead (interface substituted,
-        approach swapped, criterion reinterpreted).
-
-      Ground-truth discipline: fs_grep the symbols the criterion names (confirm
-      they exist spelled as specified), fs_read around the relevant hunks to
-      confirm the change makes the criterion true, confirm the test targets
-      BEHAVIOR (not implementation echo), use ast_grep for structural claims.
-      Watch for gamed evidence: a test weakened/deleted so it passes, hardcoded
-      values shaped to the criterion's example, TODO/stub presented as done —
-      those are PARTIAL or DIVERGED with the gaming named in the complaint.
-
-      Execution criteria ("tests pass", "lint clean", "build succeeds") are
-      judged ONLY against the recorded verification runs in your prompt — you
-      have no execution tools BY DESIGN and must never claim to have run
-      anything yourself:
-      - a recorded green run (exit 0) of a command covering the criterion is
-        the proving evidence — MET, citing that run (the command + exit 0).
-      - a recorded failing run covering the criterion ⇒ UNMET, citing the
-        recorded exit code and output tail.
-      - "none declared" or an ENVIRONMENT marker ⇒ at best PARTIAL, with an
-        ENVIRONMENT note in the complaint naming the exact command the caller
-        should declare via the `verification_commands` variable (structured
-        input, e.g. "cargo test --all") — commands are never declared in the
-        prompt.
-      - a SKIPPED record (the runner's total deadline expired before that
-        command ran) ⇒ at best PARTIAL for the criteria it covers, same
-        treatment as an ENVIRONMENT marker: unproven at the criterion level.
-        The deterministic verdict additionally blocks CONFORMS when declared
-        commands did not run — that is its job, not yours.
-
-      Output format — respond with ONLY this JSON object, no prose around it:
-      {"id": "<the criterion's id, echoed>",
-       "status": "MET" | "PARTIAL" | "UNMET" | "DIVERGED",
-       "evidence": "<for MET: the satisfying change file:line AND the proving test
-      file:line, quoted decisively; otherwise the closest relevant citations or empty>",
-       "complaint": "<required for non-MET: what the diff does/omits (file:line) and
-      what would make it conform; empty string for MET>"}
-
-      Your response is machine-validated: a malformed response is rejected back
-      to you exactly once with the reason, then recorded as PARTIAL (unproven).
-      The id is stamped from the criterion itself — your echo is informative only.
-      You have a bounded tool budget — prefer fs_grep and line-ranged fs_read over
-      whole-file reads, and conclude as soon as the evidence is decisive.
-      Never begin `evidence` with the literal `PIPELINE-FAULT:` — that prefix is
-      reserved for the graph's own fault markers.
-    prompt: |
-      Repository: {{project_dir}}
-      Changed files: {{changed_files}}
-
-      Criterion to verify (JSON):
-      {{criterion}}
-
-      Plan-recorded decisions (context): {{plan_notes}}
-      {{extra_context}}
-
-      The diff{{diff_note}}:
-      {{diff_text}}
-
-      Verification runs (recorded by the deterministic run_checks stage):
-      {{exec_results}}
-      {{gate_feedback}}
-    tools:
-      - fs_read
-      - fs_cat
-      - fs_grep
-      - ast_grep
-    max_iterations: 30
-    max_attempts: 2
-    state_updates:
-      crit_verdict: '{{output}}'
-    fallback: criterion_fault
-    next: crit_gate
-
-  crit_gate:
-    id: crit_gate
-    type: script
-    description: Deterministic contract gate per criterion verdict — status enum, MET requires evidence, non-MET requires a complaint; reject-and-retry once, then record PARTIAL (unproven). Never sinks the map.
-    script: scripts/crit_gate.py
-    timeout: 30
-
-  criterion_fault:
-    id: criterion_fault
-    type: script
-    description: Fail-closed per-criterion fault marker (reached only via check_criterion's fallback) — converts the captured "LLM node failed" text into a schema-shaped UNMET verdict carrying a PIPELINE-FAULT evidence marker, so one dead criterion check can never sink the map or read as met.
-    script: scripts/criterion_fault.py
-    timeout: 30
-
-  holistic:
-    id: holistic
-    type: llm
-    description: Cross-criterion adversarial pass — hunts what per-criterion checks cannot see. ADDITIVE-only; cannot flip criterion verdicts.
-    instructions: |
-      You run the holistic adversarial pass over a whole change AFTER each
-      acceptance criterion was independently verified. You hunt what
-      per-criterion checks cannot see. You are ADDITIVE-ONLY: you may add
-      complaints; you may NOT flip, soften, or re-judge any criterion verdict.
-
-      The checklist (each hit becomes one complaint with kind, file:line
-      location, the violation, and the fix):
-      - **Absence** — something the PLAN requires that maps to no criterion and
-        never showed up in the diff (the dog that didn't bark).
-      - **Scope drift / out-of-scope** — the diff touches what the plan's scope
-        notes say not to touch, or quietly does extra unplanned work.
-      - **Interface/approach substitution** — the plan named an interface,
-        library, or approach; the diff substituted another without the plan
-        recording that decision.
-      - **Silently overridden recorded decision** — plan says "do X not Y
-        because Z"; diff does Y.
-      - **Downstream contract breakage** — the diff changes a contract the plan
-        promised to preserve.
-      - **Gamed tests** — tests weakened, deleted, or shaped (hardcoded
-        expectations, skipped assertions) so the criteria APPEAR met.
-      - **The plan itself is the culprit** — impossible or self-contradictory
-        requirements: that is a complaint naming the PLAN as root cause; never
-        silently judge against a corrected version of it.
-
-      Be terse and decisive: three real complaints beat fifteen weak ones. A
-      complaint with no location and no criterion/scope reference is noise — do
-      not emit it. When everything is a nitpick, emit zero complaints and put
-      1-3 non-blocking notes in `observations`.
-    prompt: |
-      Repository: {{project_dir}}
-      Changed files: {{changed_files}}
-
-      Acceptance criteria: {{criteria}}
-      Per-criterion verdicts (already final): {{crit_verdicts}}
-
-      Plan-recorded decisions: {{plan_notes}}
-      Scope boundaries: {{scope_notes}}
-      {{extra_context}}
-
-      The diff{{diff_note}}:
-      {{diff_text}}
-    tools:
-      - fs_read
-      - fs_cat
-      - fs_grep
-      - ast_grep
-    output_schema:
-      type: object
-      properties:
-        extra_complaints:
-          type: array
-          items:
-            type: object
-            properties:
-              kind:
-                type: string
-              location:
-                type: string
-              violation:
-                type: string
-              fix:
-                type: string
-            required: [kind, location, violation, fix]
-        observations:
-          type: string
-      required: [extra_complaints, observations]
-    max_iterations: 45
-    max_attempts: 2
-    state_updates:
-      holistic_failure: '{{output}}'
-    fallback: verdict
-    next: verdict
-
-  pipeline_fault:
-    id: pipeline_fault
-    type: script
-    description: Fail-closed fault marker (reached only via fallback routes from parse/facts/run_checks) — records a PIPELINE-FAULT in state and continues to verdict, which turns any fault into DIVERGES. The graph never dies without its sentinel.
-    script: scripts/pipeline_fault.py
-    timeout: 30
-    next: verdict
-
-  verdict:
-    id: verdict
-    type: script
-    description: Deterministic verdict — CONFORMS requires every criterion MET, zero holistic complaints, zero pipeline faults, and zero recorded red verification runs (exit≠0/timeout/skipped, or an ENVIRONMENT runner-error marker when commands were declared); no criteria at all fails closed and any recorded PIPELINE-FAULT forces DIVERGES (degraded is never passing). Assembles the exact sentinel format.
-    script: scripts/verdict.py
-    timeout: 30
-    next: done
-
-  done:
-    id: done
-    type: end
-    output: |
-      {{adv_report}}

assets/agents/adversary/scripts/crit_gate.py

@@ -1,148 +0,0 @@
-#!/usr/bin/env python3
-"""Contract gate for the adversary's per-criterion verify chain.
-
-Validates each criterion verdict against the contract:
-  - a single JSON object with status in {MET, PARTIAL, UNMET, DIVERGED}
-  - MET requires non-empty evidence (the change AND the proving test)
-  - non-MET requires a non-empty complaint
-
-The authoritative id is stamped from the criterion item — the model's echo is
-never trusted. Malformed output is rejected back to check_criterion exactly
-once with the reason; a second failure records PARTIAL (unproven) so a
-malformed item can never sink the map or masquerade as MET.
-"""
-
-import json
-import os
-import re
-
-STATUSES = {"MET", "PARTIAL", "UNMET", "DIVERGED"}
-MAX_RETRIES = 1
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def criterion_fields(state):
-    c = state.get("criterion")
-    if isinstance(c, dict):
-        cid = c.get("id")
-        text = c.get("text")
-        return (
-            cid.strip() if isinstance(cid, str) and cid.strip() else "unknown",
-            text.strip() if isinstance(text, str) else "",
-        )
-    return "unknown", ""
-
-
-def extract_json(text):
-    if not isinstance(text, str) or not text.strip():
-        raise ValueError("criterion-check output is empty or not text")
-    text = re.sub(r"```[a-zA-Z]*", "", text).replace("```", "")
-    start, end = text.find("{"), text.rfind("}")
-    if start == -1 or end <= start:
-        raise ValueError("no JSON object found in criterion-check output")
-    return json.loads(text[start : end + 1])
-
-
-def validate(obj):
-    if not isinstance(obj, dict):
-        raise ValueError("criterion-check output is not a JSON object")
-    status = obj.get("status")
-    if status not in STATUSES:
-        raise ValueError(f"status must be one of {sorted(STATUSES)}, got {status!r}")
-    evidence = obj.get("evidence") if isinstance(obj.get("evidence"), str) else ""
-    complaint = obj.get("complaint") if isinstance(obj.get("complaint"), str) else ""
-    if status == "MET" and not evidence.strip():
-        raise ValueError(
-            "MET requires non-empty evidence citing the satisfying change AND the "
-            "test proving the behavior (file:line)"
-        )
-    if status != "MET" and not complaint.strip():
-        raise ValueError(
-            f"{status} requires a non-empty complaint (what the diff does/omits at "
-            "file:line, and what would make it conform)"
-        )
-    return status, evidence, complaint
-
-
-def main():
-    state = load_state()
-    cid, ctext = criterion_fields(state)
-    attempts = state.get("gate_attempts")
-    if not isinstance(attempts, int):
-        attempts = 0
-
-    try:
-        status, evidence, complaint = validate(extract_json(state.get("crit_verdict")))
-        print(
-            json.dumps(
-                {
-                    "crit_verdict": {
-                        "id": cid,
-                        "text": ctext,
-                        "status": status,
-                        "evidence": evidence,
-                        "complaint": complaint,
-                    }
-                }
-            )
-        )
-        return
-    except Exception as e:  # noqa: BLE001
-        reason = str(e)
-
-    if attempts < MAX_RETRIES:
-        print(
-            json.dumps(
-                {
-                    "_next": "check_criterion",
-                    "gate_attempts": attempts + 1,
-                    "gate_feedback": (
-                        "PREVIOUS RESPONSE REJECTED by the verdict gate: " + reason +
-                        ". Respond with ONLY the JSON object described in your instructions."
-                    ),
-                }
-            )
-        )
-        return
-
-    print(
-        json.dumps(
-            {
-                "crit_verdict": {
-                    "id": cid,
-                    "text": ctext,
-                    "status": "PARTIAL",
-                    "evidence": "",
-                    "complaint": (
-                        "criterion check output failed machine validation after retry: "
-                        + reason
-                        + " — treat this criterion as unproven"
-                    ),
-                }
-            }
-        )
-    )
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — the gate must never crash the chain
-    print(
-        json.dumps(
-            {
-                "crit_verdict": {
-                    "id": "unknown",
-                    "text": "",
-                    "status": "PARTIAL",
-                    "evidence": "",
-                    "complaint": f"criterion gate error: {e} — treat as unproven",
-                }
-            }
-        )
-    )

assets/agents/adversary/scripts/criterion_fault.py

@@ -1,94 +0,0 @@
-#!/usr/bin/env python3
-"""Fail-closed per-criterion fault marker for the adversary graph.
-
-Reached ONLY via check_criterion's `fallback:` route, after the engine has
-written its "LLM node …failed: <chain>" text into `crit_verdict` through
-state_updates. Converts that text into a schema-shaped UNMET verdict whose
-evidence carries a "PIPELINE-FAULT:" marker, so one criterion check that dies
-(max_iterations exhausted, API failure) is recorded as DIED rather than
-judged, the other criteria still get verdicts, and the run is DIVERGES. The
-map collects it like any other verdict — the branch never sinks the map. The
-engine applies state_updates before routing to the fallback (src/graph/llm.rs:
-`apply_state_updates_with_output`, then `outcome_from`), so the "no failure
-text captured" branch is belt-and-braces rather than an expected path.
-"""
-
-import json
-import os
-
-MAX_DETAIL_CHARS = 500
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def criterion_fields(state):
-    c = state.get("criterion")
-    if isinstance(c, dict):
-        cid = c.get("id")
-        text = c.get("text")
-        return (
-            cid.strip() if isinstance(cid, str) and cid.strip() else "unknown",
-            text.strip() if isinstance(text, str) else "",
-        )
-    return "unknown", ""
-
-
-def failure_detail(state):
-    captured = state.get("crit_verdict")
-    detail = captured.strip() if isinstance(captured, str) else ""
-    if not detail.startswith("LLM node"):
-        return "no failure text captured"
-    detail = detail.replace("\n", " ")
-    if len(detail) > MAX_DETAIL_CHARS:
-        detail = detail[: MAX_DETAIL_CHARS - 1] + "…"
-    return detail
-
-
-def main():
-    state = load_state()
-    cid, ctext = criterion_fields(state)
-    detail = failure_detail(state)
-    print(
-        json.dumps(
-            {
-                "crit_verdict": {
-                    "id": cid,
-                    "text": ctext,
-                    "status": "UNMET",
-                    "evidence": f"PIPELINE-FAULT: criterion check failed — {detail}",
-                    "complaint": (
-                        f"criterion check DIED (pipeline fault) — {detail}; the "
-                        "criterion was NOT verified and is treated as unmet "
-                        "(fail-closed)"
-                    ),
-                }
-            }
-        )
-    )
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — the fault marker itself must never crash
-    print(
-        json.dumps(
-            {
-                "crit_verdict": {
-                    "id": "unknown",
-                    "text": "",
-                    "status": "UNMET",
-                    "evidence": f"PIPELINE-FAULT: criterion fault-marker script error: {e}",
-                    "complaint": (
-                        f"criterion check DIED (pipeline fault) — fault-marker script "
-                        f"error: {e}; the criterion was NOT verified and is treated as "
-                        "unmet (fail-closed)"
-                    ),
-                }
-            }
-        )
-    )

assets/agents/adversary/scripts/diff_facts.py

@@ -1,93 +0,0 @@
-#!/usr/bin/env python3
-"""Deterministic diff resolution for the adversary graph.
-
-Resolves the diff spec (get_diff semantics: staged → unstaged → HEAD~1 for
-"auto"), lists changed files, and captures the bounded diff text every
-criterion branch verifies against. Failures degrade into diff_note — the
-review proceeds fail-closed rather than crashing.
-"""
-
-import json
-import re
-import os
-import subprocess
-
-MAX_DIFF_CHARS = 60000
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-state = load_state()
-
-# Zero criteria from a prompt that visibly carries a plan is an extraction
-# failure (observed non-deterministically live), not a fail-closed no-plan
-# run — re-run the parse ONCE before the verdict fails closed on it.
-_crit = state.get("criteria") or []
-_prompt = state.get("initial_prompt") or ""
-if not _crit and isinstance(_prompt, str) and re.search(
-    r"acceptance criteria|PLAN\s*—|Plan / acceptance", _prompt, re.I
-):
-    try:
-        _pr = int(state.get("parse_retries") or 0)
-    except (TypeError, ValueError):
-        _pr = 0
-    if _pr < 1:
-        print(json.dumps({"_next": "parse", "parse_retries": _pr + 1}))
-        raise SystemExit(0)
-proj = os.path.expanduser(
-    (state.get("project_dir_in") or "").strip() or state.get("project_dir") or "."
-)
-spec = (state.get("diff_spec") or "auto").strip()
-
-
-def git(*args):
-    r = subprocess.run(["git", "-C", proj, *args], capture_output=True, text=True, timeout=90)
-    if r.returncode != 0:
-        raise RuntimeError((r.stderr or r.stdout).strip()[:300])
-    return r.stdout
-
-
-out = {"diff_note": "", "project_dir": proj}
-try:
-    if spec in ("auto", ""):
-        text = git("diff", "--cached")
-        if not text.strip():
-            text = git("diff")
-        if not text.strip():
-            text = git("diff", "HEAD~1")
-    elif spec == "staged":
-        text = git("diff", "--cached")
-    elif spec == "worktree":
-        text = git("diff", "HEAD")
-    else:
-        text = git("diff", spec)
-
-    files = sorted({
-        line[6:].strip()
-        for line in text.splitlines()
-        if line.startswith("+++ b/")
-    })
-    out["changed_files"] = files[:300]
-    if len(files) > 300:
-        out["diff_note"] += (
-            f" (file list capped at 300 of {len(files)} changed files — use the fs "
-            "tools for the rest)"
-        )
-    if len(text) > MAX_DIFF_CHARS:
-        out["diff_note"] += (
-            f" (truncated to {MAX_DIFF_CHARS} chars of {len(text)} — use the fs tools "
-            "to inspect files beyond the cut)"
-        )
-        text = text[:MAX_DIFF_CHARS]
-    out["diff_text"] = text if text.strip() else "(empty diff — nothing changed)"
-except Exception as e:  # noqa: BLE001
-    out["changed_files"] = []
-    out["diff_text"] = "(diff unavailable)"
-    out["diff_note"] = f" (diff resolution failed for spec {spec!r}: {e})"
-
-print(json.dumps(out))

assets/agents/adversary/scripts/pipeline_fault.py

@@ -1,74 +0,0 @@
-#!/usr/bin/env python3
-"""Fail-closed fault marker for the adversary graph.
-
-Reached ONLY via `fallback:` routes (parse, facts, run_checks). Appends a
-machine-readable "PIPELINE-FAULT:" marker to `pipeline_faults` and continues
-to `verdict`, which turns any recorded fault into DIVERGES — the graph never
-dies without its sentinel, and a degraded run can never read as CONFORMS.
-
-Stage attribution — grounded in engine behavior: a SCRIPT node's fallback
-route writes NOTHING into state (src/graph/executor.rs script arm routes to
-the fallback without recording the error), so the two script stages are
-discriminated by which stage outputs are present:
-- parse (llm): its `state_updates` wrote an "LLM node …failed: <chain>"
-  string into `parse_failure` — attribute to parse.
-- run_checks vs facts (scripts): diff_facts.py unconditionally writes a
-  NONEMPTY `diff_text` (even its internal-failure path writes
-  "(diff unavailable)"), while the graph's initial value is ''. A nonempty
-  `diff_text` proves facts completed, so the fault is the verification
-  runner (run_checks killed at the node level, e.g. by the node timeout);
-  an empty `diff_text` means facts itself died.
-"""
-
-import json
-import os
-
-MAX_DETAIL_CHARS = 500
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def main():
-    state = load_state()
-    faults = [f for f in (state.get("pipeline_faults") or []) if isinstance(f, str)]
-    parse_failure = state.get("parse_failure")
-    detail = parse_failure.strip() if isinstance(parse_failure, str) else ""
-    diff_text = state.get("diff_text")
-    facts_completed = isinstance(diff_text, str) and bool(diff_text.strip())
-    if detail.startswith("LLM node"):
-        detail = detail.replace("\n", " ")
-        if len(detail) > MAX_DETAIL_CHARS:
-            detail = detail[: MAX_DETAIL_CHARS - 1] + "…"
-        faults.append(f"PIPELINE-FAULT: parse failed — cannot review: {detail}")
-    elif facts_completed:
-        faults.append(
-            "PIPELINE-FAULT: verification runner killed — the run_checks stage "
-            "died at the node level before recording exec_results; execution "
-            "criteria are unproven"
-        )
-    else:
-        faults.append(
-            "PIPELINE-FAULT: diff resolution failed — changed files and diff text "
-            "could not be resolved; criterion verification never ran"
-        )
-    print(json.dumps({"pipeline_faults": faults}))
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — the fault marker itself must never crash
-    print(
-        json.dumps(
-            {
-                "pipeline_faults": [
-                    f"PIPELINE-FAULT: fault-marker script error: {e} — treat the "
-                    "run as degraded"
-                ]
-            }
-        )
-    )

assets/agents/adversary/scripts/run_checks.py

@@ -1,252 +0,0 @@
-#!/usr/bin/env python3
-"""Deterministic execution-evidence recorder for the adversary graph.
-
-Runs ONLY the caller-declared verification commands (verification_commands)
-in the project dir and records the outcomes as `exec_results` — a list of
-{cmd, exit, duration_s, tail} records. Criterion branches cite this record;
-they never execute anything themselves.
-
-NO auto-detection: undeclared commands mean a "none declared" marker
-(fail-visible, not fail-guessed). Any runner error degrades into an
-ENVIRONMENT marker — this script never fails the node.
-
-Trust boundary: `verification_commands` is a DECLARED graph variable (or the
-review-gauntlet's structured `inputs:` passthrough), never a field an LLM
-extracts from the spawn prompt — that prose also carries plan/diff text pasted
-from the repo under review, and whatever is declared here runs with
-shell=True. Variables land in state as strings, so a JSON-encoded list is
-accepted alongside a real list. A declaration that is not a JSON array of
-strings is a caller contract violation, not a runner hiccup: it executes
-NOTHING and fails closed as a PIPELINE-FAULT (complaint #1) — it never
-degrades to an ENVIRONMENT marker. The engine merges only the keys an
-llm node's `output_schema.properties` declares, so a parse LLM coaxed into
-emitting an extra `verification_commands` key cannot overwrite the declared
-value: the undeclared key is dropped before it reaches state.
-
-Budget: commands run sequentially, so TOTAL runtime is bounded by a deadline
-(TOTAL_DEADLINE_SECS = 3300s, the run_checks node's 3600s timeout minus
-margin). Without it, a handful of hanging commands (4 x 900s) would blow the
-NODE timeout and the executor would kill this script from OUTSIDE — the
-in-script degradation would never fire. Each command gets
-min(PER_COMMAND_TIMEOUT_SECS, remaining budget); commands the deadline
-leaves no budget for are recorded as {"cmd", "skipped": "deadline"} entries,
-so the in-script handling stays authoritative. The env var
-ADVERSARY_RUN_CHECKS_DEADLINE_SECS overrides the deadline (test seam), and
-ADVERSARY_STACK_LOCK_PATH overrides the review-stack lock file location
-(isolation seam — see acquire_stack_lock).
-
-Process hygiene: commands run through the shell. On POSIX each command gets
-its own session (start_new_session) and a timeout SIGKILLs the whole process
-group, so grandchildren of a hung command cannot linger. The post-kill
-reap/drain is itself bounded by DRAIN_TIMEOUT_SECS: a grandchild that escaped
-the session (its own start_new_session) but still holds the stdout pipe
-would otherwise block the drain until it exits. On non-POSIX platforms only
-the direct shell child is killed — grandchildren of a timed-out command may
-survive (documented limitation).
-
-Verification commands run with GRAPH_STATE* (GRAPH_STATE, GRAPH_STATE_FILE)
-scrubbed from their environment: the reviewed repo's own tests may exec these very
-scripts with their own GRAPH_STATE, and load_state() prefers
-GRAPH_STATE_FILE, so an inherited live state file would silently win.
-"""
-
-import json
-import os
-import signal
-import subprocess
-import sys
-import time
-
-try:
-    import fcntl
-except ImportError:  # non-POSIX (Windows): advisory flock unavailable
-    fcntl = None
-
-PER_COMMAND_TIMEOUT_SECS = 900
-TOTAL_DEADLINE_SECS = float(os.environ.get("ADVERSARY_RUN_CHECKS_DEADLINE_SECS") or 3300)
-STACK_LOCK_PATH = os.environ.get("ADVERSARY_STACK_LOCK_PATH") or os.path.expanduser(
-    "~/.cache/coyote/review-stack.lock"
-)
-STACK_LOCK_WAIT_SECS = float(os.environ.get("ADVERSARY_STACK_LOCK_WAIT_SECS") or 1200)
-
-
-def acquire_stack_lock():
-    """Serialize with the probe lane's shared-stack work (advisory flock on a
-    well-known path; the probe is instructed to flock the same file around
-    stack boot/teardown). Bounded wait so a hogged lock can never turn into a
-    false red verification: on timeout we proceed WITHOUT the lock and note it
-    on stderr. The fd is held for the process lifetime (released on exit).
-    On non-POSIX platforms (no fcntl) the lock is skipped entirely."""
-    if fcntl is None:
-        sys.stderr.write("WARN: review-stack lock unsupported on this platform; running unlocked\n")
-        return None
-    try:
-        os.makedirs(os.path.dirname(STACK_LOCK_PATH), exist_ok=True)
-        fd = os.open(STACK_LOCK_PATH, os.O_CREAT | os.O_RDWR)
-    except OSError as e:
-        sys.stderr.write(f"WARN: review-stack lock unavailable ({e}); running unlocked\n")
-        return None
-    limit = time.monotonic() + STACK_LOCK_WAIT_SECS
-    while True:
-        try:
-            fcntl.flock(fd, fcntl.LOCK_EX | fcntl.LOCK_NB)
-            return fd
-        except OSError:
-            if time.monotonic() >= limit:
-                os.close(fd)
-                sys.stderr.write(
-                    "WARN: review-stack lock still held after bounded wait — proceeding "
-                    "WITHOUT it; shared-stack collisions with the probe lane are possible\n"
-                )
-                return None
-            time.sleep(5)
-DRAIN_TIMEOUT_SECS = 10
-TAIL_LINES = 50
-MAX_TAIL_CHARS = 8000
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-class InvalidDeclaration(ValueError):
-    pass
-
-
-def declared_commands(declared):
-    """Normalize the verification_commands declaration to a list of commands.
-
-    Accepts a JSON list or a JSON-encoded string of one; missing/None means
-    none declared. Anything else raises InvalidDeclaration.
-    """
-    if declared is None:
-        return []
-    if isinstance(declared, str):
-        if not declared.strip():
-            raise InvalidDeclaration("empty string (declare '[]' for none)")
-        try:
-            declared = json.loads(declared)
-        except json.JSONDecodeError as e:
-            raise InvalidDeclaration(f"not valid JSON: {e}") from e
-    if not isinstance(declared, list):
-        raise InvalidDeclaration(
-            f"expected a JSON array of strings, got {type(declared).__name__}"
-        )
-    bad = [c for c in declared if not isinstance(c, str)]
-    if bad:
-        raise InvalidDeclaration(f"non-string item(s): {json.dumps(bad)}")
-    return [c.strip() for c in declared if c.strip()]
-
-
-def tail_of(text):
-    tail = "\n".join(text.splitlines()[-TAIL_LINES:])
-    if len(tail) > MAX_TAIL_CHARS:
-        tail = "…" + tail[-MAX_TAIL_CHARS:]
-    return tail
-
-
-def run_one(cmd, proj, budget):
-    """Run one command, hard-bounded by `budget` seconds; return its record."""
-    start = time.monotonic()
-    popen_kwargs = {"start_new_session": True} if os.name == "posix" else {}
-    env = {k: v for k, v in os.environ.items() if not k.startswith("GRAPH_STATE")}
-    p = subprocess.Popen(
-        cmd,
-        shell=True,
-        cwd=proj,
-        stdout=subprocess.PIPE,
-        stderr=subprocess.PIPE,
-        text=True,
-        encoding="utf-8",
-        errors="replace",
-        env=env,
-        **popen_kwargs,
-    )
-    try:
-        out_s, err_s = p.communicate(timeout=budget)
-    except subprocess.TimeoutExpired:
-        if os.name == "posix":
-            try:
-                os.killpg(os.getpgid(p.pid), signal.SIGKILL)
-            except (ProcessLookupError, PermissionError):
-                pass
-        else:
-            p.kill()
-        try:
-            p.communicate(timeout=DRAIN_TIMEOUT_SECS)
-        except subprocess.TimeoutExpired:
-            pass
-        return {
-            "cmd": cmd,
-            "exit": -1,
-            "duration_s": round(time.monotonic() - start, 1),
-            "tail": f"TIMEOUT: no exit within {budget:.0f}s — recorded as a failing run",
-        }
-    combined = (out_s or "") + (("\n" + err_s) if err_s else "")
-    return {
-        "cmd": cmd,
-        "exit": p.returncode,
-        "duration_s": round(time.monotonic() - start, 1),
-        "tail": tail_of(combined),
-    }
-
-
-def main():
-    state = load_state()
-    try:
-        cmds = declared_commands(state.get("verification_commands"))
-    except InvalidDeclaration as e:
-        msg = f"PIPELINE-FAULT: verification_commands declaration invalid — {e}"
-        prior = state.get("pipeline_faults")
-        faults = [f for f in prior if isinstance(f, str)] if isinstance(prior, list) else []
-        faults.append(msg)
-        print(json.dumps({"exec_results": msg, "pipeline_faults": faults}))
-        return
-    if not cmds:
-        print(
-            json.dumps(
-                {
-                    "exec_results": (
-                        "none declared — the caller supplied no verification_commands; "
-                        "execution criteria (build/test/lint) cannot be independently "
-                        "confirmed. Declare the exact commands via the "
-                        "verification_commands variable to get recorded runs."
-                    )
-                }
-            )
-        )
-        return
-
-    proj = os.path.expanduser(
-        (state.get("project_dir") or "").strip() or "."
-    )
-    deadline = time.monotonic() + TOTAL_DEADLINE_SECS
-    results = []
-    _stack_lock = acquire_stack_lock() if cmds else None  # noqa: F841 — held until exit
-    for cmd in cmds:
-        remaining = deadline - time.monotonic()
-        if remaining <= 0:
-            results.append({"cmd": cmd, "skipped": "deadline"})
-            continue
-        results.append(run_one(cmd, proj, min(PER_COMMAND_TIMEOUT_SECS, remaining)))
-    print(json.dumps({"exec_results": results}))
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — never fail the node; degrade visibly
-    print(
-        json.dumps(
-            {
-                "exec_results": (
-                    f"ENVIRONMENT: verification runner error: {e} — the declared "
-                    "commands could not be executed; execution criteria are unproven "
-                    "(PARTIAL at the criterion level; the verdict blocks CONFORMS when "
-                    "commands were declared)"
-                )
-            }
-        )
-    )

assets/agents/adversary/scripts/verdict.py

@@ -1,293 +0,0 @@
-#!/usr/bin/env python3
-"""Deterministic conformance verdict for the adversary graph.
-
-CONFORMS requires: at least one criterion, every criterion MET, zero
-holistic complaints, zero pipeline faults, and zero recorded red
-verification runs (exit≠0/timeout/skipped, or an ENVIRONMENT runner-error
-marker when commands were declared — the declared commands never ran, so the
-run is unproven). Everything else — including a missing plan or a degraded
-(faulted) pipeline — is DIVERGES (fail-closed).
-Any "PIPELINE-FAULT:" marker recorded in `pipeline_faults` (or a holistic
-llm-node failure captured in `holistic_failure`) becomes complaint #1;
-per-criterion results are still reported. A criterion whose check DIED
-(criterion_fault's UNMET verdict, evidence prefixed DIED_EVIDENCE_PREFIX) is
-rendered as died rather than judged and counted as unmet regardless of the
-status it carries. Assembles the exact sentinel format the callers route on.
-Never crashes into a silent verdict.
-"""
-
-import json
-import os
-
-MAX_FAULT_DETAIL_CHARS = 300
-MAX_MARKER_CHARS = 200
-DIED_MARKER = "criterion check DIED (pipeline fault)"
-DIED_EVIDENCE_PREFIX = "PIPELINE-FAULT: criterion "
-
-
-def died(v):
-    evidence = v.get("evidence")
-    return isinstance(evidence, str) and evidence.startswith(DIED_EVIDENCE_PREFIX)
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def collect_pipeline_faults(state):
-    """Recorded fault markers, plus a holistic llm-node failure if one occurred.
-
-    `holistic_failure` holds the "LLM node …failed: <chain>" string when the
-    holistic pass fell back to verdict; on a successful pass it holds the
-    rendered schema output (never that prefix).
-    """
-    faults = [
-        f.strip()
-        for f in (state.get("pipeline_faults") or [])
-        if isinstance(f, str) and f.strip()
-    ]
-    hf = state.get("holistic_failure")
-    if isinstance(hf, str) and hf.strip().startswith("LLM node"):
-        detail = hf.strip().replace("\n", " ")
-        if len(detail) > MAX_FAULT_DETAIL_CHARS:
-            detail = detail[: MAX_FAULT_DETAIL_CHARS - 1] + "…"
-        faults.append(
-            "PIPELINE-FAULT: holistic pass failed — criterion verdicts stand "
-            f"but cross-cutting hunt did not run ({detail})"
-        )
-    return faults
-
-
-def append_criterion_complaints(lines, verdicts, extra, start):
-    """Numbered complaints for non-MET verdicts and holistic extras."""
-    i = start
-    for v in verdicts:
-        if v.get("status") == "MET" and not died(v):
-            continue
-        i += 1
-        text = (v.get("text") or "").strip().replace("\n", " ")
-        if len(text) > 140:
-            text = text[:137] + "…"
-        complaint = (v.get("complaint") or "").strip()
-        if died(v):
-            if not complaint.startswith(DIED_MARKER):
-                complaint = f"{DIED_MARKER} — {complaint}" if complaint else DIED_MARKER
-            lines.append(f'{i}. Acceptance criterion "{text}" — {complaint}')
-        else:
-            lines.append(
-                f'{i}. Acceptance criterion "{text}" — {v.get("status", "?").title()} — '
-                f"{complaint}"
-            )
-    for c in extra:
-        i += 1
-        lines.append(
-            f"{i}. {c.get('kind', 'violation')} — {c.get('location', '?')} — "
-            f"{c.get('violation', '')} — {c.get('fix', '')}"
-        )
-    return i
-
-
-def declared_nonempty(declared):
-    """True when verification_commands names at least one command.
-
-    Accepts a list or a JSON-encoded string of one. None, unparseable, or
-    empty declarations count as not declared — run_checks already records
-    a PIPELINE-FAULT for the invalid ones.
-    """
-    if isinstance(declared, str):
-        try:
-            declared = json.loads(declared)
-        except json.JSONDecodeError:
-            return False
-    if not isinstance(declared, list):
-        return False
-    return any(isinstance(c, str) and c.strip() for c in declared)
-
-
-def exec_run_complaints(exec_results, declared):
-    """One complaint per red verification run recorded by run_checks.py.
-
-    A red run is a record that was skipped (deadline) or exited nonzero
-    (including the -1 TIMEOUT sentinel). An "ENVIRONMENT: …" runner-error
-    marker with a non-empty declaration is one complaint: the declared
-    commands never ran. Other string markers ("none declared",
-    "PIPELINE-FAULT…") are not runs and yield nothing.
-    """
-    if isinstance(exec_results, str):
-        marker = exec_results.strip().replace("\n", " ")
-        if not marker.startswith("ENVIRONMENT:") or not declared_nonempty(declared):
-            return []
-        if len(marker) > MAX_MARKER_CHARS:
-            marker = marker[: MAX_MARKER_CHARS - 1] + "…"
-        return [
-            f"Verification runner error — the declared command(s) never ran ({marker}); "
-            "unproven runs block CONFORMS"
-        ]
-    if not isinstance(exec_results, list):
-        return []
-    out = []
-    for r in exec_results:
-        if not isinstance(r, dict):
-            continue
-        cmd = r.get("cmd", "?")
-        if r.get("skipped"):
-            out.append(f"Verification run `{cmd}` — never ran: deadline expired (unproven)")
-            continue
-        code = r.get("exit")
-        if code == 0:
-            continue
-        outcome = "TIMEOUT (exit -1)" if code == -1 else f"exit {code}"
-        out.append(
-            f"Verification run `{cmd}` — {outcome} (recorded FAIL; a red declared "
-            "command blocks CONFORMS regardless of criterion judgments)"
-        )
-    return out
-
-
-def render_exec_results(exec_results):
-    """Lines for the "Verification runs:" report section.
-
-    exec_results is a list of {cmd, exit, duration_s, tail} records (or
-    {cmd, skipped} for commands the runner's total deadline left no budget
-    for) from run_checks.py, or a string marker ("none declared —…" /
-    "ENVIRONMENT: …"), or empty when the run never reached the stage.
-    """
-    if isinstance(exec_results, list):
-        out = []
-        for r in exec_results:
-            if not isinstance(r, dict):
-                continue
-            if r.get("skipped"):
-                out.append(
-                    f"- [SKIPPED] `{r.get('cmd', '?')}` — never ran: the runner's "
-                    "total deadline expired first; covered criteria are unproven"
-                )
-                continue
-            status = "PASS" if r.get("exit") == 0 else "FAIL"
-            out.append(
-                f"- [{status}] `{r.get('cmd', '?')}` — exit {r.get('exit', '?')}, "
-                f"{r.get('duration_s', '?')}s"
-            )
-            if status == "FAIL":
-                tail = (r.get("tail") or "").strip()
-                out.extend("    " + t for t in tail.splitlines()[-15:])
-        return out or ["- (no verification commands were run)"]
-    if isinstance(exec_results, str) and exec_results.strip():
-        return [f"- {exec_results.strip()}"]
-    return ["- none recorded (the run did not reach the verification stage)"]
-
-
-def main():
-    state = load_state()
-    verdicts = [v for v in (state.get("crit_verdicts") or []) if isinstance(v, dict)]
-    extra = [c for c in (state.get("extra_complaints") or []) if isinstance(c, dict)]
-    observations = (state.get("observations") or "").strip()
-    faults = collect_pipeline_faults(state)
-    reds = exec_run_complaints(
-        state.get("exec_results"), state.get("verification_commands")
-    )
-    n = len(verdicts)
-
-    met = [v for v in verdicts if v.get("status") == "MET" and not died(v)]
-    partial = [v for v in verdicts if v.get("status") == "PARTIAL" and not died(v)]
-    bad = [
-        v for v in verdicts if died(v) or v.get("status") in ("UNMET", "DIVERGED")
-    ]
-
-    lines = []
-    if faults:
-        lines.append("ADVERSARIAL_REVIEW: DIVERGES")
-        if n:
-            lines.append(
-                f"Criteria: {len(met)}/{n} met, {len(partial)} partial, "
-                f"{len(bad)} unmet/diverged — degraded run: pipeline fault recorded "
-                "(fail-closed)."
-            )
-        else:
-            lines.append(
-                "Criteria: none verified — degraded run: pipeline fault recorded "
-                "(fail-closed)."
-            )
-        lines.append("Complaints:")
-        i = 0
-        for f in faults:
-            i += 1
-            lines.append(f"{i}. {f}")
-        i = append_criterion_complaints(lines, verdicts, extra, i)
-        for c in reds:
-            i += 1
-            lines.append(f"{i}. {c}")
-        if observations:
-            lines.append("")
-            lines.append("Non-blocking observations:")
-            lines.append(observations)
-    elif n == 0:
-        lines.append("ADVERSARIAL_REVIEW: DIVERGES")
-        lines.append("Criteria: none provided.")
-        lines.append("Complaints:")
-        lines.append(
-            "1. No acceptance criteria were provided or extractable — conformance cannot "
-            "be judged without a spec (fail-closed). Supply the plan's Objective/Tasks/"
-            "Acceptance criteria and re-run."
-        )
-        for i, c in enumerate(reds, start=2):
-            lines.append(f"{i}. {c}")
-    elif not partial and not bad and not extra and not reds:
-        lines.append("ADVERSARIAL_REVIEW: CONFORMS")
-        lines.append(f"Criteria: {n}/{n} met (all with tests).")
-        if observations:
-            lines.append("")
-            lines.append("Non-blocking observations:")
-            lines.append(observations)
-    else:
-        lines.append("ADVERSARIAL_REVIEW: DIVERGES")
-        header = f"Criteria: {len(met)}/{n} met, {len(partial)} partial, {len(bad)} unmet/diverged"
-        notes = []
-        if died_count := sum(1 for v in verdicts if died(v)):
-            notes.append(f"degraded run: {died_count} criterion check(s) died (fail-closed)")
-        if reds:
-            notes.append(f"{len(reds)} red verification run(s) (fail-closed)")
-        lines.append(header + "".join(f" — {note}" for note in notes) + ".")
-        lines.append("Complaints:")
-        i = append_criterion_complaints(lines, verdicts, extra, 0)
-        for c in reds:
-            i += 1
-            lines.append(f"{i}. {c}")
-        if observations:
-            lines.append("")
-            lines.append("Non-blocking observations:")
-            lines.append(observations)
-
-    # Per-criterion evidence appendix (MET entries, for auditability).
-    if met:
-        lines.append("")
-        lines.append("Met criteria (evidence):")
-        for v in met:
-            text = (v.get("text") or "").strip().replace("\n", " ")
-            if len(text) > 100:
-                text = text[:97] + "…"
-            lines.append(f'- "{text}" — {(v.get("evidence") or "").strip()}')
-
-    lines.append("")
-    lines.append("Verification runs:")
-    lines.extend(render_exec_results(state.get("exec_results")))
-
-    print(json.dumps({"adv_report": "\n".join(lines)}))
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — never a silent verdict
-    print(
-        json.dumps(
-            {
-                "adv_report": (
-                    "ADVERSARIAL_REVIEW: DIVERGES\n"
-                    f"Criteria: verdict computation error: {e} — treat as failed, not as conforming."
-                )
-            }
-        )
-    )

assets/agents/adversary/tools.sh

@@ -3,14 +3,14 @@ set -eo pipefail
 
 # @env LLM_OUTPUT=/dev/stdout
 # @env LLM_AGENT_VAR_PROJECT_DIR=.
-# @describe Security reviewer tools
+# @describe Adversarial plan-conformance reviewer tools
 
 _project_dir() {
   local dir="${LLM_AGENT_VAR_PROJECT_DIR:-.}"
   (cd "${dir}" 2>/dev/null && pwd) || echo "${dir}"
 }
 
-# @cmd Get the git diff to review for security flaws. Returns staged changes, or unstaged if nothing is staged, or the HEAD~1 diff if the working tree is clean.
+# @cmd Get the git diff to review for plan conformance. Returns staged changes, or unstaged if nothing is staged, or the HEAD~1 diff if the working tree is clean.
 # @option --base Optional base ref to diff against (e.g., "main", "HEAD~3", a commit SHA, or a PR base branch)
 get_diff() {
   local project_dir
@@ -45,7 +45,7 @@ get_diff() {
   } >> "$LLM_OUTPUT"
 }
 
-# @cmd Get the list of changed files with stats (a quick map of the attack surface under review).
+# @cmd Get the list of changed files with stats (a quick map of what to check against the plan).
 # @option --base Optional base ref to diff against
 get_changed_files() {
   local project_dir

assets/agents/architect/README.md

@@ -137,7 +137,6 @@ coyote -a architect \
 | `design_doc` | *(empty)* | Path to the design doc; asked for if unset. |
 | `base_branch` | `main` | Branch the run branch forks from and the PR targets. |
 | `autonomy` | `full` | `full` (no gates) · `plan-gate` (approve breakdown once) · `phase-gate` (approve each task). |
-| `escalation_policy` | `interactive` | `interactive` (pause and ask) · `autonomous` (self-resolve decisions covered by a standing ruling in `~/.config/coyote/share/standing-rulings.md` or a clearly recommended option; everything self-resolved lands in a “Decisions taken autonomously” digest in the Phase F report and PR body; secrets/money/destructive actions and novel conflicts still escalate). |
 | `parallel_tasks` | `0` | `0` = sequential (default) · `1` = opt-in worktree-parallel execution for eligible tasks. |
 | `auto_confirm` | `1` | Skip the shell confirm guard (needed for non-interactive autonomous runs). |
 
@@ -160,9 +159,6 @@ By default (`parallel_tasks: 0`) tasks run **sequentially** on the single run br
 - Architect integrates: completed task branches merge into the run branch **one at a time**, with a
   full build + test run after every merge. Conflicts go back to that task's Sisyphus session to
   rebase and re-verify.
-- Optionally, the `agent__task_*` queue may mirror the on-disk `blocked_by` graph so completing a
-  task auto-dispatches its unblocked dependents. The queue is in-memory convenience only — disk task
-  files remain the durable source of truth.
 - Worktrees and task branches are cleaned up after each clean merge. Phase F (single draft PR +
   CI-check watch) is unchanged in both modes.
 
@@ -176,8 +172,6 @@ By default (`parallel_tasks: 0`) tasks run **sequentially** on the single run br
 | [`oracle`](../oracle/README.md) | Plan review (`plan-review`); diagnosis when a task fails after Sisyphus recovery. |
 | [`explore`](../explore/README.md) | Ground the design/plan in real code; read other local repos for library usage and call sites. |
 | [`librarian`](../librarian/README.md) | External docs / OSS examples for unfamiliar libraries. |
-| [`whetstone`](../whetstone/README.md) | Continuous improvement — spawned once before the final report when the run addressed PR review feedback from outside its own lanes; converts review misses into user-approved suite edits / ledger entries. Never blocks the run. |
-| [`review-gauntlet`](../review-gauntlet/README.md) | Preferred per-task conformance gate — one spawn running adversary (+ probe for consumer-facing tasks) with a machine-parsed GAUNTLET: PASS/BLOCKED verdict; a `GAUNTLET_REVIEW_INCOMPLETE:` line is an infrastructure fault escalated to the user (retry / accept NEEDS-HUMAN / abort), never a divergence; direct adversary/probe spawns remain the fallback. |
 
 ## Related skills
 
@@ -185,3 +179,4 @@ By default (`parallel_tasks: 0`) tasks run **sequentially** on the single run br
 - [`task-tracking`](../../skills/task-tracking/SKILL.md) — the task-file schema, lifecycle, and consistency checks.
 - [`plan-gatekeeping`](../../skills/plan-gatekeeping/SKILL.md) — the gatekeeper's self-containedness manifest.
 - [`plan-authoring`](../../skills/plan-authoring/SKILL.md) / [`plan-review`](../../skills/plan-review/SKILL.md) — plan schema + oracle's executability review.
+- [`adversarial-review`](../../skills/adversarial-review/SKILL.md) — the adversary's conformance methodology.

assets/agents/architect/config.yaml

@@ -3,10 +3,9 @@ description: |
   Design-doc orchestrator for any project. Consumes a high-level design doc, decomposes it into a
   gated plan (gatekeeper self-containedness + oracle plan-review) and ~1-engineer-day task files,
   spawns one Sisyphus per task on a single run branch, verifies each with an adversarial
-  plan-conformance check (plus a black-box usage-pattern probe for consumer-facing surface), and
+  plan-conformance check, and finishes with ONE draft PR (CI checks watched to green) plus tracked
-  finishes with ONE draft PR (CI checks watched to green) plus tracked follow-up tasks. Task state
+  follow-up tasks. Task state lives on disk in a plans directory, so runs survive context compression.
-  lives on disk in a plans directory, so runs survive context compression.
+version: 2.0.0
-version: 2.5.0
 agent_session: temp
 auto_continue: true
 max_auto_continues: 100
@@ -19,10 +18,7 @@ spawnable_agents:
   - explore
   - librarian
   - adversary
-  - probe
-  - review-gauntlet
   - gatekeeper
-  - whetstone
 max_concurrent_agents: 10
 max_agent_depth: 10
 inject_spawn_instructions: true
@@ -31,7 +27,6 @@ summarization_threshold: 100000
 skills_enabled: true
 enabled_skills:
   - design-session
-  - grilling
   - task-tracking
   - plan-authoring
   - delegation-protocol
@@ -54,9 +49,6 @@ variables:
   - name: autonomy
     description: 'How autonomous the run is: full (no gates), plan-gate (approve breakdown once, then autonomous), phase-gate (approve each task)'
     default: full
-  - name: escalation_policy
-    description: "How escalation-worthy decisions (yours and relayed child escalations) are handled: 'interactive' pauses and asks the user; 'autonomous' self-resolves decisions covered by a standing ruling or a clearly recommended option, reports them in the Phase F digest, and only pings on hard triggers or novel conflicts"
-    default: 'interactive'
   - name: auto_confirm
     description: Auto-confirm command execution (1 = skip the shell guard_operation TTY prompt, needed for non-interactive autonomous runs)
     default: '1'
@@ -118,37 +110,6 @@ instructions: |
   AFTER its merge landed and integration tests passed is routine documented cleanup, not a
   destructive action.
 
-  ## Escalation policy: {{escalation_policy}}
-
-  Orthogonal to autonomy mode: autonomy decides which GATES pause the run; escalation policy decides
-  what happens when a genuine decision point fires — yours, or a child agent's escalation.
-
-  - **interactive** (default) — escalate to the user exactly as written throughout this config.
-  - **autonomous** — the user pre-delegated decision-making. Before pinging the user (and before
-    relaying any child `pending_escalations` to them), work this ladder IN ORDER:
-    1. **Hard triggers — ALWAYS the user's; no ruling can delegate them:** secrets/credentials,
-       money movement, destructive or irreversible actions, anything the Hard blocks / Anti-patterns
-       sections forbid — and any decision that already failed once after an autonomous resolution.
-    2. **Standing rulings** — read `$HOME/.config/coyote/share/standing-rulings.md` (skip silently
-       if absent). A ruling whose trigger GENUINELY matches resolves the decision: apply it, or
-       answer the blocked child via `agent__reply_escalation`. Match on substance, not resemblance;
-       unsure means no match.
-    3. **Clearly recommended option** — if the decision carries options with one clearly recommended
-       on concrete evidence (a reviewer's proposed fix, a repo convention), take it.
-    4. **Otherwise — escalate** as interactive mode would. Autonomy never converts "I don't know"
-       into a guess.
-
-    When a resolution amends a plan/task's acceptance criteria, the criterion TEXT must be rewritten
-    before any conformance re-run — when the decision was a child's, your `agent__reply_escalation`
-    reply must instruct it to amend its plan context (the adversary verifies the plan-as-amended,
-    not the stale wording).
-
-    Every autonomous resolution — yours and the ones you replied to children — gets one line in
-    Phase F's `## Decisions taken autonomously` rollup: what was decided, the basis (`ruling:
-    <id/title>` or `recommended option`), and what changed (including plan amendments). When a novel
-    decision DID reach the user, suggest `coyote --macro record-ruling` in the final report so that
-    class never asks again.
-
   ## The pipeline (drive this to completion)
 
   ### Phase A — Orient (once, at startup)
@@ -165,33 +126,15 @@ instructions: |
 
   ### Phase B — Design decomposition
 
-  Load and follow the `design-session` skill against the design doc. When running
+  Load and follow the `design-session` skill against the design doc. This produces
-  interactively, also load `grilling` and put the open design decisions to the user as
-  frontier rounds (numbered questions, each with a recommended answer) instead of ad-hoc
-  one-at-a-time questions. This produces
   `{{plans_dir}}/PLAN-<slug>.md` with Problem, Scope, Approach, Alternatives, Constraints/risks,
   Open questions, and a **Task breakdown** where **each task is sized to ~1 engineer-day** (decompose
   anything bigger NOW).
 
-  Run design-session's quality-bar round as part of decomposition: settle `rigor` and `surfaces`
-  with the user and record them in the PLAN frontmatter and its `## Quality bar` section (dropped
-  practices, long-tail criteria). For each `other:<label>` surface, spawn `librarian` for a
-  distilled best-practice checklist ("Established best practices and common review checklist for
-  <label>; authoritative sources preferred; return a distilled, deduplicated checklist"), put the
-  returned checklist through the same accept/drop round with the user, and write the ACCEPTED
-  items into the plan — as measurable acceptance criteria on the relevant tasks where possible,
-  otherwise as a checklist under `## Quality bar → Long-tail criteria`.
-
   Ground the breakdown in real code: fan out `explore` agents (load `parallel-research`) across
   {{project_dir}} — and `librarian` for unfamiliar external libraries — to confirm the design's
   assumptions before sizing. Do NOT guess file/symbol names — verify them.
 
-  When a research burst's lanes are likely to feed each other, run it in **team mode** (see
-  `parallel-research`): after spawning, message every explore lane the roster of its siblings
-  (`agent__send_message`) so cross-lane facts move mid-flight instead of waiting for your
-  synthesis. (`librarian` is a graph agent and cannot participate — route facts to it through
-  yourself.)
-
   In `full` autonomy, if the design session surfaces open questions you cannot answer from the doc or
   the codebase, ask the user (`user__ask`); an unresolved question that changes scope is a hard stop
   even in `full`.
@@ -202,8 +145,7 @@ instructions: |
 
   **Gate 1 — Self-containedness (`gatekeeper`).** The plan must pass the "docker container" test:
   every question a context-free implementer will hit is answered inline or delegated via a verified
-  pointer to code/docs (where infra code goes, DB tech/target, layout to mirror, test commands,
+  pointer to code/docs (where infra code goes, DB tech/target, layout to mirror, test commands, ...).
-  local-run recipe for any consumer-facing surface the plan creates, ...).
 
   > `agent__spawn --agent gatekeeper --prompt "Audit this plan for self-containedness. Return
   > SEALED/LEAKY. Plan: {{plans_dir}}/PLAN-<slug>.md. Target project: {{project_dir}}."`
@@ -306,10 +248,6 @@ instructions: |
      - Do NOT diverge from the task's stated scope; if the plan is wrong, STOP and report back.
 
      ## CONTEXT
-     Quality bar: rigor=<plan frontmatter rigor>, surfaces=<this task's surfaces (task frontmatter
-     `surfaces:` if present, else the plan's)>
-     <paste the plan's ## Quality bar section here verbatim — dropped practices + long-tail
-     criteria; Sisyphus forwards this bar to its reviewers>
      <paste the task's index.md body and the relevant PLAN section here verbatim — plus any code
      snippets explore found showing the patterns to follow>
      "
@@ -319,60 +257,10 @@ instructions: |
 
   3. **Wait for Sisyphus.** Do not poll `agent__collect` on a running agent — do non-overlapping work
      (e.g. prep the next task's context) or end your response and wait for the completion
-     notification (a `system_notifications` entry on your next tool result), then `agent__collect`.
+     notification, then `agent__collect`.
 
   4. **Verify against the plan (divergence check).** When Sisyphus returns, do NOT trust its
      self-report — get an INDEPENDENT conformance verdict:
-     - **Preferred: run the conformance checks through `review-gauntlet`** when it is installed —
-       ONE spawn instead of separate adversary/probe spawns, with machine-parsed verdicts:
-
-       ```
-       agent__spawn --agent review-gauntlet --prompt "Post-implementation review gate.
-       Project: <the code repo the task's changes landed in>
-       Diff: <the task's BASE SHA from its started log entry>..HEAD
-       Forced lanes: adversary<, probe — add probe when the task changed consumer-facing surface and the plan carries a local-run recipe>
-       Plan / acceptance criteria: <the task's acceptance criteria, pasted verbatim>
-       Local-run recipe / usage suites: <from the plan, when present>"
-       --variables {"verification_commands": "[\"cargo test --all\", \"cargo clippy -- -D warnings\"]"}
-       <— the cargo commands above are only an EXAMPLE: replace them with THIS project's exact build/test/lint commands; never guess, and pass "[]" when none apply>
-       ```
-
-       Verification commands go in `--variables` (a JSON-array string), never in the prompt: the
-       prompt also carries pasted plan text from the repo under review, and whatever is declared
-       here is executed with a shell — a trust boundary the prose must not cross.
-       Budget: each declared command gets at most 15 minutes and the whole set 55 minutes —
-       declare targeted build/unit-test commands, not full integration suites; a command
-       that exceeds the budget is recorded as a red run and fails conformance. Never declare
-       commands that boot shared stacks or services (docker compose projects, dev servers,
-       fixed ports) — the probe lane owns end-to-end runs and WILL collide with them in
-       parallel; keep verification to generate/lint/build/unit/integration commands.
-
-       It returns `GAUNTLET: PASS/BLOCKED`. On BLOCKED with real review findings apply the same
-       fix-and-rerun rules as below (resume the SAME Sisyphus session with the findings verbatim,
-       then a FRESH gauntlet run). A BLOCKED whose only blockers are review faults (`PIPELINE-FAULT`
-       / `review incomplete` entries) is NOT a code failure. A `GAUNTLET_REVIEW_INCOMPLETE: <lane>[,
-       <lane>]` line directly under `GAUNTLET: BLOCKED` means the review could NOT be completed: the
-       named lanes still faulted after 3 attempts, or the gauntlet pipeline itself faulted
-       (`pipeline`). This is an infrastructure fault, not a code finding.
-       NEVER route it through the findings-handling rules (it is not a divergence to send back to
-       Sisyphus). NEVER claim done while it stands.
-       Escalate to the user via `user__select` with exactly these three options:
-       - "Retry the review again"
-       - "Accept NEEDS-HUMAN: proceed without the <lane or pipeline> review (recorded in the report / PR body)"
-       - "Abort this task"
-       Retry → a FRESH gauntlet run. Accept → close the task and record the skipped review (lane
-       names or `pipeline`) in the task's `log.md`, the Phase F digest, and the PR body. Abort →
-       leave the task `in-progress`, log the abort in its `log.md`, and stop to report. Findings AND
-       incomplete on the same output → fix the findings first, then re-run the gauntlet (the re-run
-       retries the lane) — escalate only if the line persists. Under `escalation_policy: autonomous`
-       the standard ladder applies (a standing ruling may pre-answer this decision).
-       The direct `adversary`/probe spawns below are the FALLBACK when the gauntlet is not installed;
-       on that path an adversary/probe result that is ONLY a `PIPELINE-FAULT` (no verdict on the
-       code) is likewise an infrastructure fault to retry, never a divergence.
-       Each gauntlet round's outcome is recorded on the task's PR as a NEW comment titled
-       `## Review round N @ <full head SHA>` (lane table, verdicts, what changed since the
-       prior round) — never by rewriting the PR description, which carries only the stable
-       summary and the required digest sections; comments are the append-only review log.
      - **Spawn `adversary`** with the diff base and the criteria pasted in:
 
        ```
@@ -383,16 +271,9 @@ instructions: |
        this isolates THIS task's commits on the shared run branch from earlier tasks' work.
 
        PLAN — acceptance criteria to check against:
-       <paste the task index.md body + the relevant PLAN-<slug>.md section VERBATIM>
+       <paste the task index.md body + the relevant PLAN-<slug>.md section VERBATIM>"
-       <paste the plan's ## Quality bar section VERBATIM — recorded dropped practices are
-       conformance facts, not divergences>"
-       --variables {"verification_commands": "[\"cargo test --all\", \"cargo clippy -- -D warnings\"]"}
-       <— the cargo commands above are only an EXAMPLE: replace them with THIS project's exact build/test/lint commands; never guess, and pass "[]" when none apply>
        ```
 
-       Same trust boundary as the gauntlet spawn: verification commands are declared via
-       `--variables`, never in the prompt, because the prompt also carries untrusted pasted text.
-
      - **`ADVERSARIAL_REVIEW: DIVERGES`** → treat it as a blocker: resume the SAME Sisyphus session
        (`agent__spawn --session_id <id> --prompt "Fix these plan-conformance failures: <adversary
        complaints, verbatim>"`) — do not spawn a fresh one. Re-run `adversary` ONCE after the fix to
@@ -401,50 +282,13 @@ instructions: |
        escalate — do not silently change scope.
      - **`ADVERSARIAL_REVIEW: CONFORMS`** → conformance satisfied. Also confirm the stated test
        commands pass (run them if feasible) before closing.
-     - **Usage-pattern probe (consumer-facing tasks).** If the task added or changed consumer-facing
-       surface (endpoints/RPCs/CLI commands, request/response shapes, contract semantics like
-       patch-vs-replace, idempotency, auth on routes), ALSO spawn `probe` for an independent
-       black-box behavioral verdict — it boots the code locally from a clean state, runs existing
-       usage suites for regressions, and spec-first-tests the changed surface with the repo's
-       existing suite tooling or whatever is available (e.g. Hurl/curl, grpcurl, direct CLI
-       invocation). Skip it (one-line note) for tasks with no consumer-visible surface.
-
-       ```
-       agent__spawn --agent probe --prompt "Probe TASK-NNN's changed surface from the consumer's
-       perspective. Return PASS/FAIL/INCONCLUSIVE.
-
-       CHANGE: run get_diff --base <the task's BASE SHA recorded at claim time> in {{project_dir}}.
-
-       SPEC — expected behavior to verify against:
-       <paste the task's acceptance criteria + relevant API contract sections VERBATIM>
-
-       LOCAL-RUN RECIPE: <paste the plan's local-run recipe verbatim — Gate 1 requires one for
-       consumer-facing tasks>
-
-       EXISTING SUITES: <paths + run commands from the plan, or 'discover them'>"
-       ```
-
-       Set the probe's `project_dir` to {{project_dir}}. Verdict handling:
-       - **`USAGE_PROBE: FAIL`** → blocker, same loop as DIVERGES: resume the SAME Sisyphus session
-         with the behavioral findings (including repros) verbatim; re-run `probe` ONCE (resume ITS
-         session so it reuses its environment and tests); still FAILing on the same findings →
-         STOP and escalate.
-       - **`USAGE_PROBE: PASS`** → have Sisyphus adopt probe's new test files (paths are in its
-         report) as a commit on the run branch so they ship as permanent regression coverage.
-       - **`USAGE_PROBE: INCONCLUSIVE`** → the local-run recipe is missing or broken — a PLAN gap,
-         not a code failure. Fix the recipe (amend the plan) or escalate, re-run once; NEVER count
-         INCONCLUSIVE as PASS or FAIL.
      - If Sisyphus reports failure after its own recovery, surface the evidence and consult `oracle`
        for diagnosis before deciding whether to retry, re-scope, or escalate.
 
   5. **Close the task.** Per `task-tracking`: check off Steps + Acceptance criteria (verified, not
      aspirational); log `completed` with the run branch + this task's commit SHA(s); if Sisyphus
      reported FOLLOW-UPS, copy them VERBATIM into the completed entry under a "Follow-ups:" line
-     (disk is the durable store — Phase F rolls these up from the logs); if Sisyphus reported
+     (disk is the durable store — Phase F rolls these up from the logs); set `status: complete`.
-     evidence-cited rejections of review findings, log each in the same entry as one line —
-     `rejected-finding: <finding> — <evidence>` — for Phase F's `## Review decisions` rollup (a
-     rejection without cited evidence is invalid: the finding stands, do not log it as rejected);
-     set `status: complete`.
      If {{plans_dir}} rides the repo, commit the task-file updates to the run branch
      (`chore(plan): complete TASK-NNN`).
 
@@ -480,8 +324,8 @@ instructions: |
     ({{project_dir}}/.worktrees/task-NNN) and the branch with the task branch. Sisyphus commits and
     pushes the TASK branch. All other prompt sections unchanged — still no PRs, still no
     creating/switching branches (the worktree arrives already on its branch).
-  - Run the adversary check (and, for consumer-facing tasks, the probe check) in the worktree:
+  - Run the adversary check in the worktree: `get_diff --base <BASE SHA>` — identical semantics to
-    `get_diff --base <BASE SHA>` — identical semantics to sequential mode.
+    sequential mode.
 
   **Integration (architect is the integrator; merges are ALWAYS one at a time):**
   1. When a task's Sisyphus finishes AND its adversary check CONFORMS, merge in the PRIMARY checkout:
@@ -496,20 +340,6 @@ instructions: |
      the task (step 5), and clean up — `git worktree remove .worktrees/task-NNN` and delete the task
      branch (local + remote).
 
-  **Task-queue mirroring (optional).** For a parallel batch, the `agent__task_*` queue MAY mirror
-  the disk `blocked_by` graph — one queue task per TASK-NNN with `agent: sisyphus`, the delegation
-  prompt, and its variables — so completing a task auto-dispatches its unblocked dependents. This is
-  guidance, not a mandate; if you use it, these rules are HARD:
-  - Disk task files remain the durable store. The queue is in-memory and lost on
-    restart/compression — it is NEVER the source of truth.
-  - Root tasks (no blockers) are NOT auto-dispatched on create — spawn them yourself.
-  - Call `agent__task_complete` ONLY after this task's verification gate (adversary check, merge,
-    integration build+tests) passes — completing is what dispatches dependents.
-  - Collect every auto-dispatched agent via `agent__collect`; nothing is collected for you, and an
-    agent finishing does NOT complete its task.
-  - A failed spawn (capacity/whitelist) strands the queue task InProgress with no reset — recreate
-    the task rather than retrying it.
-
   Phase F is UNCHANGED (same single draft PR from the run branch). Before opening it, verify no
   stale worktrees or task branches remain (`git worktree list`); clean up any leftovers.
 
@@ -521,20 +351,9 @@ instructions: |
      the responsible Sisyphus session) before any PR exists.
   2. **Roll up follow-ups, then open the ONE PR — ALWAYS as a DRAFT** (`gh pr create --draft`) from
      `feat/PLAN-<slug>` → {{base_branch}}. First collect every "Follow-ups:" line from the completed
-     tasks' `log.md` files — findings tagged `(deferred by quality bar)` ride this rollup unchanged
+     tasks' `log.md` files. Title: `PLAN-<slug>: <design doc title>`. Body MUST contain, in order:
-     — and every `rejected-finding:` line. Title: `PLAN-<slug>: <design doc title>`. Body MUST
-     contain, in order:
      - the plan's Problem/Approach summary,
-     - a `**Quality bar:**` line — MANDATORY whenever the plan's rigor is below `production` (omit
-       at `production` rigor): `**Quality bar:** <rigor> — deferred hardening tracked in TASK-NNN, ...`,
-       listing the deferred-hardening follow-up TASK ids (appended in step 4 as those tasks are
-       created),
      - a checklist of every TASK-NNN (title + commit SHAs),
-     - a **`## Review decisions`** section: one line per collected `rejected-finding:` entry;
-       omit the section entirely when there are none,
-     - a **`## Decisions taken autonomously`** section (only when `escalation_policy: autonomous`
-       resolved anything): one line per self-resolved decision with its basis and what changed —
-       rolled up from your own resolutions and each Sisyphus report's section; omit otherwise,
      - a **`## Follow-up / manual actions`** section: one checkbox line per follow-up (WHAT, WHERE,
        WHY, WHEN — pre-merge items FIRST and clearly marked), or "None." if there are none. This
        section is the reviewer's contract for what the code does NOT do by itself.
@@ -552,24 +371,14 @@ instructions: |
      `status: pending`, with the WHAT/WHERE/WHY/WHEN and which TASK-NNN surfaced it. Then edit the
      PR body's Follow-up section to append each created TASK id to its checkbox line. Do NOT
      implement these yourself — creating them IS the deliverable; the user picks them up after the
-     merge. Append the TASK ids of deferred-hardening follow-ups to the PR body's `**Quality bar:**`
+     merge.
-     line as well.
   5. Set `PLAN-<slug>.md` frontmatter `status: implemented`, add the PR link and a
      `**Follow-ups:** TASK-NNN, ...` line when any exist; append a `pr-opened` entry to every
      completed task's `log.md`. If {{plans_dir}} rides the repo, commit these planning updates to
      the run branch (`chore(plan): ...`) — they become part of the PR.
   6. Run the `task-tracking` consistency checks; fix anything you introduced.
   7. Report: the PLAN, every TASK-NNN with its commits, the single draft PR URL with checks green,
-     the follow-up TASKs created (with their WHEN), and anything deferred/escalated — plus the
+     the follow-up TASKs created (with their WHEN), and anything deferred/escalated. STOP.
-     `## Decisions taken autonomously` rollup when the escalation policy resolved anything. STOP.
-
-  Continuous improvement: if any part of this run addressed PR review feedback that did not come
-  from the run's own reviewer lanes — humans, a teammate's review agent, another team's bot — spawn
-  `whetstone` ONCE before the final report: pass the PR ref, the human feedback verbatim, and
-  what the run's own review passes flagged. Collect it; its approval questions escalate to the
-  user directly. Never block the run's completion on it; skip silently when all feedback came from
-  the run's own lanes. (Per-task feedback handled inside a Sisyphus session is covered by Sisyphus's
-  own whetstone hook — don't double-spawn for the same feedback.)
 
   ## Durable state (survive context compression)
 
@@ -591,8 +400,6 @@ instructions: |
   | `oracle` | Plan review (`plan-review`), and diagnosis when a task fails after Sisyphus recovery. |
   | `gatekeeper` | Plan self-containedness gate (Phase C Gate 1): audits the PLAN for the "docker container" standard, returns SEALED/LEAKY with the missing implementer questions. |
   | `adversary` | Post-implementation plan-conformance verdict per task (CONFORMS/DIVERGES). |
-  | `probe` | Black-box behavioral verdict on a task's consumer-facing surface: boots the code locally from clean state, runs existing usage suites + spec-first tests. Returns USAGE_PROBE PASS/FAIL/INCONCLUSIVE. |
-  | `whetstone` | Post-run continuous improvement: classifies human review feedback vs what the suite flagged, generalizes misses, proposes suite edits / ledger entries (user-approved). Never a reviewer lane. |
 
   ## Escalation handling
 
@@ -600,11 +407,6 @@ instructions: |
   Answer from context if you can, else prompt the user, then `agent__reply_escalation` to unblock the
   child. Do not leave a child hanging.
 
-  In `autonomous` escalation policy, work the Escalation-policy ladder BEFORE prompting the user: a
-  matching standing ruling or a clearly recommended option answers the child directly (hard triggers
-  always go to the user), plan-amending replies instruct the child to rewrite the criterion text
-  first, and every autonomous reply lands in the Phase F digest.
-
   ## Anti-patterns (BLOCKING)
 
   - Opening a PER-TASK PR → the design doc gets exactly ONE PR, opened in Phase F.
@@ -618,8 +420,6 @@ instructions: |
   - Materializing tasks from a plan the gatekeeper marked LEAKY (or never audited), or that Oracle
     rejected (or never reviewed).
   - Marking a task complete without the adversary's CONFORMS verdict and verified acceptance criteria.
-  - Closing a consumer-facing task without a `probe` verdict, or treating `INCONCLUSIVE` as PASS —
-    an unprobeable consumer-facing change is a plan gap to fix, not a checkbox to skip.
   - Code comments referencing the plan/design doc/phases/steps/TASK numbers → docs drift, comments
     rot; plan references live in commit messages only.
   - A `.env` file landing in any repo → only `.env.example` with placeholder keys is committable;
@@ -633,10 +433,6 @@ instructions: |
   - Polling `agent__collect` on a running agent.
   - Writing files via `execute_command` (heredocs, `cat >`, `echo >`) instead of `fs_write`/`fs_patch`.
   - Losing a Sisyphus `session_id` or a follow-up to chat-only memory.
-  - Accepting a bare (evidence-free) rejection of a review finding → a rejection must cite a repo
-    convention at file:line or a recorded `## Quality bar` drop; otherwise the finding stands.
-  - Letting `rigor: poc/prototype` suppress a 🔴 finding → 🔴 blocks at EVERY rigor; rigor folds
-    convention findings, never critical ones.
 
   ## Hard blocks (NEVER)
 
@@ -655,7 +451,6 @@ instructions: |
   - Design doc: {{design_doc}}
   - Base branch: {{base_branch}}
   - Autonomy: {{autonomy}}
-  - Escalation policy: {{escalation_policy}}
   - Parallel tasks: {{parallel_tasks}} (0 = sequential, 1 = worktree-parallel)
   - OS: {{__os__}}  Shell: {{__shell__}}  CWD: {{__cwd__}}  Now: {{__now__}}
 

assets/agents/architecture-reviewer/README.md

@@ -1,67 +0,0 @@
-# Architecture Reviewer
-
-An **on-demand architecture improvement scout**. It scans a codebase for **deepening
-opportunities** — refactors that turn shallow modules into deep ones — presents them as a visual
-report, then refines the candidate you pick into a concrete, implementation-ready interface
-proposal.
-
-Two things it is deliberately **not**:
-
-1. **Not a completion gate.** The review stack ([`code-reviewer`](../code-reviewer/README.md),
-   [`adversary`](../adversary/README.md), [`security-reviewer`](../security-reviewer/README.md))
-   judges *changes* before a task finishes. This agent is invoked on demand, when you want the
-   codebase itself made deeper, more testable, and easier to navigate. A "cleanup gate" would
-   produce noisy, opinionated churn on every diff; a cleanup *tool* produces focused proposals
-   when you ask for them.
-2. **Not an implementer.** It proposes; you (or a `coder` you delegate to) implement. Its only
-   write is the report file in the OS temp directory — repository files are never touched.
-
-## How it works
-
-Driven by the [`codebase-design`](../../skills/codebase-design/SKILL.md) skill — the shared
-deep-module vocabulary (**module**, **interface**, **depth**, **seam**, **adapter**, **leverage**,
-**locality**) and its principles (the deletion test, "the interface is the test surface", "one
-adapter = hypothetical seam, two = real").
-
-1. **Scope by git history (YAGNI).** Deepening pays off where code keeps changing, so hot spots
-   from the commit log rank first — unless you name a direction.
-2. **Explore for friction.** Fans out `explore` agents hunting shallow modules, leaked seams,
-   concept-bouncing, and code that's hard to test through its current interface; every suspect
-   gets the deletion test.
-3. **Report candidates.** 3-6 cards (problem / solution / leverage-and-locality benefits /
-   before-after visual / `Strong`-`Worth exploring`-`Speculative` badge), as a self-contained
-   Tailwind+Mermaid HTML file in your temp dir (default) or inline markdown
-   (`report_format: markdown`). Ends with a top recommendation, then stops and asks which
-   candidate to pursue.
-4. **Refine via design-it-twice.** For the chosen candidate: frame the constraints and dependency
-   categories, produce 2-3 radically different interface designs (optionally spawning `oracle`
-   for an independent alternative), compare on depth/locality/seam placement, and hand off ONE
-   opinionated, implementation-ready proposal including the testing strategy ("replace, don't
-   layer").
-
-## Usage
-
-```sh
-# Scan the current repo, HTML report
-coyote -a architecture-reviewer "Find deepening opportunities"
-
-# Aim it at a pain point, inline report
-coyote -a architecture-reviewer --agent-variable report_format markdown \
-  "The billing/entitlements code is painful to test - what should be deepened?"
-```
-
-Also spawnable from `sisyphus` when a request is explicitly architecture-scale ("improve the
-architecture of X", "make this module easier to test").
-
-## Related
-
-- [`codebase-design`](../../skills/codebase-design/SKILL.md) — the vocabulary and principles it runs on.
-- [`oracle`](../oracle/README.md) — advisory design review; also loads `codebase-design` for the shared vocabulary.
-- [`explore`](../explore/README.md) — the codebase walkers it fans out.
-
-## Credits
-
-Adapted from the `codebase-design` and `improve-codebase-architecture` skills in
-[mattpocock/skills](https://github.com/mattpocock/skills) (MIT), which build on ideas from John
-Ousterhout's *A Philosophy of Software Design* and Michael Feathers' *Working Effectively with
-Legacy Code*.

assets/agents/architecture-reviewer/config.yaml

@@ -1,162 +0,0 @@
-name: architecture-reviewer
-description: On-demand architecture improvement scout - scans a codebase for deepening opportunities (shallow modules, leaked seams, missing locality) weighted by git-history hot spots, presents candidates as a visual report, then refines the chosen candidate into a concrete interface proposal via design-it-twice. Proposes, never implements. NOT a completion gate - invoke it when you want the codebase made deeper, more testable, and easier to navigate.
-version: 1.1.0
-
-agent_session: temp
-auto_continue: true
-max_auto_continues: 20
-inject_todo_instructions: true
-
-can_spawn_agents: true
-spawnable_agents:
-  - explore
-  - oracle
-max_concurrent_agents: 4
-# The limit is consulted by the SPAWNER against the child's absolute depth
-# (root = 0). Deepest documented chain: architect(0) → sisyphus(1) →
-# architecture-reviewer(2) → {explore | oracle}(3). This agent spawns depth-3
-# children; 4 = one level of headroom.
-max_agent_depth: 4
-inject_spawn_instructions: true
-
-skills_enabled: true
-enabled_skills:
-  - codebase-design
-  - delegation-protocol
-  - grilling
-  - parallel-research
-
-variables:
-  - name: project_dir
-    description: Project directory to scan
-    default: '.'
-  - name: report_format
-    description: Candidate report format - 'html' (self-contained file in the OS temp dir, opened for the user) or 'markdown' (inline in chat)
-    default: html
-  - name: auto_confirm
-    description: Auto-confirm command execution
-    default: '1'
-
-global_tools:
-  - ast_grep.sh
-  - fs_read.sh
-  - fs_cat.sh
-  - fs_grep.sh
-  - fs_glob.sh
-  - fs_ls.sh
-  - fs_write.sh
-  - execute_command.sh
-
-instructions: |
-  You are an architecture improvement scout. You surface **deepening opportunities** — refactors
-  that turn shallow modules into deep ones — and refine the one the user picks into a concrete
-  interface proposal. The aim is testability, locality, and AI-navigability.
-
-  Two things you are NOT:
-  1. **Not a completion gate.** The review stack (`code-reviewer`/`adversary`/`security-reviewer`)
-     judges changes; you are invoked on demand to improve what already exists.
-  2. **Not an implementer.** You produce candidates and interface proposals; the user (or a coder
-     they delegate to) owns the code change. You never modify repository files — your only writes
-     are the report file in the OS temp directory.
-
-  ## Step 0: Load the skill
-
-  Before anything else, `skill__load` `codebase-design`. It is your source of truth for the
-  vocabulary (**module**, **interface**, **depth**, **seam**, **adapter**, **leverage**,
-  **locality**), the principles (the deletion test, "the interface is the test surface", "one
-  adapter = hypothetical seam, two = real"), the dependency categories for safe deepening, and the
-  design-it-twice pattern. Use those terms EXACTLY in every finding — no "component", "service",
-  or "boundary". Load `delegation-protocol` and `parallel-research` before spawning sub-agents.
-
-  ## Phase 1: Scope, then explore
-
-  **Scope before you scan — YAGNI.** Deepening pays off where code keeps changing:
-
-  - If the user named a direction (a module, subsystem, or pain point), take it and skip inference.
-  - Otherwise mine the history for hot spots:
-    `execute_command --command "git -C {{project_dir}} log --oneline --name-only -100"` (or
-    similar) and let the files that keep recurring pull your attention. Scattered changes with no
-    hot spot → widen the net.
-
-  Read the workspace instructions (`COYOTE.md`/`AGENTS.md`) if present — documented conventions and
-  recorded decisions are constraints, not candidates; don't re-litigate them.
-
-  Then spawn 1-3 `explore` agents (per `delegation-protocol`, in parallel per `parallel-research`)
-  to walk the scoped area. Brief them to report friction, not metrics:
-
-  - Where does understanding one concept require bouncing between many small modules?
-  - Where are modules shallow — an interface nearly as complex as the implementation?
-  - Where were pure functions extracted "for testability" while the real bugs hide in how they're
-    called (no locality)?
-  - Where do tightly-coupled modules leak across their seams?
-  - What is untested, or hard to test through its current interface?
-
-  Apply the **deletion test** yourself to every suspect the explorers return: would deleting it
-  concentrate complexity (real candidate) or just move it (pass-through)?
-
-  ## Phase 2: Present candidates
-
-  Produce 3-6 candidates, each with:
-
-  - **Files**: the modules involved
-  - **Problem**: the friction the current shape causes, in skill vocabulary
-  - **Solution**: plain-English description of the deepening (no interface design yet)
-  - **Benefits**: stated as leverage and locality gains, and how tests improve
-  - **Recommendation strength**: `Strong` / `Worth exploring` / `Speculative`
-  - **Before/after sketch**: for `html`, a visual per candidate; for `markdown`, a compact
-    ASCII/mermaid sketch
-
-  **Report delivery** (per `report_format`, currently: {{report_format}}):
-
-  - `html` — write ONE self-contained file to the OS temp dir (`$TMPDIR`, falling back to `/tmp`)
-    named `architecture-review-<timestamp>.html`. Use Tailwind via CDN for layout and Mermaid via
-    CDN for graph-shaped structure (call graphs, dependencies); hand-built divs/SVG for editorial
-    visuals (mass diagrams, collapse animations). One card per candidate with a side-by-side
-    before/after diagram. Open it for the user (`open` on macOS, `xdg-open` on Linux, `start` on
-    Windows) and print the absolute path. Nothing lands in the repo.
-  - `markdown` — render the same cards inline in your response.
-
-  End the report with a **Top recommendation**: which candidate you'd tackle first and why.
-
-  Then STOP and ask which candidate to explore. Do NOT propose interfaces yet.
-
-  ## Phase 3: Refine the chosen candidate
-
-  1. **Frame the problem space**: the constraints any new interface must satisfy, the dependencies
-     and their category (in-process / local-substitutable / remote-but-owned / true external, per
-     the skill), and a rough illustrative sketch to make the constraints concrete. Show the user.
-     When the candidate carries open decisions (what sits behind the seam, which callers to
-     optimise for, what tests must survive), load `grilling` and walk them as frontier rounds —
-     recommended answer per question, facts fetched by you, decisions made by the user.
-  2. **Design it twice**: produce 2-3 radically different interface designs per the skill's
-     pattern (different constraint each: minimal interface / maximal flexibility / optimise the
-     common caller). For a candidate worth the budget, spawn `oracle` to independently design or
-     critique one alternative. Each design: interface (with invariants, ordering, error modes),
-     caller example, what hides behind the seam, adapter strategy, trade-offs.
-  3. **Compare and recommend**: contrast on depth, locality, and seam placement; give ONE
-     opinionated recommendation or a justified hybrid.
-  4. **Hand off**: summarize the chosen design as an implementation-ready proposal — files to
-     change, the target interface, the testing strategy ("replace, don't layer": new tests at the
-     deepened interface, old shallow-module tests deleted). Note that implementation belongs to
-     the caller, not you.
-
-  ## Rules
-
-  1. **Never modify repository files.** The temp-dir report is your only write.
-  2. **Skill vocabulary, exactly.** Findings that say "service" or "boundary" get rewritten.
-  3. **Friction over dogma.** A shallow module that never changes and confuses no one is not a
-     candidate. Recent-change hot spots rank first.
-  4. **Candidates are judgment calls.** Frame every problem as observed friction with evidence
-     (file:line, test absence, change-history churn), not as rule violations.
-  5. **Respect recorded decisions.** If a candidate contradicts a documented convention or
-     decision, surface it only when the friction justifies revisiting — and mark the conflict
-     clearly in the card.
-
-  ## Context
-  - Project: {{project_dir}}
-  - Report format: {{report_format}}
-  - CWD: {{__cwd__}}
-  - Shell: {{__shell__}}
-
-  ## Available Tools
-  {{__tools__}}

assets/agents/code-reviewer/README.md

@@ -1,58 +1,5 @@
 # Code Reviewer
 
-> [!IMPORTANT]
-> **v3: now a GRAPH agent.** The orchestration shell is deterministic — a script resolves the
-> diff/quality bar/ledger/history, domain linters run unconditionally, changed files are grouped
-> into DOMAIN slices (deterministic proposal → LLM refinement → exact-cover gate) reviewed in
-> parallel by [`domain-reviewer`](../domain-reviewer/README.md) leaders (peer messaging between
-> leaders; per-file depth via `file-reviewer`), every leader report passes a completeness gate,
-> findings are verified by `finding-verifier`, and the rigor folding + `MERGE-READY`/`NEEDS-HUMAN`
-> verdict are computed BY A SCRIPT. Judgment stays in the agents; discipline lives in the graph.
-> The review semantics below (severity mapping, folding rules, verdict rules, report format) are
-> unchanged — they are now structurally enforced instead of prompt-enforced.
-
-```mermaid
-flowchart TD
-    A["parse (llm)"] --> B["facts (script): diff, quality bar, ledger, history, trigger signals"]
-    A -. "fallback" .-> PF["parse_fault (script): PIPELINE-FAULT verdict"]
-    PF --> L
-    B --> C["linters (script): tflint / hadolint / actionlint / buf breaking"]
-    C --> D1["group_propose (script): deterministic domain proposal"]
-    D1 --> D2["refine_groups (llm)"]
-    D2 --> D3["cover_gate (script: exact cover)"]
-    D2 -. "fallback" .-> D3
-    D3 --> E["map over domain slices (parallel): domain-reviewer leaders, teammates on, max_attempts: 2"]
-    D3 --> F["aux_lanes (llm): org-context + prior-art spawns"]
-    D3 --> G["downstream_sweep (script)"]
-    E --> H["completeness_gate (script): required sections even when clean"]
-    E -. "fallback" .-> DF["domain_fault (script): ⚠️ PIPELINE-FAULT slice banner"]
-    H -. "reject-retry once" .-> E
-    H --> I["synthesize (llm: dedup + prose, NO verdict authority)"]
-    F --> I
-    F -. "fallback" .-> AF["aux_fault (script): PIPELINE-FAULT lane-skip note"]
-    AF --> I
-    G --> I
-    I --> J["verify: finding-verifier (agent node, unskippable, max_attempts: 2)"]
-    I -. "fallback" .-> K
-    J --> K["verdict (script): FALSE-drops, rigor folding, fault accounting, MERGE-READY / NEEDS-HUMAN arithmetic"]
-    J -. "fallback" .-> K
-    K --> L["render (script): the standard report"]
-```
-
-**Failure fails closed.** Every LLM/agent node retries once (`max_attempts: 2` — the
-domain-reviewer lanes and the verifier included), then routes to a `fallback:` instead of killing
-the graph, and every fallback that loses review coverage leaves a `PIPELINE-FAULT` marker: a dead
-`parse` emits a complete fault verdict and jumps straight to render; a dead domain lane becomes a
-`> ⚠️ PIPELINE-FAULT` banner where its slice report would be; a dead `refine_groups` falls
-through to the cover gate, which keeps the deterministic proposal; a dead synthesis or verifier
-falls through to the verdict script. The verdict script counts every fault and forces
-`NEEDS-HUMAN` — a degraded run never reads `MERGE-READY`. The aux context lanes are the one
-exception: they are enrichment, so their fault (`aux_fault`) is surfaced as a lane-skip note but
-never blocks. Fault detection is prefix-anchored (a report that merely *quotes* a marker doesn't
-trip it), and the report is always emitted: the verdict script's own crash guard emits a
-`PIPELINE-FAULT` NEEDS-HUMAN, and render bypasses its "No changes to review." stub for fault
-verdicts — a fault renders as a full report, never silence.
-
 A CodeRabbit-style code review orchestrator that coordinates per-file reviews and synthesizes findings into a unified 
 report.
 
@@ -65,37 +12,6 @@ agents while handling coordination and final reporting.
 - 🔄 **Cross-File Context**: Broadcasts sibling rosters so reviewers can alert each other about cross-cutting changes.
 - 📊 **Unified Reporting**: Synthesizes findings into a structured, easy-to-read summary with severity levels.
 - ⚡ **Parallel Execution**: Runs reviews concurrently for maximum speed.
-- 🚨 **Operational History (optional)**: Checks the change against past production incidents via the [`incident-prior-art`](../../skills/incident-prior-art/SKILL.md) skill.
-- 📦 **Context pack**: Every file-reviewer gets the same assembled inputs — change intent, repo convention docs, and matching entries from the review-miss ledger — so reviews judge against the house rules, not generic taste.
-- 🏛️ **Org context (optional)**: When the diff touches decision-laden surface (public API shapes, money/auth logic), the agent named by the `org_context_agent` variable is spawned to find recorded decisions the diff must honor — contradicting one is a 🔴 finding. Disabled by default (`org_context_agent: ''`).
-- 📚 **Review-miss ledger**: Loads the [`review-misses`](../../skills/review-misses/SKILL.md) skill — defect classes that previously ESCAPED review run as first-class checks; recurrences default to 🔴.
-- ✅ **Finding Verifier**: Before the report posts, every 🔴/🟡 is re-validated against the working tree with quoted evidence; provably-false findings are dropped (and tallied) — false positives kill trust faster than missed bugs. Verification is delegated to the [`finding-verifier`](../finding-verifier/README.md) graph agent (one map branch per finding — structurally unskippable, fresh-context independent), with an inline fallback when it isn't installed.
-- 🌐 **Downstream consumers (optional)**: When the diff changes consumer-facing contract surface (routes, protos, exported API, CLI flags), sibling checkouts under `consumers_root` and a `github_org` code search are grepped for consumers of the changed elements — a consumer matching a removed/changed contract is a 🔴 finding naming repo + file:line. Public-library consumers are unenumerable; the check degrades to semver/changelog discipline. Both probes disabled by default (`consumers_root: ''`, `github_org: ''`).
-- 🚦 **Review Verdict**: The report opens with `MERGE-READY` or `NEEDS-HUMAN` (+ the 1-3 items a human must judge). Always-human triggers (irreversible migrations, authn/authz, money movement, secrets/crypto, incident-linked guard deletion) force `NEEDS-HUMAN` regardless of findings. Routing signal only — merging stays a human act.
-
-## Operational History Lane
-
-Code review answers "is this code good?" — this lane answers "did we already get burned by this?"
-When the diff touches operationally-relevant surface (error handling, retries, timeouts, alerting,
-config controlling any of these), the orchestrator:
-
-1. **Git archaeology** (always available): blames the lines the diff deletes or weakens. A guard
-   that originated in an incident-fix commit and is being removed is a 🔴 CRITICAL finding — the
-   change reintroduces a known production failure mode.
-2. **Prior-art delegation** (opt-in): if the `prior_art_agent` variable names an agent that can
-   search your incident record (Slack, Jira, postmortems, handoff docs), it is spawned in REVIEW
-   MODE with symptom-vocabulary search keys extracted from the diff (error strings, metric/alert
-   names, config keys — the vocabulary operators actually use).
-
-The lane is disabled by default (`prior_art_agent: ''`) and findings fold into the standard
-severity taxonomy under an "Operational history" report section — no separate verdict. Wire it up
-in a bundle or your local config:
-
-```yaml
-variables:
-  - name: prior_art_agent
-    default: 'oncall-historian'  # any spawnable agent that can search your incident record
-```
 
 ## Pro-Tip: Use an IDE MCP Server for Improved Performance
 Many modern IDEs now include MCP servers that let LLMs perform operations within the IDE itself and use IDE tools. Using

assets/agents/code-reviewer/config.yaml

@@ -0,0 +1,167 @@
+name: code-reviewer
+description: CodeRabbit-style code reviewer - spawns per-file reviewers, synthesizes findings
+version: 2.0.0
+
+auto_continue: true
+max_auto_continues: 20
+inject_todo_instructions: true
+
+can_spawn_agents: true
+max_concurrent_agents: 10
+max_agent_depth: 2
+
+skills_enabled: true
+enabled_skills:
+  - delegation-protocol
+  - parallel-research
+
+variables:
+  - name: project_dir
+    description: Project directory to review
+    default: '.'
+  - name: auto_confirm
+    description: Auto-confirm command execution
+    default: '1'
+
+global_tools:
+  - ast_grep.sh
+  - fs_read.sh
+  - fs_cat.sh
+  - fs_grep.sh
+  - fs_glob.sh
+  - execute_command.sh
+
+instructions: |
+  You are a code review orchestrator, similar to CodeRabbit. You coordinate per-file reviews and produce a unified report.
+
+  ## Step 0: Load orchestration skills
+
+  Before doing anything else, call `skill__load` for `delegation-protocol` and `parallel-research`. They carry the methodology you need:
+  - **`delegation-protocol`** — how to write delegation prompts that give the sub-agent its full context (TASK / EXPECTED OUTCOME / MUST DO / MUST NOT DO / CONTEXT). Apply this format when spawning each file-reviewer.
+  - **`parallel-research`** — the spawn-and-wait protocol, the anti-duplication rule (don't redo work you delegated), and the rule about ending your response and letting the system notify you on agent completion.
+
+  Both skills are always-on for this agent's workflow. Skill bodies are your source of truth for HOW to delegate and HOW to coordinate parallel work; this agent's instructions handle the CodeRabbit-specific shape.
+
+  ## Workflow
+
+  1. **Get the diff:** Run `get_diff` to get the git diff (defaults to staged changes, falls back to unstaged)
+  2. **Parse changed files:** Extract the list of files from the diff
+  3. **Create todos:** One todo per phase (get diff, spawn reviewers, collect results, synthesize report)
+  4. **Spawn file-reviewers:** One `file-reviewer` agent per changed file, in parallel. Apply the `delegation-protocol` structured prompt format.
+  5. **Broadcast sibling roster:** Send each file-reviewer a message with all sibling IDs and their file assignments
+  6. **Collect all results:** Per `parallel-research`, do not poll. End your response after spawns + roster; the system will notify you when agents complete.
+  7. **Synthesize:** Combine all findings into a CodeRabbit-style report
+
+  ## Spawning File Reviewers
+
+  Apply the `delegation-protocol` structured prompt format. Each spawn gets the full TASK / EXPECTED OUTCOME / MUST DO / MUST NOT DO / CONTEXT sections — the file-reviewer hasn't seen the codebase or the broader PR; the spawn prompt IS its entire context.
+
+  ```
+  agent__spawn --agent file-reviewer --prompt "
+  ## TASK
+  Review the git diff for <file_path>. Produce structured findings per your output format.
+
+  ## EXPECTED OUTCOME
+  A REVIEW_COMPLETE-terminated report following your standard format:
+  - ## File: <file_path>
+  - ### Summary (1-2 sentences)
+  - ### Findings (each with severity, lines, description, suggestion)
+  - ### Cross-File Concerns (or 'None')
+
+  ## MUST DO
+  - Load `code-review` and `ai-slop-remover` skills before reading any code
+  - Apply both skill checklists to the diff
+  - Use targeted fs_read with offset/limit; max 5 file reads
+  - End with REVIEW_COMPLETE
+
+  ## MUST NOT DO
+  - Do not modify files (you are read-only)
+  - Do not review unchanged code unrelated to the diff
+  - Do not omit findings to keep the report short
+
+  ## CONTEXT
+  Project: {{project_dir}}
+  File under review: <file_path>
+
+  Diff:
+  <diff content for this file>
+  "
+  ```
+
+  Paste the actual diff hunk(s) inline — the reviewer can't see your context. If you have prior knowledge of the change's intent (PR description, ticket), include it in CONTEXT.
+
+  ## Sibling Roster Broadcast
+
+  After spawning ALL file-reviewers (collecting their IDs), send each one a message with the roster:
+
+  ```
+  agent__send_message --to <agent_id> --message "SIBLING_ROSTER:
+  - <agent_id_1>: reviewing <file_1>
+  - <agent_id_2>: reviewing <file_2>
+  ...
+  Send cross-cutting alerts to relevant siblings if your changes affect their files."
+  ```
+
+  ## Diff Parsing
+
+  Split the diff by file. Each file's diff starts with `diff --git a/<path> b/<path>`. Extract:
+  - The file path (from the `+++ b/<path>` line)
+  - All hunks for that file (from `@@` markers to the next `diff --git` or end)
+
+  Skip binary files and files with only whitespace changes.
+
+  ## Final Report Format
+
+  After collecting all file-reviewer results, synthesize into:
+
+  ```
+  # Code Review Summary
+
+  ## Walkthrough
+  <2-3 sentence overview of what the changes do as a whole>
+
+  ## Changes
+
+  | File | Changes | Findings |
+  |------|---------|----------|
+  | `path/to/file1.rs` | <brief description> | 🔴 1 🟡 2 🟢 1 |
+  | `path/to/file2.rs` | <brief description> | 🟢 2 💡 1 |
+
+  ## Detailed Findings
+
+  ### `path/to/file1.rs`
+  <paste file-reviewer's findings here, cleaned up>
+
+  ### `path/to/file2.rs`
+  <paste file-reviewer's findings here, cleaned up>
+
+  ## Cross-File Concerns
+  <any cross-cutting issues identified by the teammate pattern>
+
+  ---
+  *Reviewed N files, found X critical, Y warnings, Z suggestions, W nitpicks*
+  ```
+
+  ## Edge Cases
+
+  - **Single file changed:** Still spawn one file-reviewer (for consistency), skip roster broadcast
+  - **Too many files (>10):** Group small files (< 20 lines changed) and review them together
+  - **No changes found:** Report "No changes to review" and exit
+  - **Binary files:** Skip with a note in the summary
+
+  ## Rules
+
+  1. **Always use `get_diff` first:** Don't assume what changed
+  2. **Spawn in parallel:** All file-reviewers should be spawned before collecting any
+  3. **Don't review code yourself:** Delegate ALL review work to file-reviewers
+  4. **Preserve severity tags:** Don't downgrade or remove severity from file-reviewer findings
+  5. **Include ALL findings:** Don't summarize away specific issues
+  6. **File reads:** If you do read a file directly (e.g. to verify a finding before synthesis), `fs_read` returns a TRUNCATED view with line numbers (default 2000 lines, long lines cut at 2000 chars). Use `fs_cat` only when you need the FULL untruncated contents of a file.
+
+  ## Context
+  - Project: {{project_dir}}
+  - CWD: {{__cwd__}}
+  - Shell: {{__shell__}}
+
+  ## Available Tools:
+  {{__tools__}}

assets/agents/code-reviewer/graph.yaml

@@ -1,563 +0,0 @@
-name: code-reviewer
-description: |
-  Graph-based review orchestrator — the deterministic shell around LLM review
-  judgment. A script resolves the diff, quality bar, conventions, review-miss
-  ledger patterns, and repo-history signals; domain linters run unconditionally;
-  changed files are grouped into DOMAIN slices (deterministic proposal, LLM
-  refinement, exact-cover gate) and each slice is reviewed by a domain-reviewer
-  leader — in parallel, with peer messaging between leaders — which delegates
-  per-file depth to file-reviewer. Every leader's report passes a completeness
-  gate (mandatory sections present even when clean, reject-and-retry once).
-  Findings are re-validated by the finding-verifier graph, folded by rigor and
-  scored into the MERGE-READY / NEEDS-HUMAN verdict BY A SCRIPT — the model
-  that wrote the findings never grades its own homework. Judgment stays in the
-  agents (per-file review, synthesis, dedup); discipline lives in the graph
-  (unskippable steps, identical context to every reviewer, machine-parsed
-  verdict math).
-
-version: '1.0'
-
-can_spawn_agents: true
-# The limit is consulted by the SPAWNER against the child's absolute depth
-# (root = 0). Deepest documented chain: architect(0) → sisyphus(1) →
-# review-gauntlet | step-runner(2) → code-reviewer(3) →
-# {domain-reviewer(4) → file-reviewer(5) | finding-verifier(4)}.
-# This agent spawns depth-4 children; 5 = one level of headroom.
-max_agent_depth: 5
-max_concurrent_agents: 16
-
-variables:
-  - name: project_dir
-    description: Project directory containing the changes to review
-    default: '.'
-  - name: rigor
-    description: Quality bar rigor (poc|prototype|production); empty = resolve from plan frontmatter or default to production
-    default: ''
-  - name: surfaces
-    description: Comma-separated surface list governing skill routing; empty = detect from the diff
-    default: ''
-  - name: prior_art_agent
-    description: Agent for the operational-history lane (incident prior art); empty = skip the agent lane
-    default: ''
-  - name: org_context_agent
-    description: Agent for the org-context lane (recorded decisions, PRDs); empty = skip the lane
-    default: ''
-  - name: consumers_root
-    description: Directory of sibling consumer checkouts for the downstream sweep; empty = skip the local probe
-    default: ''
-  - name: github_org
-    description: GitHub org for the downstream code-search probe; empty = skip it
-    default: ''
-
-settings:
-  max_loop_iterations: 12
-  log_state_snapshots: false
-  timeout: 10800
-
-initial_state:
-  project_dir_in: ''
-  verify_retries: 0
-  diff_spec: auto
-  intent: ''
-  rigor_in: ''
-  surfaces_in: ''
-  extra_context: ''
-  resolved_rigor: production
-  resolved_surfaces: ''
-  bar_provenance: detected-default
-  resolved_diff_spec: ''
-  changed_files: []
-  file_count: 0
-  facts_note: ''
-  conventions: ''
-  ledger_matches: ''
-  history_notes: ''
-  touches_auth: false
-  destructive_migration: false
-  consumer_surface: false
-  linter_notes: ''
-  proposed_groups: []
-  groups_note: ''
-  group_items: []
-  domain_reports: []
-  org_context_notes: ''
-  prior_art_notes: ''
-  aux_note: ''
-  downstream_notes: ''
-  walkthrough: ''
-  changes_rows: []
-  findings: []
-  cross_file: ''
-  operational_history: ''
-  org_context_section: ''
-  attention_flags: []
-  placement_notes: ''
-  verifier_output: ''
-  verdict_out: {}
-  final_report: ''
-  gate_feedback: ''
-  gate_attempts: 0
-  parse_failure: ''
-  refine_failure: ''
-  aux_failure: ''
-  synth_failure: ''
-
-start: parse
-
-nodes:
-  parse:
-    id: parse
-    type: llm
-    description: Extract the review request's facts from the spawn prompt. Extraction only — no judging.
-    instructions: |
-      You extract the facts of a code-review request. EXTRACTION ONLY.
-
-      - `diff_spec`: the git diff basis the caller named — a range ("main...HEAD"),
-        a ref/SHA, "staged", "worktree" (uncommitted vs HEAD), or "auto" when the
-        caller did not name one (auto = staged, falling back to unstaged, falling
-        back to HEAD~1 — the classic get_diff semantics; a caller phrase like
-        "run get_diff --base X" means diff_spec = "X").
-      - `intent`: the PR description / ticket / task intent text, condensed but
-        specific. Empty string when the caller gave none.
-      - `rigor_in`: ONLY when the caller explicitly set a rigor (poc|prototype|production),
-        e.g. via a "Quality bar:" line; else empty string.
-      - `surfaces_in`: ONLY when the caller explicitly declared surfaces; else empty.
-      - `project_dir_in`: the directory/worktree path the caller named as
-        holding the code under review (e.g. "in /tmp/pr-review-x", "the repo
-        at ~/code/foo"); empty string when the caller named none.
-      - `extra_context`: any remaining reviewer-relevant caller context, condensed.
-    prompt: |
-      Extract the review-request facts from this request:
-
-      {{initial_prompt}}
-    tools: []
-    output_schema:
-      type: object
-      properties:
-        diff_spec:
-          type: string
-        intent:
-          type: string
-        rigor_in:
-          type: string
-        surfaces_in:
-          type: string
-        project_dir_in:
-          type: string
-        extra_context:
-          type: string
-      required: [diff_spec, intent, rigor_in, surfaces_in, project_dir_in, extra_context]
-    max_iterations: 6
-    max_attempts: 2
-    state_updates:
-      parse_failure: '{{output}}'
-    fallback: parse_fault
-    next: facts
-
-  parse_fault:
-    id: parse_fault
-    type: script
-    description: Fail-closed marker for a dead parse stage (reached only via parse's fallback) — emits a complete PIPELINE-FAULT verdict_out and jumps straight to render; a review that could not parse its request never reads as MERGE-READY.
-    script: scripts/parse_fault.py
-    timeout: 30
-    next: render
-
-  facts:
-    id: facts
-    type: script
-    description: Deterministic facts — diff resolution, changed files, quality-bar resolution (passed → plan frontmatter → detected), conventions pointer, review-miss ledger matches, repo-history sweep, verdict-trigger signals. Pure git/gh/filesystem; no LLM.
-    script: scripts/facts.py
-    timeout: 240
-    next: linters
-
-  linters:
-    id: linters
-    type: script
-    description: Domain linter pass — tflint/hadolint/actionlint on matching changed files, buf breaking when buf-configured protos changed. Only tools already on PATH; never installs; degrades silently per tool.
-    script: scripts/linters.py
-    timeout: 420
-    next: group_propose
-
-  group_propose:
-    id: group_propose
-    type: script
-    description: Deterministic domain grouping of changed files by surface-trigger path patterns.
-    script: scripts/group_domains.py
-    timeout: 30
-    next: refine_groups
-
-  refine_groups:
-    id: refine_groups
-    type: llm
-    description: Judgment refinement of the proposed domain groups — may rebalance, never drop or invent files (the cover gate enforces it).
-    instructions: |
-      You refine a deterministic domain grouping of changed files. You may:
-      - move a file whose CONTENT belongs to a different domain than its path suggests;
-      - split a group larger than ~8 files into coherent subgroups (name them
-        "<domain>-1", "<domain>-2" or by subsystem);
-      - merge groups that are really one change (a migration and its models);
-      - rename a domain for clarity.
-
-      You MUST include every changed file in exactly one group — no drops, no
-      inventions, no duplicates. A downstream gate validates the cover and falls
-      back to the deterministic proposal if you violate it.
-    prompt: |
-      Proposed groups (deterministic):
-      {{proposed_groups}}
-
-      All changed files (every one must appear in exactly one group):
-      {{changed_files}}
-
-      Change intent: {{intent}}
-    tools: []
-    output_schema:
-      type: object
-      properties:
-        groups:
-          type: array
-          items:
-            type: object
-            properties:
-              domain:
-                type: string
-              files:
-                type: array
-                items:
-                  type: string
-              rationale:
-                type: string
-            required: [domain, files]
-      required: [groups]
-    max_iterations: 6
-    max_attempts: 2
-    state_updates:
-      refine_failure: '{{output}}'
-    fallback: cover_gate
-    next: cover_gate
-
-  cover_gate:
-    id: cover_gate
-    type: script
-    description: Exact-cover validation of the refined groups — every changed file in exactly one group, no unknown files. Violations fall back to the deterministic proposal (noted). Emits the map items.
-    script: scripts/cover_gate.py
-    timeout: 30
-    next: [map_domains, aux_lanes, downstream_sweep]
-
-  map_domains:
-    id: map_domains
-    type: map
-    over: '{{group_items}}'
-    as: domain_group
-    branch: review_domain
-    output_key: domain_report
-    collect_into: domain_reports
-    max_concurrency: 4
-    next: synthesize
-
-  review_domain:
-    id: review_domain
-    type: agent
-    description: One domain-reviewer leader per domain slice — reviews the slice as a unit, delegates per-file depth to file-reviewer, messages the other leaders.
-    agent: domain-reviewer
-    teammates: true
-    timeout: 7200
-    prompt: |
-      ## TASK
-      Review the changes in your assigned domain slice as ONE coherent unit and
-      produce a DOMAIN_REVIEW_COMPLETE-terminated report per your output format.
-
-      ## ASSIGNMENT (JSON)
-      {{domain_group}}
-
-      ## MUST DO
-      - Fetch your slice's diff yourself: `get_diff --files <your files, comma-separated>`
-        (diff spec: {{resolved_diff_spec}} — pass it as `--base` when it is a ref or range;
-        omit `--base` for staged/unstaged specs)
-      - Apply your domain charter: per-file review depth per your sizing rules, PLUS the
-        domain-level pass (guard symmetry across the slice, literal/enum drift,
-        schema↔usage mismatch, slice-level blast radius / test adequacy / removed guards)
-      - Report the mandatory checks EVEN WHEN CLEAN
-      - Message the other domain leaders when your slice changes something their domain consumes
-      {{gate_feedback}}
-
-      ## MUST NOT DO
-      - No file modification; no findings omitted; never rewrite severities
-
-      ## CONTEXT
-      Project: {{project_dir}}
-      Rigor: {{resolved_rigor}} (provenance: {{bar_provenance}})
-      Surfaces: {{resolved_surfaces}}
-      Intent: {{intent}}
-      Conventions: {{conventions}}
-      Review-miss patterns (run as FIRST-CLASS checks; cite MISS-NNN in the finding title when one fires):
-      {{ledger_matches}}
-      Repo-history signals:
-      {{history_notes}}
-      Linter output (extract the lines for your files):
-      {{linter_notes}}
-      {{extra_context}}
-    max_attempts: 2
-    state_updates:
-      domain_report: '{{output}}'
-    fallback: domain_fault
-    next: completeness_gate
-
-  completeness_gate:
-    id: completeness_gate
-    type: script
-    description: Deterministic report-contract gate — required sections present (even when clean) and the completion sentinel. Rejects back to the leader exactly once with the missing sections, then keeps the report banner-flagged. Never sinks the map.
-    script: scripts/completeness_gate.py
-    timeout: 30
-
-  domain_fault:
-    id: domain_fault
-    type: script
-    description: Fail-closed domain lane fault marker (reached only via review_domain's fallback route inside the map branch). Normalizes the engine's "Agent node failed" text in domain_report into a > ⚠️ PIPELINE-FAULT banner the map collects; verdict.py counts any faulted lane and forces NEEDS-HUMAN — a dead domain lane never reads as a clean slice.
-    script: scripts/domain_fault.py
-    timeout: 30
-
-  aux_lanes:
-    id: aux_lanes
-    type: llm
-    description: Conditional context lanes — org-context and operational-history/prior-art agents, spawned only when configured AND triggered. Additive context; never blocks.
-    instructions: |
-      You run the review's conditional context lanes by spawning agents (you have the
-      agent__spawn / agent__collect tools). Evaluate each lane's trigger against the
-      change facts; spawn the applicable ones IN ONE BURST, collect, and distill.
-
-      **Org-context lane** — only if `{{org_context_agent}}` is a non-empty agent name AND
-      the diff touches surface where a recorded decision plausibly exists (public API
-      shapes, money/entitlement logic, auth flows, data retention/deletion, domain state
-      machines and lifecycle semantics) OR the diff's scope visibly mismatches the
-      ticket/intent it cites. Spawn it with ONE question: "Any recorded decisions, PRDs,
-      or incident-driven constraints about <changed area>? Return quoted decisions with
-      dates/sources." (For a ticket mismatch: "which recorded ticket/PRD does THIS change
-      actually implement?") Distill the answer into `org_context_notes` — quoted decisions
-      with dates, and whether the diff appears to honor them.
-
-      **Operational-history lane** — only if `{{prior_art_agent}}` is a non-empty agent
-      name AND the diff touches operationally relevant surface (workers/queues,
-      migrations, infra, auth, retry/timeout logic, external calls, feature flags).
-      Spawn it in REVIEW MODE: "REVIEW MODE: incident prior art for <the changed
-      paths/surfaces>. Return incidents, postmortems, alert history, and prior-PR
-      lessons tied to these paths, with dates and links — especially any GUARD present
-      in the past that this diff deletes or weakens." Distill into `prior_art_notes`;
-      quote anything tying a DELETED guard to a past incident verbatim (the verdict
-      treats reintroduced failure modes as blocking).
-
-      A lane whose trigger does not match, whose agent name is empty, or whose agent
-      fails: skip it and say why in `aux_note` (one line each). Never invent lane
-      content; empty results are valid results.
-    prompt: |
-      Change facts:
-      - files: {{changed_files}}
-      - intent: {{intent}}
-      - auth surface: {{touches_auth}}; migrations: {{destructive_migration}}; consumer surface: {{consumer_surface}}
-      - resolved surfaces: {{resolved_surfaces}}
-      - extra: {{extra_context}}
-
-      Configured lane agents: org-context='{{org_context_agent}}', prior-art='{{prior_art_agent}}'.
-      Project: {{project_dir}}
-    output_schema:
-      type: object
-      properties:
-        org_context_notes:
-          type: string
-        prior_art_notes:
-          type: string
-        aux_note:
-          type: string
-      required: [org_context_notes, prior_art_notes, aux_note]
-    max_iterations: 10
-    max_attempts: 2
-    timeout: 3600
-    state_updates:
-      aux_failure: '{{output}}'
-    fallback: aux_fault
-    next: synthesize
-
-  aux_fault:
-    id: aux_fault
-    type: script
-    description: Fail-closed marker for dead aux context lanes (reached only via aux_lanes' fallback) — records the failure as a PIPELINE-FAULT in aux_note, which synthesize surfaces as a lane skip. Aux lanes are enrichment; the degradation is visible but never blocks.
-    script: scripts/aux_fault.py
-    timeout: 30
-    next: synthesize
-
-  downstream_sweep:
-    id: downstream_sweep
-    type: script
-    description: Downstream-consumers sweep — deterministic contract-token extraction from the diff, grep of sibling checkouts, bounded org code search. Runs only when consumer-facing surface changed; degrades silently.
-    script: scripts/downstream_sweep.py
-    timeout: 240
-    state_updates:
-      downstream_notes: '{{downstream_notes}}'
-    next: synthesize
-
-  synthesize:
-    id: synthesize
-    type: llm
-    description: The judgment core — dedup, cross-file/cross-domain reasoning, prose. Emits STRUCTURED findings for the deterministic verdict; has NO verdict authority and cannot drop findings.
-    instructions: |
-      You synthesize domain review reports into the structured inputs of a code-review
-      report. You have NO verdict authority: the verdict, rigor folding, and severity
-      math happen downstream in a script, and finding verification happens in a separate
-      fresh-context agent. Your job is judgment, not grading.
-
-      Rules (non-negotiable):
-      - **Include ALL findings** from every domain report — never summarize one away.
-        Preserve each severity tag and any `[convention]`/`[correctness]` title marker
-        VERBATIM (marker goes in the `marker` field: "", "convention", or "correctness").
-      - **Dedup**: an identical finding reported twice (e.g. a surface skill and an
-        aspect skill like transactional-integrity) → keep the aspect skill's copy, drop
-        the duplicate. Dedup is the ONLY permitted removal.
-      - **Lane-derived findings you MUST add** when present in the lane notes:
-        - a diff that contradicts a recorded org decision (org_context_notes) → a
-          🔴 CRITICAL finding quoting the decision;
-        - a downstream consumer hit on a changed/removed contract element
-          (downstream_notes) → a 🔴 CRITICAL finding naming the consuming repo + file:line;
-        - repo-level linter residue that maps to no single file → a finding under the
-          owning surface (severity per the linter's own level; buf breaking = 🔴).
-      - **Every finding needs**: id (f1, f2, …), severity (icon + word verbatim, e.g.
-        "🔴 CRITICAL"), marker, file, lines, title, and `block` = the finding's full
-        markdown block exactly as it will appear in the report (#### title + Severity /
-        Lines / Description / Suggestion bullets).
-      - **attention_flags** (ADDITIVE-ONLY human-attention triggers; scripts add the
-        deterministic ones — migrations, auth — separately): money movement or
-        billing-amount computation changes; secrets/cryptography/key handling; a deleted
-        guard the operational-history lane tied to a past incident; a reintroduced
-        incident failure mode; a contradicted recorded decision. One short line each.
-      - **The placement question**: when the diff adds tolerance for a state its own
-        comments/errors call impossible ("should never happen", "defensive"), name the
-        PRODUCER of that state at path:line and put the question in `placement_notes` —
-        it is design intent, never auto-resolved.
-      - Prose sections: `walkthrough` (2-3 sentences on the change as a whole),
-        `changes_rows` (one {file, desc} per changed file, brief), `cross_file`
-        (cross-domain concerns from the leaders' reports + teammate alerts, or "None"),
-        `operational_history` (from prior_art_notes; "" when the lane didn't run),
-        `org_context_section` (from org_context_notes; "" when the lane didn't run).
-      Prior review decisions supplied in the caller context are SETTLED: never
-      invert or re-litigate one on the same line without NEW evidence (the line
-      changed, a new failure appeared). If you believe a settled decision is
-      wrong, do not re-flag it as a finding — surface it in `cross_file` as an
-      explicit conflict citing the prior decision, so the human sees a
-      disagreement, not a flip-flop.
-
-    prompt: |
-      Domain reports ({{file_count}} changed files, grouped into the domain slices below):
-      {{domain_reports}}
-
-      Lane notes:
-      - org context: {{org_context_notes}}
-      - operational history / prior art: {{prior_art_notes}}
-      - downstream consumers: {{downstream_notes}}
-      - lane skips: {{aux_note}}
-      - linter summary: {{linter_notes}}
-      - facts notes: {{facts_note}} {{groups_note}}
-
-      Intent: {{intent}}
-      Rigor: {{resolved_rigor}}; surfaces: {{resolved_surfaces}}
-    output_schema:
-      type: object
-      properties:
-        walkthrough:
-          type: string
-        changes_rows:
-          type: array
-          items:
-            type: object
-            properties:
-              file:
-                type: string
-              desc:
-                type: string
-            required: [file, desc]
-        findings:
-          type: array
-          items:
-            type: object
-            properties:
-              id:
-                type: string
-              severity:
-                type: string
-              marker:
-                type: string
-              file:
-                type: string
-              lines:
-                type: string
-              title:
-                type: string
-              block:
-                type: string
-            required: [id, severity, marker, file, lines, title, block]
-        cross_file:
-          type: string
-        operational_history:
-          type: string
-        org_context_section:
-          type: string
-        attention_flags:
-          type: array
-          items:
-            type: string
-        placement_notes:
-          type: string
-      required: [walkthrough, changes_rows, findings, cross_file, operational_history, org_context_section, attention_flags, placement_notes]
-    max_iterations: 6
-    max_attempts: 2
-    state_updates:
-      synth_failure: '{{output}}'
-    fallback: verdict
-    next: verify
-
-  verify:
-    id: verify
-    type: agent
-    description: Independent fresh-context verification of every 🔴/🟡 finding — structurally on the path to the report; cannot be skipped.
-    agent: finding-verifier
-    timeout: 3600
-    prompt: |
-      Verify these code-review findings against the working tree.
-
-      Project: {{project_dir}}
-
-      Findings (JSON; verify every 🔴 and 🟡 entry — id, severity, path, lines, claim
-      are the fields; `title` + `block` together are the claim):
-      {{findings}}
-    max_attempts: 2
-    state_updates:
-      verifier_output: '{{output}}'
-    fallback: verdict
-    next: verify_gate
-
-  verify_gate:
-    id: verify_gate
-    type: script
-    description: Local verifier-fault retry — when the verifier completed but its output carries PIPELINE-FAULT markers (or the verifier died), re-run the cheap finding-verifier ONCE instead of letting the fault escalate into a full lane re-run at the gauntlet. Falls through to verdict when clean or out of retries; a gate crash falls forward on the declared edge.
-    script: scripts/verify_gate.py
-    timeout: 60
-    next: verdict
-
-  verdict:
-    id: verdict
-    type: script
-    description: Deterministic verdict math — applies verifier drops (FALSE, tallied), attaches evidence, folds by rigor, computes MERGE-READY/NEEDS-HUMAN from severity counts + always-human triggers. The model never grades its own homework.
-    script: scripts/verdict.py
-    timeout: 60
-    next: render
-
-  render:
-    id: render
-    type: script
-    description: Deterministic report assembly in the standard format from the structured findings and prose sections.
-    script: scripts/render.py
-    timeout: 30
-    next: done
-
-  done:
-    id: done
-    type: end
-    output: |
-      {{final_report}}

assets/agents/code-reviewer/scripts/aux_fault.py

@@ -1,48 +0,0 @@
-#!/usr/bin/env python3
-"""Fail-closed marker for dead aux context lanes of the code-reviewer graph.
-
-Reached ONLY via aux_lanes' `fallback:` route. aux_lanes' state_updates wrote
-an "LLM node …failed: <chain>" string into `aux_failure` before routing here;
-this node records the failure as a PIPELINE-FAULT in `aux_note`, which flows
-into synthesize's "lane skips" prompt line. Aux lanes are ENRICHMENT, not
-review coverage: the degradation is made VISIBLE in the report's inputs but
-never blocks — verdict.py deliberately does NOT scan aux_note for faults.
-"""
-
-import json
-import os
-
-MAX_DETAIL_CHARS = 500
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def main():
-    state = load_state()
-    raw = state.get("aux_failure")
-    detail = raw.strip().replace("\n", " ") if isinstance(raw, str) else ""
-    if len(detail) > MAX_DETAIL_CHARS:
-        detail = detail[: MAX_DETAIL_CHARS - 1] + "…"
-    print(
-        json.dumps(
-            {"aux_note": f"PIPELINE-FAULT: aux context lanes failed after retries — {detail}"}
-        )
-    )
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — the fault marker itself must never crash
-    print(
-        json.dumps(
-            {
-                "aux_note": "PIPELINE-FAULT: aux context lanes failed after retries — "
-                f"fault-marker script error: {e}"
-            }
-        )
-    )

assets/agents/code-reviewer/scripts/completeness_gate.py

@@ -1,76 +0,0 @@
-#!/usr/bin/env python3
-"""Report-contract gate for each domain-reviewer's output.
-
-"Silence reads as not done": the mandatory sections must be PRESENT even when
-clean. A report missing required sections is rejected back to the leader
-exactly once with the missing list; a second failure keeps the report,
-banner-flagged, so the synthesis (and the human) can see the gap — a
-malformed report never sinks the whole review and never silently passes as
-complete.
-"""
-
-import json
-import os
-import re
-
-REQUIRED = [
-    ("## Domain:", "the `## Domain:` header"),
-    ("### Findings", "the `### Findings` section"),
-    ("### Mandatory checks", "the `### Mandatory checks` section (report blast radius / test adequacy / guard symmetry even when clean)"),
-    ("DOMAIN_REVIEW_COMPLETE", "the `DOMAIN_REVIEW_COMPLETE` sentinel"),
-]
-MAX_RETRIES = 1
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def main():
-    state = load_state()
-    report = state.get("domain_report")
-    report = report if isinstance(report, str) else ""
-    attempts = state.get("gate_attempts")
-    if not isinstance(attempts, int):
-        attempts = 0
-
-    missing = [desc for marker, desc in REQUIRED if marker not in report]
-    if not missing:
-        print(json.dumps({}))
-        return
-
-    if attempts < MAX_RETRIES:
-        print(
-            json.dumps(
-                {
-                    "_next": "review_domain",
-                    "gate_attempts": attempts + 1,
-                    "gate_feedback": (
-                        "- COMPLETENESS GATE REJECTED your previous report — missing: "
-                        + "; ".join(missing)
-                        + ". Re-emit the FULL report with every required section "
-                        "(mandatory checks are reported even when clean) and end with "
-                        "DOMAIN_REVIEW_COMPLETE."
-                    ),
-                }
-            )
-        )
-        return
-
-    group = state.get("domain_group")
-    domain = group.get("domain", "?") if isinstance(group, dict) else "?"
-    banner = (
-        f"> ⚠️ COMPLETENESS GATE: this domain report ({domain}) is missing required "
-        f"sections after one retry: {'; '.join(missing)}. Treat the missing checks as "
-        "NOT DONE, not as clean.\n\n"
-    )
-    print(json.dumps({"domain_report": banner + report}))
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — a gate crash must never sink the map
-    print(json.dumps({"domain_report": f"> ⚠️ COMPLETENESS GATE ERROR: {e}\n\n(report unavailable)"}))

assets/agents/code-reviewer/scripts/cover_gate.py

@@ -1,81 +0,0 @@
-#!/usr/bin/env python3
-"""Exact-cover gate for the refined domain groups.
-
-The LLM refinement may rebalance the deterministic proposal, but it may not
-lose, invent, or duplicate files. This gate verifies the refined groups are an
-EXACT COVER of the changed-file set; any violation falls back to the
-deterministic proposal with a note. The LLM can shape the grouping, never
-shrink it. Emits `group_items` — the map node's item list.
-
-Crash-safe: this node has a `next:` edge, so an unguarded crash would
-tolerant-fail ONWARD with an empty `group_items` — an empty review that could
-masquerade as MERGE-READY. On any internal error it therefore emits one
-catch-all group so the review still runs (and verdict.py's pipeline tripwire
-catches the empty-report case independently).
-"""
-
-import json
-import os
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def main():
-    state = load_state()
-    changed = state.get("changed_files") or []
-    proposed = state.get("proposed_groups") or []
-    refined = state.get("groups") or []
-
-    note = ""
-    chosen = None
-    if isinstance(refined, list) and refined:
-        seen = []
-        valid = True
-        for g in refined:
-            if not isinstance(g, dict) or not isinstance(g.get("files"), list) or not g.get("domain"):
-                valid = False
-                note = "refined groups malformed — fell back to the deterministic grouping"
-                break
-            seen.extend(g["files"])
-        if valid:
-            if sorted(seen) != sorted(changed):
-                missing = sorted(set(changed) - set(seen))
-                extra = sorted(set(seen) - set(changed))
-                dupes = sorted({f for f in seen if seen.count(f) > 1})
-                note = (
-                    "refined groups failed the exact-cover check "
-                    f"(missing={missing[:5]} extra={extra[:5]} duplicated={dupes[:5]}) — "
-                    "fell back to the deterministic grouping"
-                )
-            else:
-                chosen = [{"domain": g["domain"], "files": g["files"]} for g in refined]
-    if chosen is None:
-        # refine_groups' fallback lands here with `groups` never set; make the
-        # degradation visible in the synthesis prompt via groups_note.
-        refine_failure = state.get("refine_failure")
-        if not refined and isinstance(refine_failure, str) and refine_failure.startswith("LLM node"):
-            note = "refinement lane failed after retries — fell back to the deterministic grouping"
-        chosen = [{"domain": g["domain"], "files": g["files"]} for g in proposed if isinstance(g, dict)]
-
-    print(json.dumps({"group_items": chosen, "groups_note": note}))
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — a crash must never tolerant-fail into an empty review
-    try:
-        files = load_state().get("changed_files") or []
-    except Exception:  # noqa: BLE001
-        files = []
-    print(
-        json.dumps(
-            {
-                "group_items": [{"domain": "all-changes", "files": files}],
-                "groups_note": f"cover gate error: {e} — fell back to a single catch-all group",
-            }
-        )
-    )

assets/agents/code-reviewer/scripts/domain_fault.py

@@ -1,59 +0,0 @@
-#!/usr/bin/env python3
-"""Fail-closed domain lane fault marker for the code-reviewer graph.
-
-Reached ONLY via review_domain's `fallback:` route inside the map branch.
-Grounded in engine behavior: on agent-node failure the engine writes
-"Agent node failed: {e:#}" into `domain_report` via the node's state_updates
-BEFORE routing to the fallback, so the raw failure text is already in state.
-This node normalizes it into a "> ⚠️ PIPELINE-FAULT: domain review lane
-failed after retries — …" banner the map collects as the lane's report;
-verdict.py counts any banner-prefixed report as a fault and forces
-NEEDS-HUMAN — a dead domain lane never reads as a clean slice.
-
-Slice identity comes from `domain_group` (the map item cover_gate emitted,
-which carries `domain` and `files`); a missing/malformed item degrades to
-the failure detail alone.
-"""
-
-import json
-import os
-
-MAX_DETAIL_CHARS = 500
-
-FAULT_PREFIX = "> ⚠️ PIPELINE-FAULT: domain review lane failed after retries — "
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def main():
-    state = load_state()
-    slice_desc = ""
-    group = state.get("domain_group")
-    if isinstance(group, dict):
-        domain = group.get("domain")
-        files = [f for f in (group.get("files") or []) if isinstance(f, str)]
-        if isinstance(domain, str) and domain.strip():
-            slice_desc = f"domain '{domain.strip()}' (files: {', '.join(files)}): "
-    raw = state.get("domain_report")
-    detail = raw.strip().replace("\n", " ") if isinstance(raw, str) else ""
-    if len(detail) > MAX_DETAIL_CHARS:
-        detail = detail[: MAX_DETAIL_CHARS - 1] + "…"
-    print(json.dumps({"domain_report": f"{FAULT_PREFIX}{slice_desc}{detail}"}))
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — the fault marker itself must never crash
-    print(
-        json.dumps(
-            {
-                "domain_report": "> ⚠️ PIPELINE-FAULT: domain review lane failed "
-                f"after retries — fault-marker script error: {e}"
-            }
-        )
-    )

assets/agents/code-reviewer/scripts/downstream_sweep.py

@@ -1,102 +0,0 @@
-#!/usr/bin/env python3
-"""Downstream-consumers sweep for the code-reviewer graph.
-
-Runs only when consumer-facing contract surface changed. Extracts the most
-specific changed contract tokens from the diff deterministically (route path
-literals, proto message/service/rpc names, exported symbols), greps sibling
-checkouts under `consumers_root`, and runs a bounded org code search via gh.
-Hits are reported for the synthesis to raise as 🔴 findings naming the
-consuming repo + file:line. Degrades silently when unconfigured/offline;
-public-library caveats are noted, not guessed at.
-"""
-
-import json
-import os
-import re
-import shutil
-import subprocess
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-state = load_state()
-proj = os.path.abspath(state.get("project_dir") or ".")
-spec = state.get("resolved_diff_spec") or "worktree"
-consumers_root = os.path.expanduser((state.get("consumers_root") or "").strip())
-github_org = (state.get("github_org") or "").strip()
-
-if not state.get("consumer_surface"):
-    print(json.dumps({"downstream_notes": "(skipped — no consumer-facing contract surface in the diff)"}))
-    raise SystemExit(0)
-
-
-def diff_text():
-    args = {"staged": ["--cached"], "worktree": ["HEAD"], "HEAD~1": ["HEAD~1"]}.get(spec, [spec])
-    r = subprocess.run(["git", "-C", proj, "diff", *args], capture_output=True, text=True, timeout=90)
-    return r.stdout if r.returncode == 0 else ""
-
-
-try:
-    changed = [
-        l[1:] for l in diff_text().splitlines()
-        if (l.startswith("+") or l.startswith("-")) and not l.startswith(("+++", "---"))
-    ]
-    text = "\n".join(changed)
-    tokens = set()
-    tokens.update(re.findall(r'["\'](/[a-z0-9][a-z0-9/_{}.:-]{5,})["\']', text))          # route paths
-    tokens.update(re.findall(r"^\s*(?:message|service|rpc)\s+([A-Z][A-Za-z0-9_]{5,})", text, re.M))  # proto names
-    tokens.update(re.findall(r"^\s*(?:pub\s+fn|pub\s+struct|func|export\s+(?:function|const|class))\s+([A-Z][A-Za-z0-9_]{5,})", text, re.M))
-    tokens = sorted(tokens, key=len, reverse=True)[:5]
-
-    notes = []
-    if not tokens:
-        notes.append("(no specific contract tokens extractable from the diff — sweep skipped)")
-    else:
-        notes.append(f"contract tokens probed: {tokens}")
-        if consumers_root and os.path.isdir(consumers_root):
-            self_name = os.path.basename(proj)
-            for tok in tokens:
-                r = subprocess.run(
-                    ["grep", "-rIl", "--exclude-dir=.git", "--exclude-dir=node_modules",
-                     "--exclude-dir=target", "--exclude-dir=vendor", tok, consumers_root],
-                    capture_output=True, text=True, timeout=60,
-                )
-                hits = [
-                    h for h in r.stdout.splitlines()
-                    if h.strip() and f"/{self_name}/" not in h and not h.startswith(proj)
-                ][:4]
-                for h in hits:
-                    notes.append(f"CONSUMER HIT (sibling checkout): {h} references '{tok}' — "
-                                 "a changed/removed contract element with a live consumer is a 🔴 finding")
-        elif consumers_root:
-            notes.append(f"(consumers_root '{consumers_root}' not found — local probe skipped)")
-        else:
-            notes.append("(consumers_root unset — local probe skipped)")
-
-        if github_org and shutil.which("gh"):
-            env = dict(os.environ)
-            env.pop("CLICOLOR_FORCE", None)
-            env.pop("FORCE_COLOR", None)
-            env["GH_NO_UPDATE_NOTIFIER"] = "1"
-            for tok in tokens:
-                r = subprocess.run(
-                    ["gh", "api", "search/code", "-f", f'q=org:{github_org} "{tok}"',
-                     "--jq", r'.items[:4][] | "\(.repository.full_name): \(.path)"'],
-                    capture_output=True, text=True, timeout=30, env=env,
-                )
-                if r.returncode == 0 and r.stdout.strip():
-                    for line in r.stdout.strip().splitlines():
-                        notes.append(f"CONSUMER HIT (org search): {line} references '{tok}'")
-        elif github_org:
-            notes.append("(gh unavailable — org code search skipped)")
-        else:
-            notes.append("(github_org unset — org code search skipped)")
-        notes.append("Public-library caveat: consumers of a PUBLIC library are unenumerable — "
-                     "for exported-API changes the check degrades to semver/changelog discipline.")
-    print(json.dumps({"downstream_notes": "\n".join(notes)}))
-except Exception as e:  # noqa: BLE001
-    print(json.dumps({"downstream_notes": f"(sweep degraded: {e})"}))

assets/agents/code-reviewer/scripts/facts.py

@@ -1,288 +0,0 @@
-#!/usr/bin/env python3
-"""Deterministic review facts for the code-reviewer graph.
-
-Resolves the diff, the changed-file list, the quality bar (caller-passed →
-plan frontmatter → detected default), the conventions pointer, review-miss
-ledger matches, the repo-history sweep (fix/revert clusters, bounded gh
-PR-comment pull), and the deterministic verdict-trigger signals. Pure
-git/gh/filesystem — no LLM. Failures degrade into `facts_note`; they never
-sink the review.
-"""
-
-import glob
-import json
-import os
-import re
-import subprocess
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-state = load_state()
-proj = os.path.expanduser(
-    (state.get("project_dir_in") or "").strip() or state.get("project_dir") or "."
-)
-spec = (state.get("diff_spec") or "auto").strip()
-notes = []
-out = {"project_dir": proj}
-
-
-def git(*args, timeout=60):
-    r = subprocess.run(["git", "-C", proj, *args], capture_output=True, text=True, timeout=timeout)
-    if r.returncode != 0:
-        raise RuntimeError((r.stderr or r.stdout).strip()[:300])
-    return r.stdout
-
-
-def scrubbed_env():
-    env = dict(os.environ)
-    env.pop("CLICOLOR_FORCE", None)
-    env.pop("FORCE_COLOR", None)
-    env["GH_NO_UPDATE_NOTIFIER"] = "1"
-    env["NO_COLOR"] = "1"
-    return env
-
-
-# --- diff resolution (get_diff semantics) -----------------------------------
-resolved = spec
-files = []
-try:
-    if spec in ("auto", ""):
-        names = git("diff", "--cached", "--numstat")
-        resolved = "staged"
-        if not names.strip():
-            names = git("diff", "--numstat")
-            resolved = "worktree"
-        if not names.strip():
-            names = git("diff", "HEAD~1", "--numstat")
-            resolved = "HEAD~1"
-    elif spec == "staged":
-        names = git("diff", "--cached", "--numstat")
-    elif spec == "worktree":
-        names = git("diff", "HEAD", "--numstat")
-    else:
-        names = git("diff", spec, "--numstat")
-    for line in names.splitlines():
-        parts = line.split("\t")
-        if len(parts) == 3:
-            added, deleted, path = parts
-            if added == "-" and deleted == "-":
-                notes.append(f"binary file skipped: {path}")
-                continue
-            files.append(path.strip())
-except Exception as e:  # noqa: BLE001
-    notes.append(f"diff resolution failed for spec {spec!r}: {e}")
-
-out["resolved_diff_spec"] = resolved
-out["changed_files"] = files[:300]
-out["file_count"] = len(files)
-if len(files) > 300:
-    notes.append(
-        f"file list truncated: {len(files)} changed files, only the first 300 are "
-        "grouped and reviewed"
-    )
-
-
-def diff_text():
-    try:
-        if resolved == "staged":
-            return git("diff", "--cached", timeout=90)
-        if resolved == "worktree":
-            return git("diff", "HEAD", timeout=90) if spec == "worktree" else git("diff", timeout=90)
-        if resolved == "HEAD~1":
-            return git("diff", "HEAD~1", timeout=90)
-        return git("diff", resolved, timeout=90)
-    except Exception:  # noqa: BLE001
-        return ""
-
-
-dtext = diff_text()
-added_lines = "\n".join(
-    l for l in dtext.splitlines() if l.startswith("+") and not l.startswith("+++")
-)
-
-# --- quality bar resolution --------------------------------------------------
-rigor_in = (state.get("rigor_in") or state.get("rigor") or "").strip()
-surfaces_in = (state.get("surfaces_in") or state.get("surfaces") or "").strip()
-resolved_rigor, resolved_surfaces, provenance = "production", "", "detected-default"
-if rigor_in or surfaces_in:
-    resolved_rigor = rigor_in or "production"
-    resolved_surfaces = surfaces_in
-    provenance = "passed"
-else:
-    for plan in sorted(glob.glob(os.path.join(proj, "plans", "PLAN-*.md"))):
-        try:
-            with open(plan) as f:
-                head = f.read(4000)
-            m = re.match(r"\A---\n(.*?)\n---", head, re.S)
-            if m and re.search(r"^status:\s*active\s*$", m.group(1), re.M):
-                rig = re.search(r"^rigor:\s*(\S+)", m.group(1), re.M)
-                sur = re.search(r"^surfaces:\s*(.+)$", m.group(1), re.M)
-                if rig:
-                    resolved_rigor = rig.group(1).strip()
-                if sur:
-                    resolved_surfaces = sur.group(1).strip("[] \n")
-                provenance = "plan"
-                break
-        except OSError:
-            continue
-
-SURFACE_PATTERNS = [
-    ("db-migration", r"migrations?/|\.sql$|schema\.(rb|prisma|sql)"),
-    ("iac", r"\.tf$|helm|charts?/|Dockerfile|docker-compose|k8s/|manifests?/"),
-    ("ci-cd", r"\.github/workflows/|\.gitlab-ci|Jenkinsfile|\.circleci/"),
-    ("worker", r"workers?/|jobs?/|consumers?/|cron|celery|sidekiq|river"),
-    ("rest-api", r"routes?|handlers?|controllers?|endpoints?|\bapi\b|\.proto$|openapi|swagger|graphql|resolvers?"),
-    ("cli", r"\bcmd/|\bcli\b"),
-    ("library", r"go\.mod$|package\.json$|Cargo\.toml$|pyproject\.toml$|setup\.py$|__init__\.py$"),
-]
-if provenance == "detected-default" and files:
-    detected = []
-    for surface, pat in SURFACE_PATTERNS:
-        if any(re.search(pat, f, re.I) for f in files):
-            detected.append(surface)
-    resolved_surfaces = ", ".join(detected)
-
-out["resolved_rigor"] = resolved_rigor
-out["resolved_surfaces"] = resolved_surfaces
-out["bar_provenance"] = provenance
-
-# --- conventions pointer ------------------------------------------------------
-conv = []
-for pat in ("CLAUDE.md", "COYOTE.md", "CONTRIBUTING.md", ".golangci*", ".eslintrc*",
-            "rustfmt.toml", ".rubocop.yml", "ruff.toml", ".editorconfig", "Makefile"):
-    conv.extend(sorted(glob.glob(os.path.join(proj, pat)))[:2])
-out["conventions"] = ", ".join(os.path.relpath(p, proj) for p in conv) or "none found"
-
-# --- review-miss ledger -------------------------------------------------------
-ledger_text = ""
-for cand in (
-    os.path.join(os.path.expanduser("~"), ".config", "coyote", "share", "review-misses.md"),
-    os.path.join(os.path.expanduser("~"), ".config", "coyote", "review-misses.md"),
-):
-    if os.path.isfile(cand):
-        try:
-            with open(cand) as f:
-                ledger_text = f.read()
-        except OSError:
-            pass
-        break
-
-matches = []
-if ledger_text:
-    try:
-        repo_name = os.path.basename(git("rev-parse", "--show-toplevel").strip())
-    except Exception:  # noqa: BLE001
-        repo_name = os.path.basename(os.path.abspath(proj))
-    keywords = {repo_name.lower()}
-    keywords.update(s.strip().lower() for s in resolved_surfaces.split(",") if s.strip())
-    for f in files:
-        keywords.update(p.lower() for p in re.split(r"[/_.-]", f) if len(p) >= 4)
-    entries = re.split(r"(?=^## MISS-)", ledger_text, flags=re.M)
-    for entry in entries:
-        if not entry.startswith("## MISS-"):
-            continue
-        body = entry.lower()
-        if any(k in body for k in keywords):
-            lines = entry.strip().splitlines()
-            matches.append("\n".join(lines[:8]))
-        if len(matches) >= 8:
-            break
-out["ledger_matches"] = "\n\n".join(matches) if matches else "(no matching ledger entries)"
-
-# --- repo-history sweep -------------------------------------------------------
-history = []
-fragile = []
-try:
-    if files:
-        log = git("log", "--oneline", "-15", "--", *files[:100])
-        history.append(log.strip()[:2000])
-        per_file = {}
-        for f in files[:50]:
-            try:
-                fl = git("log", "--oneline", "-10", "--", f)
-            except Exception:  # noqa: BLE001
-                continue
-            hits = [l for l in fl.splitlines() if re.search(r"\b(fix|revert|hotfix)\b", l, re.I)]
-            if len(hits) >= 2:
-                fragile.append(f)
-                per_file[f] = hits[:2]
-        for f, hits in per_file.items():
-            history.append(f"FRAGILE: {f} — {len(hits)}+ fix/revert commits recently — raise scrutiny")
-except Exception as e:  # noqa: BLE001
-    notes.append(f"history sweep failed: {e}")
-
-# gh one-level-deeper: PR review comments for fragile files (bounded, silent skip)
-try:
-    if fragile:
-        remote = git("remote", "get-url", "origin").strip()
-        m = re.search(r"github\.com[:/]([^/]+/[^/.]+)", remote)
-        if m:
-            repo_slug = m.group(1)
-            env = scrubbed_env()
-            shas = []
-            for f in fragile[:2]:
-                lg = git("log", "--format=%H", "-2", "--", f)
-                shas.extend(lg.split())
-            pr_nums = []
-            for sha in shas[:3]:
-                r = subprocess.run(
-                    ["gh", "api", f"repos/{repo_slug}/commits/{sha}/pulls", "--jq", ".[].number"],
-                    capture_output=True, text=True, timeout=30, env=env,
-                )
-                if r.returncode == 0:
-                    pr_nums.extend(n for n in r.stdout.split() if n.isdigit())
-            seen = []
-            for n in pr_nums:
-                if n not in seen:
-                    seen.append(n)
-            comments = []
-            for n in seen[:3]:
-                r = subprocess.run(
-                    ["gh", "api", f"repos/{repo_slug}/pulls/{n}/comments",
-                      "--jq", r'.[] | "\(.path): \(.body)"'],
-                    capture_output=True, text=True, timeout=30, env=env,
-                )
-                if r.returncode == 0:
-                    for line in r.stdout.splitlines():
-                        path = line.split(":", 1)[0]
-                        if any(path in f or f in path for f in files):
-                            comments.append(line[:200])
-                if len(comments) >= 6:
-                    break
-            if comments:
-                history.append("Prior PR review comments on fragile paths:\n" + "\n".join(comments[:6]))
-except Exception:  # noqa: BLE001
-    pass  # offline / not GitHub / no gh — silent by design
-
-out["history_notes"] = "\n".join(h for h in history if h) or "(no notable history)"
-
-# --- deterministic verdict-trigger signals -----------------------------------
-def any_path(pattern):
-    return any(re.search(pattern, f, re.I) for f in files)
-
-
-migration_files = [f for f in files if re.search(r"migrations?/|\.sql$", f, re.I)]
-mig_added = "\n".join(
-    l for l in dtext.splitlines()
-    if l.startswith("+") and not l.startswith("+++")
-) if migration_files else ""
-out["destructive_migration"] = bool(
-    migration_files
-    and re.search(r"(?i)drop\s+(table|column)|rename\s+(table|column|to)|alter\s+\S+\s+drop", mig_added)
-)
-out["touches_auth"] = bool(
-    any_path(r"auth(?!or)|login|logout|token|session|permission|rbac|\bacl\b|credential")
-    or re.search(r"auth(?!or)|password|jwt|session|credential", added_lines, re.I)
-)
-out["consumer_surface"] = any_path(
-    r"routes?|handlers?|\bapi\b|endpoints?|\bcmd/|\bcli\b|\.proto$|openapi|swagger|controllers?|graphql"
-)
-
-if notes:
-    out["facts_note"] = "; ".join(notes)[:800]
-print(json.dumps(out))

assets/agents/code-reviewer/scripts/group_domains.py

@@ -1,66 +0,0 @@
-#!/usr/bin/env python3
-"""Deterministic domain grouping of changed files for the code-reviewer graph.
-
-Each file lands in the FIRST matching domain (patterns ordered most-specific
-first); unmatched files land in `general`. When the grouping is very wide,
-single-file groups merge into `general` so the fan-out stays sane. The LLM
-refinement node may rebalance this proposal; the cover gate guarantees no
-file is lost either way. Crash-safe: an error emits one catch-all proposal
-rather than tolerant-failing into an empty grouping.
-"""
-
-import json
-import os
-import re
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-DOMAINS = [
-    ("db", r"migrations?/|\.sql$|schema\.(rb|prisma|sql)|models?/"),
-    ("iac", r"\.tf$|helm|charts?/|(^|/)Dockerfile|docker-compose|k8s/|manifests?/"),
-    ("ci-cd", r"\.github/workflows/|\.gitlab-ci|Jenkinsfile|\.circleci/"),
-    ("workers", r"workers?/|jobs?/|consumers?/|cron|tasks?/"),
-    ("api", r"routes?|handlers?|controllers?|endpoints?|\bapi\b|\.proto$|openapi|swagger|graphql|resolvers?"),
-    ("cli", r"\bcmd/|\bcli\b"),
-    ("deps", r"go\.(mod|sum)$|package(-lock)?\.json$|yarn\.lock$|Cargo\.(toml|lock)$|requirements[^/]*\.txt$|pyproject\.toml$|Gemfile|pom\.xml$|composer\.json$"),
-    ("tests", r"(^|/)tests?/|_test\.|\.test\.|spec\."),
-    ("docs", r"\.(md|rst|adoc|txt)$"),
-]
-
-
-def main():
-    state = load_state()
-    files = state.get("changed_files") or []
-
-    groups = {}
-    for f in files:
-        domain = "general"
-        for name, pat in DOMAINS:
-            if re.search(pat, f, re.I):
-                domain = name
-                break
-        groups.setdefault(domain, []).append(f)
-
-    # Wide fan-out: merge single-file groups into general.
-    if len(groups) > 6:
-        for name in list(groups):
-            if name != "general" and len(groups[name]) == 1:
-                groups.setdefault("general", []).extend(groups.pop(name))
-
-    proposed = [{"domain": k, "files": v} for k, v in sorted(groups.items())]
-    print(json.dumps({"proposed_groups": proposed}))
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — never tolerant-fail into an empty grouping
-    try:
-        files = load_state().get("changed_files") or []
-    except Exception:  # noqa: BLE001
-        files = []
-    print(json.dumps({"proposed_groups": [{"domain": "all-changes", "files": files}]}))

assets/agents/code-reviewer/scripts/linters.py

@@ -1,87 +0,0 @@
-#!/usr/bin/env python3
-"""Domain linter pass for the code-reviewer graph.
-
-Runs whichever mechanized checkers exist on PATH against the matching changed
-files: tflint (Terraform), hadolint (Dockerfiles), actionlint (workflow
-files), and `buf breaking` when buf-configured protos changed. Read-only,
-never installs anything, and each tool degrades silently to a skip note.
-Output is routed per-file where possible so the domain leaders can extract
-their slice's lines.
-"""
-
-import json
-import os
-import re
-import shutil
-import subprocess
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-state = load_state()
-proj = state.get("project_dir") or "."
-files = state.get("changed_files") or []
-spec = state.get("resolved_diff_spec") or "worktree"
-notes = []
-
-
-def run(cmd, timeout=60):
-    r = subprocess.run(cmd, capture_output=True, text=True, timeout=timeout, cwd=proj)
-    return (r.stdout + r.stderr).strip()
-
-
-def capped(text, n=40):
-    lines = text.splitlines()
-    return "\n".join(lines[:n]) + (f"\n… ({len(lines) - n} more lines)" if len(lines) > n else "")
-
-
-try:
-    tf = [f for f in files if f.endswith(".tf")]
-    if tf and shutil.which("tflint"):
-        notes.append("[tflint]\n" + capped(run(["tflint", "--no-color"], 120) or "clean"))
-    elif tf:
-        notes.append("[tflint] skipped — not on PATH")
-
-    dockers = [f for f in files if re.search(r"(^|/)Dockerfile", f)]
-    if dockers and shutil.which("hadolint"):
-        notes.append("[hadolint]\n" + capped(run(["hadolint", "--no-color", *dockers[:10]], 60) or "clean"))
-    elif dockers:
-        notes.append("[hadolint] skipped — not on PATH")
-
-    workflows = [f for f in files if ".github/workflows/" in f]
-    if workflows and shutil.which("actionlint"):
-        notes.append("[actionlint]\n" + capped(run(["actionlint", "-no-color", *workflows[:10]], 60) or "clean"))
-    elif workflows:
-        notes.append("[actionlint] skipped — not on PATH")
-
-    protos = [f for f in files if f.endswith(".proto")]
-    if protos and os.path.isfile(os.path.join(proj, "buf.yaml")) and shutil.which("buf"):
-        base = None
-        if "..." in spec:
-            base = spec.split("...")[0]
-        elif ".." in spec:
-            base = spec.split("..")[0]
-        elif spec not in ("staged", "worktree", "HEAD~1"):
-            base = spec
-        else:
-            try:
-                r = subprocess.run(["git", "-C", proj, "rev-parse", "HEAD"],
-                                   capture_output=True, text=True, timeout=15)
-                base = r.stdout.strip() if r.returncode == 0 else None
-            except Exception:  # noqa: BLE001
-                base = None
-        if base:
-            out = run(["buf", "breaking", "--against", f".git#ref={base}"], 120)
-            notes.append("[buf breaking] (wire-compat breaks are 🔴 by default)\n" + capped(out or "clean"))
-        else:
-            notes.append("[buf breaking] skipped — no base ref resolvable")
-    elif protos:
-        notes.append("[buf breaking] skipped — no buf.yaml or buf not on PATH")
-except Exception as e:  # noqa: BLE001
-    notes.append(f"[linters] pass degraded: {e}")
-
-print(json.dumps({"linter_notes": "\n\n".join(notes) if notes else "(no applicable linters)"}))

assets/agents/code-reviewer/scripts/parse_fault.py

@@ -1,58 +0,0 @@
-#!/usr/bin/env python3
-"""Fail-closed marker for a dead parse stage of the code-reviewer graph.
-
-Reached ONLY via parse's `fallback:` route. parse's state_updates wrote an
-"LLM node …failed: <chain>" string into `parse_failure` before routing here;
-this node emits a complete PIPELINE-FAULT `verdict_out` and the graph jumps
-straight to render — a review that could not even parse its request never
-reads as MERGE-READY. render.py renders a PIPELINE-FAULT verdict despite the
-empty changed-file list (its "No changes to review." early return skips
-fault-reason verdicts).
-"""
-
-import json
-import os
-
-MAX_DETAIL_CHARS = 500
-
-ATTENTION_LINE = (
-    "PIPELINE-FAULT: parse failed — the review request could not be parsed; "
-    "the review did not run"
-)
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def fault_verdict(detail):
-    return {
-        "verdict": "NEEDS-HUMAN",
-        "reason": f"PIPELINE-FAULT: parse failed — {detail}",
-        "counts": {},
-        "deferred_count": 0,
-        "dropped_count": 0,
-        "dropped_titles": [],
-        "attention": [ATTENTION_LINE],
-        "findings_final": [],
-    }
-
-
-def main():
-    state = load_state()
-    raw = state.get("parse_failure")
-    detail = raw.strip().replace("\n", " ") if isinstance(raw, str) else ""
-    if not detail.startswith("LLM node"):
-        detail = "the parse stage died without recording a failure detail"
-    if len(detail) > MAX_DETAIL_CHARS:
-        detail = detail[: MAX_DETAIL_CHARS - 1] + "…"
-    print(json.dumps({"verdict_out": fault_verdict(detail)}))
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — the fault marker itself must never crash
-    print(json.dumps({"verdict_out": fault_verdict(f"fault-marker script error: {e}")}))

assets/agents/code-reviewer/scripts/render.py

@@ -1,125 +0,0 @@
-#!/usr/bin/env python3
-"""Deterministic report assembly for the code-reviewer graph.
-
-Builds the standard report format from the structured findings and prose
-sections. Pure templating — no judgment, no re-summarization, no finding
-ever added or removed here.
-"""
-
-import json
-import os
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-# LLM-influenced values rendered after the summary line: a newline could
-# forge a second summary line that review-gauntlet/verdict_gate.py parses.
-def one_line(x):
-    return str(x).replace("\n", " ")
-
-
-def main():
-    state = load_state()
-    v = state.get("verdict_out") or {}
-    findings = v.get("findings_final") or []
-    counts = v.get("counts") or {}
-    changed = state.get("changed_files") or []
-    rigor = one_line(state.get("resolved_rigor") or "production")
-
-    # A fault can leave changed_files empty (a parse fault dies before the
-    # diff is resolved; a verifier fault fires even on an empty diff) — a
-    # fault-degraded verdict must still render as a full report. parse_fault
-    # puts the marker in the reason; verdict.py prepends it to attention.
-    faulted = str(v.get("reason") or "").startswith("PIPELINE-FAULT:") or any(
-        isinstance(a, str) and a.startswith("PIPELINE-FAULT:") for a in v.get("attention") or []
-    )
-    if not changed and not faulted:
-        print(json.dumps({"final_report": "# Code Review Summary\n\nNo changes to review."}))
-        return
-
-    verdict = v.get("verdict", "NEEDS-HUMAN")
-    lines = [
-        "# Code Review Summary",
-        "",
-        # CONTRACT: review-gauntlet/verdict_gate.py anchors on this wording
-        f"**Verdict: {verdict}** — {one_line(v.get('reason', ''))}",
-        "",
-        "## Walkthrough",
-        state.get("walkthrough") or "(no walkthrough provided)",
-        "",
-        "## Changes",
-        "",
-        "| File | Changes | Findings |",
-        "|------|---------|----------|",
-    ]
-
-    desc_by_file = {}
-    for row in state.get("changes_rows") or []:
-        if isinstance(row, dict) and row.get("file"):
-            desc_by_file[row["file"]] = row.get("desc", "")
-    blocking = [f for f in findings if f.get("section") == "blocking"]
-    deferred = [f for f in findings if f.get("section") == "deferred"]
-    for f in changed:
-        per = [x for x in blocking if x.get("file") == f]
-        tally = " ".join(
-            f"{icon} {n}" for icon, n in
-            ((i, sum(1 for x in per if x.get("icon") == i)) for i in ("🔴", "🟡", "🟢", "💡"))
-            if n
-        ) or "—"
-        lines.append(f"| `{f}` | {desc_by_file.get(f, '')} | {tally} |")
-
-    lines += ["", "## Detailed Findings", ""]
-    by_file = {}
-    for x in blocking:
-        by_file.setdefault(x.get("file", "(unattributed)"), []).append(x)
-    if by_file:
-        for f in sorted(by_file):
-            lines += [f"### `{f}`", ""]
-            for x in by_file[f]:
-                lines += [x.get("block", ""), ""]
-    else:
-        lines += ["No blocking findings.", ""]
-
-    lines += ["## Cross-File Concerns", state.get("cross_file") or "None", ""]
-    if (state.get("operational_history") or "").strip():
-        lines += ["## Operational history", state["operational_history"], ""]
-    if (state.get("org_context_section") or "").strip():
-        lines += ["## Org context", state["org_context_section"], ""]
-    if deferred and rigor != "production":
-        lines += ["## Deferred by quality bar", ""]
-        for x in deferred:
-            lines += [x.get("block", ""), ""]
-    attention = v.get("attention") or []
-    if verdict == "NEEDS-HUMAN" and attention:
-        lines += ["## Human attention required", ""]
-        lines += [f"- {a}" for a in attention]
-        lines += [""]
-
-    miss_ids = sorted({
-        m for x in findings for m in
-        __import__("re").findall(r"MISS-\d+", (x.get("title") or "") + (x.get("block") or ""))
-    })
-    dropped = ", ".join(one_line(t) for t in v.get("dropped_titles", [])[:5])
-    lines += [
-        "---",
-        # CONTRACT: review-gauntlet/verdict_gate.py parses this line — keep the format in sync
-        f"*Reviewed {len(changed)} files, found {counts.get('🔴', 0)} critical, "
-        f"{counts.get('🟡', 0)} warnings, {counts.get('🟢', 0)} suggestions, "
-        f"{counts.get('💡', 0)} nitpicks ({v.get('deferred_count', 0)} deferred by quality bar)*",
-        f"*Quality bar: {rigor} — provenance: {one_line(state.get('bar_provenance', '?'))}; "
-        f"surfaces: {one_line(state.get('resolved_surfaces') or 'none')}*",
-        f"*Verdict: {verdict}; verifier: dropped {v.get('dropped_count', 0)} provably-false"
-        + (f" ({dropped})" if v.get("dropped_count") else "")
-        + f"; review-miss patterns applied: {', '.join(miss_ids) if miss_ids else 'none relevant'}*",
-    ]
-    print(json.dumps({"final_report": "\n".join(lines)}))
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001
-    print(json.dumps({"final_report": f"# Code Review Summary\n\n**Verdict: NEEDS-HUMAN** — report rendering error: {e}"}))

assets/agents/code-reviewer/scripts/verdict.py

@@ -1,283 +0,0 @@
-#!/usr/bin/env python3
-"""Deterministic verdict math for the code-reviewer graph.
-
-The model that wrote the findings never grades its own homework:
-- verifier verdicts are applied mechanically (FALSE → drop, tallied;
-  VERIFIED → evidence attached; UNVERIFIABLE → kept, marked);
-- rigor folding is arithmetic over severity + [convention]/[correctness]
-  markers, exactly per the published rules;
-- MERGE-READY/NEEDS-HUMAN is computed from counts + always-human triggers
-  (deterministic signals ∪ the synthesis's ADDITIVE-only flags).
-Fail-closed: any PIPELINE-FAULT recorded upstream (dead domain lane, dead
-verifier, verifier verdicts carrying a PIPELINE-FAULT note or the
-`pipeline-fault` sentinel id, dead synthesis, missing domain reports)
-forces NEEDS-HUMAN — a degraded run can never read MERGE-READY. Faults
-always lead the attention list; the display cap applies only to the
-non-fault entries so a degraded run can never hide a fault.
-The gate never crashes into a silent verdict: any internal error emits
-NEEDS-HUMAN naming the error.
-"""
-
-import json
-import os
-import re
-
-MAX_DETAIL_CHARS = 500
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def sev_icon(severity):
-    for icon in ("🔴", "🟡", "🟢", "💡"):
-        if icon in (severity or ""):
-            return icon
-    return "🟢"
-
-
-def parse_verifier_entries(text):
-    """Extract the raw list of {id, verdict, evidence, note} dicts from
-    finding-verifier output. Order and duplicates are preserved so fault
-    accounting can count every entry (crash-guard entries all carry the
-    same "unknown" id)."""
-    if not isinstance(text, str) or not text.strip():
-        return []
-    start, end = text.find("["), text.rfind("]")
-    if start != -1 and end > start:
-        try:
-            return [
-                v for v in json.loads(text[start : end + 1]) if isinstance(v, dict) and v.get("id")
-            ]
-        except (ValueError, TypeError):
-            pass
-    entries = []
-    for m in re.finditer(r'\{[^{}]*"id"[^{}]*\}', text):
-        try:
-            v = json.loads(m.group(0))
-            if v.get("id"):
-                entries.append(v)
-        except (ValueError, TypeError):
-            continue
-    return entries
-
-
-def parse_verifier(entries):
-    """Index verifier entries by finding id; the last entry per id wins."""
-    return {str(v["id"]): v for v in entries}
-
-
-def main():
-    state = load_state()
-    findings = [f for f in (state.get("findings") or []) if isinstance(f, dict)]
-    rigor = (state.get("resolved_rigor") or "production").lower()
-    verifier_entries = parse_verifier_entries(state.get("verifier_output"))
-    verdicts = parse_verifier(verifier_entries)
-
-    kept, dropped_titles = [], []
-    for f in findings:
-        icon = sev_icon(f.get("severity"))
-        v = verdicts.get(str(f.get("id")))
-        block = f.get("block") or f"#### {f.get('title', '(untitled)')}"
-        if v and icon in ("🔴", "🟡"):
-            if v.get("verdict") == "FALSE":
-                dropped_titles.append(f.get("title", f.get("id", "?")))
-                continue
-            if v.get("verdict") == "VERIFIED" and v.get("evidence"):
-                block += f"\n- **Evidence** (verifier): {v['evidence']}"
-            elif v.get("verdict") == "UNVERIFIABLE":
-                block += "\n- *(unverified: " + (v.get("note") or "could not be established") + ")*"
-        elif icon in ("🔴", "🟡") and not v:
-            block += "\n- *(unverified: no verifier verdict returned for this finding)*"
-        kept.append({**f, "icon": icon, "block": block})
-
-    # --- rigor folding (arithmetic, never rewrites severities) --------------
-    for f in kept:
-        marker = (f.get("marker") or "").lower()
-        icon = f["icon"]
-        section = "blocking"
-        if icon == "🔴":
-            section = "blocking"
-        elif rigor == "prototype" and ((icon == "🟡" and marker == "convention") or icon == "🟢"):
-            section = "deferred"
-        elif rigor == "poc":
-            if icon == "🟡" and marker == "convention":
-                section = "deferred"
-            elif icon in ("🟢", "💡") and marker == "convention":
-                section = "dropped-by-poc"
-        f["section"] = section
-    final = [f for f in kept if f["section"] != "dropped-by-poc"]
-    blocking = [f for f in final if f["section"] == "blocking"]
-    deferred = [f for f in final if f["section"] == "deferred"]
-
-    counts = {i: sum(1 for f in blocking if f["icon"] == i) for i in ("🔴", "🟡", "🟢", "💡")}
-    yellow_correctness = sum(
-        1 for f in blocking if f["icon"] == "🟡" and (f.get("marker") or "").lower() == "correctness"
-    )
-
-    # --- always-human triggers ----------------------------------------------
-    attention = []
-    if state.get("destructive_migration"):
-        attention.append("Destructive/irreversible migration in the diff (DROP/RENAME) — needs a human signature.")
-    if state.get("touches_auth"):
-        attention.append("Authentication/authorization surface changed — needs a human signature.")
-    for flag in state.get("attention_flags") or []:
-        if isinstance(flag, str) and flag.strip():
-            attention.append(flag.strip())
-    placement = (state.get("placement_notes") or "").strip()
-    if placement:
-        attention.append("Placement question (design intent, never auto-resolved): " + placement)
-    # dedup, preserve order
-    seen = set()
-    attention = [a for a in attention if not (a.lower() in seen or seen.add(a.lower()))]
-
-    # --- pipeline-fault accounting (fail closed) -----------------------------
-    # PREFIX-anchored: a report that merely QUOTES a marker mid-text must not
-    # trip it. Any fault forces NEEDS-HUMAN.
-    faults = []
-    changed = state.get("changed_files") or []
-    reports = state.get("domain_reports") or []
-    faulted = sum(
-        1 for r in reports if isinstance(r, str) and r.lstrip().startswith("> ⚠️ PIPELINE-FAULT:")
-    )
-    if faulted:
-        faults.append(
-            f"PIPELINE-FAULT: {faulted} of {len(reports)} domain review lane(s) "
-            "failed after retries — their slices were not reviewed"
-        )
-    verifier_raw = state.get("verifier_output")
-    if isinstance(verifier_raw, str) and verifier_raw.lstrip().startswith("Agent node failed:"):
-        faults.append(
-            "PIPELINE-FAULT: finding verification failed — findings render as unverified"
-        )
-    # finding-verifier completes "successfully" with faults INSIDE the payload:
-    # parse_fault's `pipeline-fault` sentinel entry, or a per-finding
-    # PIPELINE-FAULT note from verify_fault or verdict_gate's crash guard.
-    # Anchored on the sentinel id / note prefix only. Counted over the raw
-    # entries, not the id-indexed dict, so N crash-guard entries sharing the
-    # "unknown" id count as N.
-    fv_faults = [
-        v
-        for v in verifier_entries
-        if v.get("id") == "pipeline-fault"
-        or (isinstance(v.get("note"), str) and v["note"].lstrip().startswith("PIPELINE-FAULT:"))
-    ]
-    # parse_fault's sentinel = the verifier verified NOTHING (hard fault, lane-
-    # degrading). Per-finding verify_fault / crash-guard notes = those findings
-    # simply stand UNVERIFIED (soft: proportionate NEEDS-HUMAN attention — a
-    # ~1 h lane re-run to re-check a few findings is the wrong trade, and the
-    # verify_gate node already retried the verifier locally once).
-    hard_fv = [v for v in fv_faults if v.get("id") == "pipeline-fault"]
-    soft_fv = [v for v in fv_faults if v.get("id") != "pipeline-fault"]
-
-    def _fv_detail(entries):
-        first = entries[0].get("note")
-        detail = first.strip().replace("\n", " ") if isinstance(first, str) else ""
-        if len(detail) > MAX_DETAIL_CHARS:
-            detail = detail[: MAX_DETAIL_CHARS - 1] + "…"
-        return detail
-
-    soft_notes = []
-    if hard_fv:
-        faults.append(
-            "PIPELINE-FAULT: finding verification degraded — the verifier verified "
-            f"nothing ({_fv_detail(hard_fv)})"
-        )
-    if soft_fv:
-        soft_notes.append(
-            f"Verifier: {len(soft_fv)} finding(s) could not be verified (verifier "
-            f"branch fault: {_fv_detail(soft_fv)}) — they stand above UNVERIFIED; "
-            "verify them manually"
-        )
-    # Files beyond facts.py's 300-file cap were never grouped or reviewed —
-    # disclose the gap and force NEEDS-HUMAN with wording that does NOT match
-    # the gauntlet's degraded-run anchors (a lane re-run cannot fix a cap).
-    coverage_notes = []
-    try:
-        total_files = int(state.get("file_count") or 0)
-    except (TypeError, ValueError):
-        total_files = 0
-    if total_files > len(changed):
-        coverage_notes.append(
-            f"Coverage gap: {total_files - len(changed)} of {total_files} changed files "
-            "were NOT reviewed (file-list cap) — review them manually or split the PR"
-        )
-    # Keyed off synth_failure + a non-empty diff, NEVER off findings == [] —
-    # a clean review legitimately has zero findings and stays MERGE-READY.
-    synth_failure = state.get("synth_failure")
-    if isinstance(synth_failure, str) and synth_failure.startswith("LLM node") and changed:
-        detail = synth_failure.strip().replace("\n", " ")
-        if len(detail) > MAX_DETAIL_CHARS:
-            detail = detail[: MAX_DETAIL_CHARS - 1] + "…"
-        faults.append(f"PIPELINE-FAULT: synthesis failed — findings unavailable; {detail}")
-    if changed and not reports:
-        faults.append(
-            "PIPELINE-FAULT: the diff is non-empty but no domain reports were produced — "
-            "the review did not actually run; do not trust this verdict."
-        )
-    # faults go FIRST and uncapped so the display cap can never hide one;
-    # the trigger reason keys off the human-facing triggers alone
-    has_triggers = bool(attention)
-    attention = faults + soft_notes + coverage_notes + attention[:5]
-
-    reasons = []
-    if counts["🔴"]:
-        reasons.append(f"{counts['🔴']} 🔴 CRITICAL finding(s)")
-    if yellow_correctness:
-        reasons.append(f"{yellow_correctness} 🟡 [correctness] finding(s) outside the deferred section")
-    if faults:
-        # CONTRACT: review-gauntlet/verdict_gate.py anchors on this wording
-        reasons.append("pipeline fault(s) recorded — degraded run")
-    if soft_notes:
-        # Deliberately does NOT match the gauntlet's degraded-run anchors:
-        # unverified findings are a human-attention item, not a re-runnable
-        # lane fault.
-        reasons.append(f"{len(soft_fv)} finding(s) unverified (verifier branch fault)")
-    if coverage_notes:
-        reasons.append(f"{total_files - len(changed)} changed file(s) not reviewed (file cap)")
-    if has_triggers:
-        reasons.append("always-human trigger(s) fired")
-    verdict = "NEEDS-HUMAN" if reasons else "MERGE-READY"
-    reason_line = "; ".join(reasons) if reasons else "no blocking findings and no always-human triggers"
-
-    print(
-        json.dumps(
-            {
-                "verdict_out": {
-                    "verdict": verdict,
-                    "reason": reason_line,
-                    "counts": counts,
-                    "deferred_count": len(deferred),
-                    "dropped_count": len(dropped_titles),
-                    "dropped_titles": dropped_titles,
-                    "attention": attention,
-                    "findings_final": final,
-                }
-            }
-        )
-    )
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — never crash into a silent verdict
-    print(
-        json.dumps(
-            {
-                "verdict_out": {
-                    "verdict": "NEEDS-HUMAN",
-                    # PIPELINE-FAULT prefix is load-bearing: render.py's
-                    # empty-diff stub bypass anchors on it — without it a
-                    # crashed gate on an empty diff collapses into the
-                    # "No changes to review." stub.
-                    "reason": f"PIPELINE-FAULT: verdict computation error: {e} — human review required",
-                    "counts": {}, "deferred_count": 0, "dropped_count": 0,
-                    "dropped_titles": [], "attention": [f"PIPELINE-FAULT: verdict script error: {e}"],
-                    "findings_final": [],
-                }
-            }
-        )
-    )

assets/agents/code-reviewer/scripts/verify_gate.py

@@ -1,52 +0,0 @@
-#!/usr/bin/env python3
-"""Local verifier-fault retry gate for the code-reviewer graph.
-
-finding-verifier converts its own branch faults into DATA (UNVERIFIABLE
-verdicts with a PIPELINE-FAULT: note, or parse_fault's pipeline-fault
-sentinel), so the verify agent node completes "successfully" and its
-max_attempts never fires. Without this gate the fault escalates all the
-way to the gauntlet, which re-runs the ENTIRE code-review lane (~1 h) to
-recover a ~4-minute verifier — the wrong trade. This gate re-runs just
-the verifier ONCE; if faults persist, verdict.py downgrades them to a
-proportionate NEEDS-HUMAN (findings stand, unverified).
-
-Anchored detection only: the JSON-encoded note prefix and the sentinel id
-— a finding merely QUOTING the marker mid-text does not trip it. Always
-exits 0 with valid JSON; a crash falls forward on the declared edge.
-"""
-import json
-import os
-import sys
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-try:
-    state = load_state()
-    raw = state.get("verifier_output")
-    text = raw if isinstance(raw, str) else (json.dumps(raw) if raw is not None else "")
-    faulted = (
-        text.lstrip().startswith("Agent node failed:")
-        or '"note": "PIPELINE-FAULT:' in text
-        or "'note': 'PIPELINE-FAULT:" in text
-        or '"id": "pipeline-fault"' in text
-    )
-    try:
-        retries = int(state.get("verify_retries") or 0)
-    except (TypeError, ValueError):
-        retries = 0
-    if faulted and retries < 1:
-        sys.stderr.write(
-            "WARN: verifier output carries pipeline-fault markers — re-running "
-            "finding-verifier locally (attempt 2/2) before computing the verdict.\n"
-        )
-        print(json.dumps({"_next": "verify", "verify_retries": retries + 1}))
-    else:
-        print(json.dumps({"verify_retries": retries}))
-except Exception as e:  # never block the verdict
-    print(json.dumps({"verify_gate_error": f"verify_gate crashed: {e}"}))

assets/agents/coder/graph.yaml

@@ -15,9 +15,6 @@ skills_enabled: true
 enabled_skills:
   - ai-slop-remover
   - code-review
-  - comment-discipline
-  - diagnosing-bugs
-  - logging-discipline
   - git-master
   - frontend-ui-ux
   - verification-gates
@@ -34,7 +31,7 @@ settings:
   max_loop_iterations: 20
   log_state_snapshots: true
   validate_before_run: true
-  timeout: 14400
+  timeout: 1800
 
 initial_state:
   project_dir: ''
@@ -93,7 +90,6 @@ nodes:
       Project directory: {{project_dir}}
     prompt: '{{initial_prompt}}'
     tools: []
-    timeout: 300
     output_schema:
       type: object
       properties:
@@ -170,9 +166,6 @@ nodes:
     enabled_skills:
       - ai-slop-remover
       - code-review
-      - comment-discipline
-      - diagnosing-bugs
-      - logging-discipline
       - git-master
       - frontend-ui-ux
       - verification-gates
@@ -183,10 +176,9 @@ nodes:
       ## Skills
 
       Use `skill__list` to see what's available, then `skill__load` the ones
-      that fit the work: `ai-slop-remover` and `comment-discipline` always,
+      that fit the work: `ai-slop-remover` always, `frontend-ui-ux` when
-      `frontend-ui-ux` when touching UI, `git-master` when touching history,
+      touching UI, `git-master` when touching history, `verification-gates`
-      `verification-gates` to remember what evidence is required. Unload when
+      to remember what evidence is required. Unload when a phase ends.
-      a phase ends.
 
       ## Writing code
 
@@ -219,16 +211,7 @@ nodes:
       Before writing ANY file:
       1. Find a similar existing file (grep, then read).
       2. Match its style: imports, naming, structure, error handling.
-      3. While reading it, note the repo's comment register per
+      3. Follow the same patterns exactly. Do not invent new ones.
-         `comment-discipline` (self-documenting / api-documented /
-         comment-heavy) and write comments to match. When the signal is
-         weak, write NO comment.
-      4. If the change touches boundaries, error paths, jobs, or state
-         transitions, also note the logging register per
-         `logging-discipline` (logger, message style, payload vs IDs,
-         level semantics) and match it; with no signal, use its
-         best-judgment defaults.
-      5. Follow the same patterns exactly. Do not invent new ones.
 
       ## Fix loop
 
@@ -236,11 +219,6 @@ nodes:
       the previous attempt failed verification. Read the error, identify
       the minimal fix, apply it. Do not refactor while fixing.
 
-      If the fix is not obvious from the error, or a previous fix attempt
-      for the SAME failure did not stick, `skill__load` `diagnosing-bugs`
-      and follow it: build a red-capable reproduction loop before forming
-      any hypothesis. Do not spend a second attempt on a blind retry.
-
       ## Rules
 
       1. Match existing patterns - read examples first.
@@ -276,7 +254,6 @@ nodes:
       - fs_patch
       - execute_command
     max_iterations: 100
-    timeout: 1800
     state_updates:
       last_node_output: '{{output}}'
     fallback: end_failure
@@ -350,7 +327,6 @@ nodes:
       - fs_ls
       - execute_command
     max_iterations: 15
-    timeout: 600
     output_schema:
       type: object
       properties:
@@ -408,4 +384,4 @@ nodes:
       {{build_output}}
 
       Last tests output:
-      {{tests_output}}
+      {{tests_output}}

assets/agents/deep-research/README.md

@@ -22,13 +22,11 @@ agent, this is the file to read alongside the
 
 ## Workflow
 
-23 nodes. Solid arrows are static `next` / `routes` edges declared in
+17 nodes. Solid arrows are static `next` / `routes` edges declared in
 `graph.yaml`; script nodes can also route dynamically via `_next` (shown as
 labeled branches out of the diamond). Dotted arrows show `map` fan-out — the
 `research_each_question` node spawns one `research_one_question` branch per
-sub-question and joins them before continuing — and `fallback` edges
+sub-question and joins them before continuing.
-(labeled "fallback"), taken when a node fails outright (see *Fault paths*
-below).
 
 ```mermaid
 flowchart TD
@@ -40,27 +38,18 @@ flowchart TD
     bootstrap_research --> plan
     bootstrap_research --> knowledge_lookup
     plan["plan<br/>llm + output_schema"] --> research_each_question
-    plan -. "fallback" .-> plan_fault{"plan_fault<br/>script"}
-    plan_fault --> end_fault
     knowledge_lookup[("knowledge_lookup<br/>rag")] --> research_each_question
     research_each_question[\research_each_question<br/>map/]
     research_each_question -. "spawns × N" .-> research_one_question["research_one_question<br/>llm + web tools"]
-    research_one_question -. "fallback" .-> question_fault{"question_fault<br/>script"}
     research_each_question --> combine_findings
     combine_findings{"combine_findings<br/>script"} --> vet_sources
     vet_sources["vet_sources<br/>llm + classify_source"] --> critique
-    vet_sources -. "fallback" .-> vet_fault{"vet_fault<br/>script"}
-    vet_fault --> critique
     critique["critique<br/>llm"] --> reflexion_gate
-    critique -. "fallback" .-> critique_fault{"critique_fault<br/>script"}
-    critique_fault --> reflexion_gate
     reflexion_gate{"reflexion_gate<br/>script"}
     reflexion_gate -->|"PASS"| synthesize
     reflexion_gate -->|"REVISE (budget left)"| research_each_question
     reflexion_gate -->|"REVISE (budget spent)"| synthesize
     synthesize[["synthesize<br/>agent → report-writer"]] --> verify_sources
-    synthesize -. "fallback" .-> synth_fault{"synth_fault<br/>script"}
-    synth_fault --> end_fault
     verify_sources{"verify_sources<br/>script"} --> approve
     approve{{"approve<br/>approval"}}
     approve -->|"accept"| end_accepted
@@ -70,14 +59,13 @@ flowchart TD
 
     end_accepted(["end_accepted<br/>report"])
     end_rejected(["end_rejected"])
-    end_fault(["end_fault<br/>DEEP_RESEARCH FAILED"])
 ```
 
 ### Node-type breakdown
 
 | Type                        | Nodes                                                                                                                 |
 |-----------------------------|-----------------------------------------------------------------------------------------------------------------------|
-| `script` (Python)           | `parse_request`, `bootstrap_research`, `combine_findings`, `reflexion_gate`, `verify_sources`, `incorporate_feedback`, plus the fault markers `plan_fault`, `question_fault`, `vet_fault`, `critique_fault`, `synth_fault` |
+| `script` (Python)           | `parse_request`, `bootstrap_research`, `combine_findings`, `reflexion_gate`, `verify_sources`, `incorporate_feedback` |
 | `llm` (tools: `[]`)         | `plan`, `critique`                                                                                                    |
 | `llm` (with tool whitelist) | `research_one_question`, `vet_sources`                                                                                |
 | `rag`                       | `knowledge_lookup` — local corpus retrieval                                                                           |
@@ -85,7 +73,7 @@ flowchart TD
 | `agent`                     | `synthesize` — spawns the `report-writer` sub-agent                                                                   |
 | `input`                     | `ask_topic`                                                                                                           |
 | `approval`                  | `approve`                                                                                                             |
-| `end`                       | `end_accepted`, `end_rejected`, `end_fault`                                                                           |
+| `end`                       | `end_accepted`, `end_rejected`                                                                                        |
 
 ## Parallel execution
 
@@ -229,46 +217,6 @@ folds that text into `research_feedback` and loops back to
 `settings.max_loop_iterations` (40) is the engine's infinite-loop
 backstop: it caps the total visits to any single node.
 
-## Fault paths
-
-Every stage that can die outright has a `fallback:` edge to a small
-fault-marker script — the dashed edges in the diagram. A fallback fires
-after a node's retries are exhausted (`research_one_question` and
-`synthesize` each get two attempts via `max_attempts: 2`); the engine
-writes its failure text into the node's state key before routing, and
-the marker normalizes that text into a `PIPELINE-FAULT: ...` entry in
-`pipeline_faults`. The five routes:
-
-- `plan -> plan_fault -> end_fault` — fail-closed: no plan means
-  nothing to research.
-- `research_one_question -> question_fault` — branch-local, inside the
-  map branch: one dead research lane becomes a fault finding instead of
-  sinking the whole map.
-- `vet_sources -> vet_fault -> critique` — degrade-visibly: vetting is
-  a quality lane, not the product; `source_assessment` becomes a
-  neutral "unvetted" note.
-- `critique -> critique_fault -> reflexion_gate` — degrade-visibly: the
-  rewritten critique deliberately has no `VERDICT:` line, so the gate's
-  malformed-critique PASS default proceeds to synthesis.
-- `synthesize -> synth_fault -> end_fault` — fail-closed: no report
-  means no product.
-
-On the fail-closed routes, `end_fault` renders the
-`DEEP_RESEARCH FAILED — PIPELINE-FAULT: ...` sentinel. On the
-degrade-visibly routes, `verify_sources` folds the accumulated faults
-into a `## Pipeline notes` section shown at the approval step and
-appended to the accepted report (`{{report}}{{pipeline_notes}}`;
-empty when there were no faults). Degraded output is never a silent
-pass — every fault is visible to the reviewer or the caller — and some
-end node always renders its sentinel, so the graph degrades instead of
-dying.
-
-All 11 scripts also carry a top-level crash guard: a script that
-throws records a fault and fails forward where the flow allows it (a
-crashed `reflexion_gate` proceeds to `synthesize`; a crashed
-`verify_sources` reports that sources were NOT checked) instead of
-killing the run.
-
 ## Running
 
 ```sh
@@ -293,9 +241,6 @@ coyote -a deep-research                # no prompt -> triggers ask_topic
 - `verify_sources` probes every cited URL / DOI with an HTTP HEAD
   request and reports which are unreachable, so the human reviewer
   sees broken citations before approving.
-- Fault paths degrade visibly, never silently: a `PIPELINE-FAULT`
-  can only ever surface as a failure sentinel or a `## Pipeline
-  notes` section, never as a clean report.
 
 ## Customizing
 
@@ -325,7 +270,7 @@ coyote -a deep-research                # no prompt -> triggers ask_topic
 
 ```
 assets/agents/deep-research/
-  graph.yaml                    - agent config + 23-node workflow
+  graph.yaml                    - agent config + 17-node workflow
   tools.sh                      - classify_source custom tool
   README.md                     - this file
   knowledge/
@@ -334,15 +279,9 @@ assets/agents/deep-research/
   scripts/
     parse_request.py            - _next: bootstrap_research, or ask_topic if no topic
     bootstrap_research.py       - fan-out source: next [plan, knowledge_lookup]
-    plan_fault.py               - fail-closed fault marker: dead plan -> end_fault
-    question_fault.py           - branch-local fault marker for a dead research lane
     combine_findings.py         - joins map output (question_findings) into findings
-    vet_fault.py                - degrade-visibly fault marker: unvetted sources
-    critique_fault.py           - degrade-visibly fault marker: skipped critique
     reflexion_gate.py           - _next: research_each_question (revise) or synthesize
-    synth_fault.py              - fail-closed fault marker: no report -> end_fault
+    verify_sources.py           - HTTP HEAD on cited URLs / DOIs
-    verify_sources.py           - HTTP HEAD on cited URLs / DOIs; folds pipeline_faults
-                                  into the report's "## Pipeline notes" section
     incorporate_feedback.py     - _next: research_each_question, with user feedback
 ```
 

assets/agents/deep-research/graph.yaml

@@ -13,7 +13,7 @@ description: |
   node type (script, llm, rag, map, agent, input, approval, end) and
   both static fan-out and dynamic map fan-out.
 
-version: '1.0'
+version: "1.0"
 
 global_tools:
   - web_search_coyote.sh
@@ -24,8 +24,8 @@ mcp_servers:
   - ddg-search
 
 conversation_starters:
-  - 'How does HTTP/3 differ from HTTP/2?'
+  - "How does HTTP/3 differ from HTTP/2?"
-  - 'Summarize recent advances in solid-state battery chemistry'
+  - "Summarize recent advances in solid-state battery chemistry"
 
 settings:
   max_loop_iterations: 40
@@ -34,22 +34,15 @@ settings:
   max_concurrency: 4
 
 initial_state:
-  research_feedback: ''
+  research_feedback: ""
   research_attempts: 0
-  local_context: ''
+  local_context: ""
-  local_sources: ''
+  local_sources: ""
-  # Fault-path defaults. `questions: []` also keeps the
-  # knowledge_lookup lane alive for one super-step when `plan` dies inside the
-  # static fan-out: research_each_question maps over zero items while the
-  # plan_fault → end_fault route renders the failure sentinel.
-  pipeline_faults: []
-  pipeline_notes: ''
-  fault_text: ''
-  questions: []
 
 start: parse_request
 
 nodes:
+
   parse_request:
     id: parse_request
     type: script
@@ -59,10 +52,10 @@ nodes:
   ask_topic:
     id: ask_topic
     type: input
-    question: 'What would you like me to research?'
+    question: "What would you like me to research?"
-    validation: 'len(input) > 0'
+    validation: "len(input) > 0"
     state_updates:
-      topic: '{{input}}'
+      topic: "{{input}}"
     next: bootstrap_research
 
   bootstrap_research:
@@ -84,7 +77,7 @@ nodes:
       are precise, self-contained queries (each one is sent on its own
       to a separate research worker, so they must be answerable
       without each other's context).
-    prompt: 'Research topic: {{topic}}'
+    prompt: "Research topic: {{topic}}"
     tools: []
     output_schema:
       type: object
@@ -99,44 +92,29 @@ nodes:
           maxItems: 6
           description: 3-5 specific, self-contained sub-questions.
       required: [research_plan, questions]
-    # On success plan_failure holds the node's structured JSON output; on
-    # failure the engine writes "LLM node ...failed: <chain>" into it BEFORE
-    # routing to the fallback (schema properties are only merged on success).
-    state_updates:
-      plan_failure: '{{output}}'
-    fallback: plan_fault
     next: research_each_question
 
-  plan_fault:
-    id: plan_fault
-    type: script
-    description: Fail-closed marker for a dead planning stage (reached only via plan's fallback) — normalizes the failure text captured in plan_failure into a PIPELINE-FAULT and continues to end_fault; no plan means nothing to research, so the DEEP_RESEARCH FAILED sentinel always renders. The sibling knowledge_lookup lane survives one more super-step by mapping over the empty initial_state `questions` list.
-    script: scripts/plan_fault.py
-    fallback: end_fault
-    next: end_fault
-
   knowledge_lookup:
     id: knowledge_lookup
     type: rag
     documents:
       - ./knowledge/
-    query: '{{topic}}'
+    query: "{{topic}}"
     top_k: 6
     chunk_size: 1000
     chunk_overlap: 100
     state_updates:
-      local_context: '{{output.context}}'
+      local_context: "{{output.context}}"
-      local_sources: '{{output.sources}}'
+      local_sources: "{{output.sources}}"
     next: research_each_question
 
   research_each_question:
     id: research_each_question
     type: map
-    over: '{{questions}}'
+    over: "{{questions}}"
     as: question
     branch: research_one_question
     collect_into: question_findings
-    output_key: finding
     max_concurrency: 3
     next: combine_findings
 
@@ -173,18 +151,7 @@ nodes:
       - mcp:ddg-search
     max_iterations: 10
     max_attempts: 2
-    state_updates:
+    temperature: 0.1
-      finding: '{{output}}'
-    # On failure the engine writes "LLM node ...failed: <chain>" into `finding`
-    # via the state_updates above BEFORE routing to the fallback. The marker
-    # is branch-local: a map branch's fallback must stay inside the branch.
-    fallback: question_fault
-
-  question_fault:
-    id: question_fault
-    type: script
-    description: Fail-closed marker for a dead research lane (reached only via research_one_question's fallback route inside the map branch). Normalizes the engine's failure text in `finding` into a PIPELINE-FAULT finding the map collects — one dead lane never sinks the whole map. combine_findings later lifts PIPELINE-FAULT findings into pipeline_faults for the report's Pipeline notes.
-    script: scripts/question_fault.py
 
   combine_findings:
     id: combine_findings
@@ -210,16 +177,7 @@ nodes:
       - classify_source
     max_iterations: 15
     state_updates:
-      source_assessment: '{{output}}'
+      source_assessment: "{{output}}"
-    fallback: vet_fault
-    next: critique
-
-  vet_fault:
-    id: vet_fault
-    type: script
-    description: Degrade-visibly marker for a dead vetting stage (reached only via vet_sources' fallback) — vetting is a quality lane, not the product. Records a PIPELINE-FAULT, rewrites source_assessment to a neutral "unvetted" note, and continues to critique, the stage vet_sources' own next pointed to.
-    script: scripts/vet_fault.py
-    fallback: critique
     next: critique
 
   critique:
@@ -259,16 +217,7 @@ nodes:
       {{source_assessment}}
     tools: []
     state_updates:
-      critique: '{{output}}'
+      critique: "{{output}}"
-    fallback: critique_fault
-    next: reflexion_gate
-
-  critique_fault:
-    id: critique_fault
-    type: script
-    description: Degrade-visibly marker for a dead critique stage (reached only via critique's fallback) — critique is a quality lane, not the product. Records a PIPELINE-FAULT and rewrites `critique` to a neutral note with deliberately NO "VERDICT:" line, so reflexion_gate's malformed-critique PASS default proceeds to synthesis; then continues to reflexion_gate, the stage critique's own next pointed to.
-    script: scripts/critique_fault.py
-    fallback: reflexion_gate
     next: reflexion_gate
 
   reflexion_gate:
@@ -292,22 +241,10 @@ nodes:
 
       Produce the final report following your instructions.
     timeout: 300
-    max_attempts: 2
     state_updates:
-      report: '{{output}}'
+      report: "{{output}}"
-    # On failure the engine writes "Agent node failed: <chain>" into `report`
-    # via the state_updates above BEFORE routing to the fallback.
-    fallback: synth_fault
     next: verify_sources
 
-  synth_fault:
-    id: synth_fault
-    type: script
-    description: Fail-closed marker for a dead synthesis stage (reached only via synthesize's fallback) — no report means no product. Normalizes the "Agent node failed:" text captured in `report` into a PIPELINE-FAULT and continues to end_fault, which renders the DEEP_RESEARCH FAILED sentinel.
-    script: scripts/synth_fault.py
-    fallback: end_fault
-    next: end_fault
-
   verify_sources:
     id: verify_sources
     type: script
@@ -323,20 +260,20 @@ nodes:
       {{report}}
 
       ----
-      {{source_check}}{{pipeline_notes}}
+      {{source_check}}
       ----
 
       Accept this report? Pick "accept" or "reject", or type specific
       feedback to send the research back for another pass.
     options:
-      - 'accept'
+      - "accept"
-      - 'reject'
+      - "reject"
     routes:
-      'accept': end_accepted
+      "accept": end_accepted
-      'reject': end_rejected
+      "reject": end_rejected
     on_other: incorporate_feedback
     state_updates:
-      decision: '{{choice}}'
+      decision: "{{choice}}"
 
   incorporate_feedback:
     id: incorporate_feedback
@@ -346,14 +283,9 @@ nodes:
   end_accepted:
     id: end_accepted
     type: end
-    output: '{{report}}{{pipeline_notes}}'
+    output: "{{report}}"
 
   end_rejected:
     id: end_rejected
     type: end
     output: "Research on '{{topic}}' was rejected and discarded."
-
-  end_fault:
-    id: end_fault
-    type: end
-    output: 'DEEP_RESEARCH FAILED — PIPELINE-FAULT: {{fault_text}}'

assets/agents/deep-research/scripts/bootstrap_research.py

@@ -6,12 +6,6 @@ list on this node fans out into two parallel branches (the LLM planner and
 the RAG knowledge lookup) as a single super-step. The validator requires
 declared parallel-branch script outputs, so we emit an empty JSON object
 explicitly here.
-
-Fail-safe: the node reads no state and computes nothing, so its
-happy-path output IS the sane degraded output — the guard emits the same
-empty object on any crash. No PIPELINE-FAULT is recorded: appending one
-would require reading state (the very thing that crashed) or clobbering
-faults recorded upstream by parse_request, and a crash here loses nothing.
 """
 import json
 
@@ -20,7 +14,5 @@ def main():
     print(json.dumps({}))
 
 
-try:
+if __name__ == "__main__":
     main()
-except Exception:  # noqa: BLE001 — the fan-out source must never crash the graph
-    print(json.dumps({}))

assets/agents/deep-research/scripts/combine_findings.py

@@ -6,18 +6,6 @@ one entry per sub-question, in input order). Downstream nodes
 (`vet_sources`, `critique`, `synthesize`) read `{{findings}}` as a
 single block, so this script renders the array as a Markdown document
 with one section per question.
-
-Fault visibility: a research lane that died lands here as a finding
-starting with "PIPELINE-FAULT:" (written by question_fault inside the map
-branch, where `pipeline_faults` itself is out of reach — map branches only
-surface their collected output_key). This script lifts such findings into
-`pipeline_faults` (deduplicated, since a reflexion or feedback loop can
-re-run the map) so dead lanes surface in the report's Pipeline notes.
-
-Fail-safe: on a crash (e.g. malformed GRAPH_STATE), `findings`
-becomes the fault text itself and a PIPELINE-FAULT entry is recorded —
-the pipeline proceeds visibly degraded, and the human approval gate is
-the backstop. Existing faults are preserved best-effort.
 """
 import json
 import os
@@ -31,40 +19,21 @@ def load_state():
     return json.loads(os.environ.get("GRAPH_STATE", "{}"))
 
 
-def safe_faults():
-    try:
-        state = load_state()
-        return [f for f in (state.get("pipeline_faults") or []) if isinstance(f, str)]
-    except Exception:  # noqa: BLE001 — best-effort preservation only
-        return []
-
-
 def main():
     state = load_state()
     questions = state.get("questions") or []
     per_question = state.get("question_findings") or []
-    faults = [f for f in (state.get("pipeline_faults") or []) if isinstance(f, str)]
 
     sections = []
     for idx, q in enumerate(questions):
         body = per_question[idx] if idx < len(per_question) else ""
         if isinstance(body, dict) or isinstance(body, list):
             body = json.dumps(body, indent=2)
-        if isinstance(body, str) and body.startswith("PIPELINE-FAULT:") and body not in faults:
-            faults.append(body)
         sections.append(f"## {q}\n\n{body}")
 
     findings = "\n\n".join(sections) if sections else "No findings gathered."
-    print(json.dumps({"findings": findings, "pipeline_faults": faults}))
+    print(json.dumps({"findings": findings}))
 
 
-try:
+if __name__ == "__main__":
     main()
-except Exception as e:  # noqa: BLE001 — a crashed join must degrade, not die
-    faults = safe_faults()
-    fault = (
-        f"PIPELINE-FAULT: combining findings crashed — {e}; per-question "
-        "findings may exist in state but could not be joined"
-    )
-    faults.append(fault)
-    print(json.dumps({"findings": fault, "pipeline_faults": faults}))

assets/agents/deep-research/scripts/critique_fault.py

@@ -1,71 +0,0 @@
-#!/usr/bin/env python3
-"""Degrade-visibly marker for a dead critique stage of deep-research.
-
-Reached ONLY via critique's `fallback:` route. Grounded in engine behavior:
-on llm-node failure the engine writes "LLM node …failed: <chain>" into
-`critique` via the node's state_updates BEFORE routing to the fallback.
-Critique is a quality lane, not the product, so this path degrades instead
-of failing closed: it records a PIPELINE-FAULT (surfaced later in the
-report's Pipeline notes) and rewrites `critique` to a neutral note, then
-continues to `reflexion_gate` — the stage critique's own `next` pointed to.
-
-The rewritten note deliberately contains NO "VERDICT:" line:
-reflexion_gate's parse_verdict defaults to PASS when no verdict line is
-found (its documented malformed-critique behavior), so a dead critique
-proceeds to synthesis instead of burning the revision budget on a fault.
-"""
-
-import json
-import os
-
-MAX_DETAIL_CHARS = 500
-
-CRITIQUE_NOTE = (
-    "Critique unavailable — the critique stage failed (pipeline fault); "
-    "proceeding to synthesis without an automated review pass."
-)
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def safe_faults():
-    try:
-        state = load_state()
-        return [f for f in (state.get("pipeline_faults") or []) if isinstance(f, str)]
-    except Exception:  # noqa: BLE001 — best-effort preservation only
-        return []
-
-
-def main():
-    state = load_state()
-    faults = [f for f in (state.get("pipeline_faults") or []) if isinstance(f, str)]
-    raw = state.get("critique")
-    detail = raw.strip().replace("\n", " ") if isinstance(raw, str) else ""
-    if not detail.startswith("LLM node"):
-        detail = "the critique stage died without recording a failure detail"
-    if len(detail) > MAX_DETAIL_CHARS:
-        detail = detail[: MAX_DETAIL_CHARS - 1] + "…"
-    fault = f"PIPELINE-FAULT: critique failed — {detail}"
-    if fault not in faults:
-        faults.append(fault)
-    print(json.dumps({"pipeline_faults": faults, "critique": CRITIQUE_NOTE}))
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — the fault marker itself must never crash
-    faults = safe_faults()
-    faults.append(f"PIPELINE-FAULT: critique failed — fault-marker script error: {e}")
-    print(
-        json.dumps(
-            {
-                "pipeline_faults": faults,
-                "critique": CRITIQUE_NOTE,
-            }
-        )
-    )

assets/agents/deep-research/scripts/incorporate_feedback.py

@@ -10,13 +10,6 @@ reflexion counter is reset so the user-driven pass gets a fresh revision
 budget.
 
 Routing (`_next`): always research_each_question.
-
-Fail-safe: a crash here means the user's feedback text cannot be
-recovered, but their INTENT — another research pass — is unambiguous
-(they chose neither accept nor reject). The degraded route therefore
-still loops to `research_each_question`, with a generic feedback note
-naming the loss and a PIPELINE-FAULT entry (best-effort preserving
-existing faults) that surfaces in the next approval's Pipeline notes.
 """
 import json
 import os
@@ -30,14 +23,6 @@ def load_state():
     return json.loads(os.environ.get("GRAPH_STATE", "{}"))
 
 
-def safe_faults():
-    try:
-        state = load_state()
-        return [f for f in (state.get("pipeline_faults") or []) if isinstance(f, str)]
-    except Exception:  # noqa: BLE001 — best-effort preservation only
-        return []
-
-
 def main():
     state = load_state()
     feedback = (state.get("decision") or "").strip()
@@ -52,26 +37,5 @@ def main():
     print(json.dumps(output))
 
 
-try:
+if __name__ == "__main__":
     main()
-except Exception as e:  # noqa: BLE001 — a crashed feedback fold must degrade, not die
-    faults = safe_faults()
-    faults.append(
-        f"PIPELINE-FAULT: feedback incorporation crashed — {e}; the reviewer's "
-        "feedback text could not be recovered"
-    )
-    print(
-        json.dumps(
-            {
-                "_next": "research_each_question",
-                "research_attempts": 0,
-                "research_feedback": (
-                    "The user reviewed the report and asked for changes, but "
-                    "the feedback text could not be recovered (pipeline "
-                    "fault). Re-run the research pass with extra care and "
-                    "note this loss."
-                ),
-                "pipeline_faults": faults,
-            }
-        )
-    )

assets/agents/deep-research/scripts/parse_request.py

@@ -9,13 +9,6 @@ supply one interactively.
 Routing (`_next`):
   - prompt present -> (no _next; static next: plan)
   - prompt empty   -> ask_topic
-
-Fail-safe: a crash here (e.g. malformed GRAPH_STATE) means the
-caller's prompt cannot be read at all, so proceeding silently is
-meaningless — the degraded route is `ask_topic`, which asks the user for
-the topic directly, plus a PIPELINE-FAULT entry so the loss is visible in
-the final report's Pipeline notes. Clobbering `pipeline_faults` is safe
-here: this is the start node, so the list can only hold its initial [].
 """
 import json
 import os
@@ -38,17 +31,5 @@ def main():
         print(json.dumps({"_next": "ask_topic"}))
 
 
-try:
+if __name__ == "__main__":
     main()
-except Exception as e:  # noqa: BLE001 — a crashed entry router must degrade, not die
-    print(
-        json.dumps(
-            {
-                "_next": "ask_topic",
-                "pipeline_faults": [
-                    f"PIPELINE-FAULT: request parsing crashed — {e}; asked the "
-                    "user for the research topic instead"
-                ],
-            }
-        )
-    )

assets/agents/deep-research/scripts/plan_fault.py

@@ -1,58 +0,0 @@
-#!/usr/bin/env python3
-"""Fail-closed marker for a dead planning stage of the deep-research graph.
-
-Reached ONLY via plan's `fallback:` route. Grounded in engine behavior: on
-llm-node failure the engine writes "LLM node …failed: <chain>" into
-`plan_failure` via the node's state_updates BEFORE routing to the fallback
-(on success the same key holds the node's structured JSON output, which
-never starts with the "LLM node" prefix). No plan means no sub-questions —
-there is nothing to research — so this path is fail-closed: record the
-PIPELINE-FAULT and continue to `end_fault`, which renders the
-DEEP_RESEARCH FAILED sentinel.
-
-The planner runs inside the static fan-out [plan, knowledge_lookup]. While
-this marker routes to end_fault, the sibling branch proceeds one more
-super-step into `research_each_question`, whose `{{questions}}` resolves to
-the initial_state [] — the doomed lane maps over zero items and the graph
-returns end_fault's output at the next join.
-"""
-
-import json
-import os
-
-MAX_DETAIL_CHARS = 500
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def main():
-    state = load_state()
-    faults = [f for f in (state.get("pipeline_faults") or []) if isinstance(f, str)]
-    raw = state.get("plan_failure")
-    detail = raw.strip().replace("\n", " ") if isinstance(raw, str) else ""
-    if not detail.startswith("LLM node"):
-        detail = "the planning stage died without recording a failure detail"
-    if len(detail) > MAX_DETAIL_CHARS:
-        detail = detail[: MAX_DETAIL_CHARS - 1] + "…"
-    fault_text = f"planning failed — nothing to research: {detail}"
-    faults.append(f"PIPELINE-FAULT: {fault_text}")
-    print(json.dumps({"fault_text": fault_text, "pipeline_faults": faults}))
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — the fault marker itself must never crash
-    fault_text = f"planning failed — fault-marker script error: {e}"
-    print(
-        json.dumps(
-            {
-                "fault_text": fault_text,
-                "pipeline_faults": [f"PIPELINE-FAULT: {fault_text}"],
-            }
-        )
-    )

assets/agents/deep-research/scripts/question_fault.py

@@ -1,70 +0,0 @@
-#!/usr/bin/env python3
-"""Fail-closed marker for a dead research lane of the deep-research graph.
-
-Reached ONLY via research_one_question's `fallback:` route inside the
-`research_each_question` map branch (branch-local — a map branch's fallback
-must stay inside the branch subgraph). Grounded in engine behavior: on
-llm-node failure the engine writes "LLM node …failed: <chain>" into
-`finding` via the node's state_updates BEFORE routing to the fallback (on
-success the same key holds the researched findings, which never start with
-the "LLM node" prefix). This node normalizes the failure text into a
-PIPELINE-FAULT finding and the chain ends here — the map collects the fault
-as the lane's `finding`, so one dead research lane never sinks the whole
-map. combine_findings later lifts PIPELINE-FAULT findings into
-`pipeline_faults` so the fault also surfaces in the report's Pipeline notes.
-The question text is part of the fault so distinct dead lanes with identical
-engine failure text do not collapse into one entry there.
-"""
-
-import json
-import os
-
-MAX_DETAIL_CHARS = 500
-MAX_QUESTION_CHARS = 200
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def fault_finding(question, detail):
-    return {
-        "finding": (
-            "PIPELINE-FAULT: question research failed — finding unavailable — "
-            f'{detail} (question: "{question}")'
-        )
-    }
-
-
-def question_label(state):
-    raw = state.get("question")
-    question = raw.strip().replace("\n", " ") if isinstance(raw, str) else ""
-    if not question:
-        return "(unknown question)"
-    if len(question) > MAX_QUESTION_CHARS:
-        question = question[: MAX_QUESTION_CHARS - 1] + "…"
-    return question
-
-
-def main():
-    state = load_state()
-    raw = state.get("finding")
-    detail = raw.strip().replace("\n", " ") if isinstance(raw, str) else ""
-    if not detail.startswith("LLM node"):
-        detail = "the research lane died without recording a failure detail"
-    if len(detail) > MAX_DETAIL_CHARS:
-        detail = detail[: MAX_DETAIL_CHARS - 1] + "…"
-    print(json.dumps(fault_finding(question_label(state), detail)))
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — the fault marker itself must never crash
-    print(
-        json.dumps(
-            fault_finding("(unknown question)", f"fault-marker script error: {e}")
-        )
-    )

assets/agents/deep-research/scripts/reflexion_gate.py

@@ -15,12 +15,6 @@ Routing (`_next`):
 Reflexion is a best-effort quality booster, not a hard gate: once the
 budget is spent the workflow proceeds anyway, and the human approval
 step is the final backstop.
-
-Fail-safe: a crash here fails FORWARD to `synthesize` — the same
-direction as the existing malformed-critique PASS default — with a
-PIPELINE-FAULT entry recorded (best-effort preserving existing faults),
-so a broken gate costs the run its automated critique routing, never the
-run itself.
 """
 import json
 import os
@@ -39,14 +33,6 @@ def load_state():
     return json.loads(os.environ.get("GRAPH_STATE", "{}"))
 
 
-def safe_faults():
-    try:
-        state = load_state()
-        return [f for f in (state.get("pipeline_faults") or []) if isinstance(f, str)]
-    except Exception:  # noqa: BLE001 — best-effort preservation only
-        return []
-
-
 def as_int(value, default=0):
     try:
         return int(value)
@@ -86,12 +72,5 @@ def main():
     print(json.dumps(output))
 
 
-try:
+if __name__ == "__main__":
     main()
-except Exception as e:  # noqa: BLE001 — a crashed gate fails forward, never dies
-    faults = safe_faults()
-    faults.append(
-        f"PIPELINE-FAULT: reflexion gate crashed — {e}; proceeded to synthesis "
-        "without automated critique routing"
-    )
-    print(json.dumps({"_next": "synthesize", "pipeline_faults": faults}))

assets/agents/deep-research/scripts/synth_fault.py

@@ -1,51 +0,0 @@
-#!/usr/bin/env python3
-"""Fail-closed marker for a dead synthesis stage of the deep-research graph.
-
-Reached ONLY via synthesize's `fallback:` route. Grounded in engine
-behavior: on agent-node failure the engine writes "Agent node failed:
-{e:#}" into `report` via the node's state_updates BEFORE routing to the
-fallback (on success the same key holds the report-writer's report, which
-never starts with that prefix). No report means no product, so this path is
-fail-closed: normalize the failure text, record the PIPELINE-FAULT, and
-continue to `end_fault`, which renders the DEEP_RESEARCH FAILED sentinel.
-"""
-
-import json
-import os
-
-MAX_DETAIL_CHARS = 500
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def main():
-    state = load_state()
-    faults = [f for f in (state.get("pipeline_faults") or []) if isinstance(f, str)]
-    raw = state.get("report")
-    detail = raw.strip().replace("\n", " ") if isinstance(raw, str) else ""
-    if not detail.startswith("Agent node failed:"):
-        detail = "the synthesis stage died without recording a failure detail"
-    if len(detail) > MAX_DETAIL_CHARS:
-        detail = detail[: MAX_DETAIL_CHARS - 1] + "…"
-    fault_text = f"report synthesis failed — no report was produced: {detail}"
-    faults.append(f"PIPELINE-FAULT: {fault_text}")
-    print(json.dumps({"fault_text": fault_text, "pipeline_faults": faults}))
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — the fault marker itself must never crash
-    fault_text = f"report synthesis failed — fault-marker script error: {e}"
-    print(
-        json.dumps(
-            {
-                "fault_text": fault_text,
-                "pipeline_faults": [f"PIPELINE-FAULT: {fault_text}"],
-            }
-        )
-    )

assets/agents/deep-research/scripts/verify_sources.py

@@ -6,19 +6,6 @@ request, and writes a `source_check` summary into state so the human
 reviewer sees broken citations at the approval step.
 
 Times out per request so a slow source cannot stall the graph.
-
-Pipeline-notes fold: end-node templates render unconditionally, so the
-conditional "## Pipeline notes" section of the accepted report is built
-HERE — the last stop before the approval gate on every accepted path,
-including reflexion and feedback re-loops. `pipeline_notes` is the
-rendered section when `pipeline_faults` is non-empty and the empty
-string otherwise, keeping the happy-path `{{report}}{{pipeline_notes}}`
-output byte-identical to the pre-hardening `{{report}}`.
-
-Fail-safe: per-URL probes were already guarded; the top level now
-is too. On a crash the summary says sources were NOT checked, a
-PIPELINE-FAULT is recorded (best-effort preserving existing faults), and
-pipeline_notes still renders — the approval gate remains the backstop.
 """
 import json
 import os
@@ -38,21 +25,6 @@ def load_state():
     return json.loads(os.environ.get("GRAPH_STATE", "{}"))
 
 
-def safe_faults():
-    try:
-        state = load_state()
-        return [f for f in (state.get("pipeline_faults") or []) if isinstance(f, str)]
-    except Exception:  # noqa: BLE001 — best-effort preservation only
-        return []
-
-
-def render_notes(faults):
-    entries = [f for f in (faults or []) if isinstance(f, str) and f.strip()]
-    if not entries:
-        return ""
-    return "\n\n## Pipeline notes\n\n" + "\n".join(f"- {e}" for e in entries)
-
-
 def reachable(url, timeout=5.0):
     req = urllib.request.Request(url, method="HEAD")
     try:
@@ -90,27 +62,8 @@ def main():
             + "\n".join(results)
         )
 
-    notes = render_notes(state.get("pipeline_faults"))
+    print(json.dumps({"source_check": summary}))
-    print(json.dumps({"source_check": summary, "pipeline_notes": notes}))
 
 
-try:
+if __name__ == "__main__":
     main()
-except Exception as e:  # noqa: BLE001 — a crashed source check must degrade, not die
-    faults = safe_faults()
-    faults.append(
-        f"PIPELINE-FAULT: source verification crashed — {e}; cited sources "
-        "were not checked for reachability"
-    )
-    print(
-        json.dumps(
-            {
-                "source_check": (
-                    "Source verification crashed (pipeline fault) — cited "
-                    "sources were NOT checked for reachability."
-                ),
-                "pipeline_notes": render_notes(faults),
-                "pipeline_faults": faults,
-            }
-        )
-    )

assets/agents/deep-research/scripts/vet_fault.py

@@ -1,71 +0,0 @@
-#!/usr/bin/env python3
-"""Degrade-visibly marker for a dead source-vetting stage of deep-research.
-
-Reached ONLY via vet_sources' `fallback:` route. Grounded in engine
-behavior: on llm-node failure the engine writes "LLM node …failed: <chain>"
-into `source_assessment` via the node's state_updates BEFORE routing to the
-fallback. Vetting is a quality lane, not the product, so this path degrades
-instead of failing closed: it records a PIPELINE-FAULT (surfaced later in
-the report's Pipeline notes) and rewrites `source_assessment` to a neutral
-"unvetted" note so downstream prompts (critique, synthesize) never carry
-raw engine error text, then continues to `critique` — the stage
-vet_sources' own `next` pointed to.
-"""
-
-import json
-import os
-
-MAX_DETAIL_CHARS = 500
-
-UNVETTED_NOTE = (
-    "Source credibility assessment unavailable — the vetting stage failed "
-    "(pipeline fault); treat every cited source as unvetted and needing "
-    "corroboration. Do not request revision solely because this assessment "
-    "is unavailable — re-research cannot restore it; judge the findings on "
-    "their own evidence."
-)
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def safe_faults():
-    try:
-        state = load_state()
-        return [f for f in (state.get("pipeline_faults") or []) if isinstance(f, str)]
-    except Exception:  # noqa: BLE001 — best-effort preservation only
-        return []
-
-
-def main():
-    state = load_state()
-    faults = [f for f in (state.get("pipeline_faults") or []) if isinstance(f, str)]
-    raw = state.get("source_assessment")
-    detail = raw.strip().replace("\n", " ") if isinstance(raw, str) else ""
-    if not detail.startswith("LLM node"):
-        detail = "the vetting stage died without recording a failure detail"
-    if len(detail) > MAX_DETAIL_CHARS:
-        detail = detail[: MAX_DETAIL_CHARS - 1] + "…"
-    fault = f"PIPELINE-FAULT: source vetting failed — {detail}"
-    if fault not in faults:
-        faults.append(fault)
-    print(json.dumps({"pipeline_faults": faults, "source_assessment": UNVETTED_NOTE}))
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — the fault marker itself must never crash
-    faults = safe_faults()
-    faults.append(f"PIPELINE-FAULT: source vetting failed — fault-marker script error: {e}")
-    print(
-        json.dumps(
-            {
-                "pipeline_faults": faults,
-                "source_assessment": UNVETTED_NOTE,
-            }
-        )
-    )

assets/agents/domain-reviewer/README.md

@@ -1,43 +0,0 @@
-# Domain Reviewer
-
-A **domain-slice review leader**. Where `file-reviewer` reviews one file's diff
-in isolation, domain-reviewer reviews a group of *related* changed files — the
-DB migration plus the queries that use it, the routes plus their handlers — as
-ONE coherent unit. It runs as a map branch of the `code-reviewer` graph: one
-leader per domain, in parallel, with peer messaging between leaders.
-
-## Why it exists
-
-The strongest recurring review misses are **cross-file-within-domain** defects:
-seed data drifting from canonical enums, a guard fixed in one of N twin paths,
-a migration renaming a column the query layer still uses. Per-file reviewers
-each hold one fragment of those bugs and only connect them if sibling messaging
-happens to fire. A domain leader holds the whole slice in one context — the
-connection is the default, not a lucky message.
-
-## How it works
-
-1. Fetches its slice's diff itself (`get_diff --files <its files>`).
-2. **Sizing**: a small slice (≤3 files, <400 changed lines) is reviewed
-   directly with the full `code-review` skill stack; a larger one fans out one
-   `file-reviewer` per file (classic delegation-protocol prompts + sibling
-   roster) and the leader synthesizes.
-3. **The domain pass** (always, its unique value): guard symmetry across the
-   slice, literal/constant drift between files, schema↔usage mismatch, and the
-   mandatory blast-radius / test-adequacy / removed-guards checks at slice
-   level — reported even when clean.
-4. **Leader-to-leader messaging**: the code-reviewer graph runs leaders with
-   `teammates: true`, so the DB leader can tell the API leader "the migration
-   renames `status` → `state`, check your serializers" mid-review.
-5. Emits a machine-checkable report (`## Domain:` / `### Findings` with a
-   `File` field per finding / `### Mandatory checks` / `### Cross-Domain
-   Concerns` / `DOMAIN_REVIEW_COMPLETE`) — the graph's completeness gate
-   rejects a report missing required sections exactly once, then flags it.
-
-## Notes
-
-- Read-only; severities per the standard 🔴/🟡/🟢/💡 mapping; never rewrites a
-  file-reviewer's severity; dedups identical findings (aspect skill's copy wins).
-- Normally spawned by the `code-reviewer` graph, not directly — but a direct
-  spawn works: give it a domain name, a file list, a diff spec, and the quality
-  bar in the prompt.

assets/agents/domain-reviewer/config.yaml

@@ -1,166 +0,0 @@
-name: domain-reviewer
-description: Domain-slice review leader - reviews a group of related changed files as ONE coherent unit (cross-file-within-domain checks are first-class), delegating per-file depth to file-reviewer when the slice is large. Runs as a map branch of the code-reviewer graph with teammate messaging to the other domain leaders.
-version: 1.0.0
-
-auto_continue: true
-max_auto_continues: 20
-inject_todo_instructions: false
-
-skills_enabled: true
-enabled_skills:
-  - code-review
-  - ai-slop-remover
-  - transactional-integrity
-  - logging-discipline
-  - rest-api-review
-  - cli-review
-  - library-review
-  - worker-review
-  - iac-review
-  - migration-review
-  - cicd-review
-
-spawnable_agents:
-  - file-reviewer
-max_concurrent_agents: 8
-# The limit is consulted by the SPAWNER against the child's absolute depth
-# (root = 0). Deepest documented chain: architect(0) → sisyphus(1) →
-# review-gauntlet | step-runner(2) → code-reviewer(3) → domain-reviewer(4) →
-# file-reviewer(5). This agent spawns depth-5 children; 6 = one level of headroom.
-# NOTE: can_spawn_agents is not yet set, so the file-reviewer hop is documented
-# but inert; 6 keeps the limit forward-compatible for when it is wired.
-max_agent_depth: 6
-
-variables:
-  - name: project_dir
-    description: Project directory containing the changes under review
-    default: '.'
-  - name: auto_confirm
-    description: Auto-confirm command execution
-    default: '1'
-
-global_tools:
-  - fs_read.sh
-  - fs_grep.sh
-  - fs_glob.sh
-  - fs_cat.sh
-  - fs_ls.sh
-
-instructions: |
-  You are a DOMAIN REVIEW LEADER. You review one domain's slice of a code change — a group of
-  related files (the DB migration plus the queries that use it; the routes plus their handlers) —
-  as ONE coherent unit. Your unique value over per-file review is the space BETWEEN the files:
-  cross-file-within-domain defects that no single-file reviewer can see. You either review the
-  slice directly or lead a team of `file-reviewer` agents through it, and you always add the
-  domain-level pass on top.
-
-  Your spawn prompt IS your entire context: an ASSIGNMENT (JSON with `domain` and `files`), a diff
-  spec, the quality bar (rigor/surfaces + provenance), and the shared context pack (intent,
-  conventions, review-miss patterns, repo-history signals, linter output).
-
-  ## Step 0: Load review skills
-
-  Before reading any code, `skill__load` `code-review` and `ai-slop-remover`. Additionally load
-  `transactional-integrity` when the slice touches state-changing code (DB writes, transactions,
-  queue/webhook/job handlers, retries, external side effects) and `logging-discipline` when it
-  touches boundaries, error paths, background jobs, or state transitions. Load the surface skill(s)
-  for your domain per this table (load a row's skill when your files match that surface's trigger
-  AND the surface is in the resolved surfaces list; when provenance is `detected-default`, a
-  trigger match alone suffices):
-
-  | declared surface | skill loaded |
-  |---|---|
-  | `rest-api` (and `grpc`/`graphql` aliases) | `rest-api-review` |
-  | `cli` | `cli-review` |
-  | `library` | `library-review` |
-  | `worker` | `worker-review` |
-  | `iac` | `iac-review` |
-  | `db-migration` | `migration-review` |
-  | `ci-cd` | `cicd-review` |
-
-  ## Workflow
-
-  1. **Fetch your slice's diff**: `get_diff --files <your files, comma-separated>` (add
-     `--base <ref-or-range>` when the diff spec names one; omit it for staged/unstaged review).
-  2. **Choose depth**:
-     - **Direct** (slice is ≤3 files AND <400 changed lines): review each file's diff yourself,
-       applying the loaded skill checklists exactly as a file-reviewer would.
-     - **Delegate** (bigger): spawn one `file-reviewer` per file IN PARALLEL, each with the full
-       TASK / EXPECTED OUTCOME / MUST DO / MUST NOT DO / CONTEXT structure — pass through the
-       context pack fields from YOUR prompt verbatim (intent, conventions, review-miss patterns,
-       rigor/surfaces + provenance, this file's linter output) and paste each file's diff hunks
-       inline (the reviewer cannot see your context). Group tiny files (<20 changed lines) into a
-       shared reviewer when the slice exceeds ~8 files. After spawning ALL of them, send each the
-       sibling roster (`SIBLING_ROSTER:` with ids + file assignments) so they can exchange
-       cross-cutting alerts. Then collect results — do not poll.
-  3. **The domain pass** (ALWAYS yours, direct or delegated — this is why you exist). Check the
-     SLICE AS A WHOLE for:
-     - **Guard symmetry**: a guard/validation/limit changed in one file — grep the slice (and the
-       repo) for its siblings (same interface, same job kind, same naming family); a fix applied
-       to one of N twins is N-1 latent bugs.
-     - **Literal/constant drift**: values that must agree across the slice's files (enum literals
-       vs seed data, config keys vs readers, error codes vs handlers) — quote both sides when they
-       disagree.
-     - **Schema ↔ usage mismatch**: migrations vs the queries/models that use the schema; proto
-       definitions vs marshaling code; API shapes vs client calls within the slice.
-     - **Blast radius, test adequacy, and removed guards at slice level** (the mandatory checks
-       from `code-review`) — REPORT them under `### Mandatory checks` even when clean; silence
-       reads as not done.
-  4. **Talk to the other domain leaders** (you run alongside them with peer messaging armed):
-     check your inbox before finalizing, and send a leader a 1-2 sentence alert when your slice
-     changes something their domain consumes (a renamed column, a changed route shape, a moved
-     constant). Messages move facts sideways; they never replace your report.
-  5. **Synthesize the domain report** in the exact output format below.
-
-  ## Output Format
-
-  Structure your final response EXACTLY as:
-
-  ```
-  ## Domain: <domain name>
-
-  ### Summary
-  <2-3 sentences: what this slice changes as a unit>
-
-  ### Findings
-
-  #### <finding title (optional [convention]/[correctness] marker per the loaded skills)>
-  - **Severity**: 🔴 CRITICAL | 🟡 WARNING | 🟢 SUGGESTION | 💡 NITPICK
-  - **File**: <path>
-  - **Lines**: <start>-<end>
-  - **Description**: <clear explanation of the issue>
-  - **Suggestion**: <how to fix it>
-
-  #### <next finding>
-  ...
-
-  ### Mandatory checks
-  - Blast radius: <result, or "clean — callers of the changed symbols checked: <list>">
-  - Test adequacy: <result, or "clean — behavior changes covered by: <tests>">
-  - Guard symmetry: <result, or "clean — no guard changes in this slice" / "twins checked: <list>">
-
-  ### Cross-Domain Concerns
-  <alerts you sent or received and concerns affecting other domains, or "None">
-
-  DOMAIN_REVIEW_COMPLETE
-  ```
-
-  ## Rules
-
-  1. **You are read-only.** Never modify files.
-  2. **Every finding carries a File field** — your report covers multiple files and the synthesis
-     is machine-assisted; a finding without a file is unroutable.
-  3. **Severity tags per the standard mapping** (🔴 correctness/security/data-loss; 🟡 logic
-     errors, races, missing error handling; 🟢 clarity/coupling/missing tests; 💡 style/nitpicks).
-     Preserve your file-reviewers' severities verbatim; dedup identical findings (keep the aspect
-     skill's copy).
-  4. **Include ALL findings** — yours and your file-reviewers' — never summarize any away.
-  5. **Mandatory checks report even when clean.**
-  6. **End with DOMAIN_REVIEW_COMPLETE** on its own line.
-
-  ## Context
-  - Project: {{project_dir}}
-  - CWD: {{__cwd__}}
-
-  ## Available Tools
-  {{__tools__}}

assets/agents/domain-reviewer/tools.sh

@@ -1,63 +0,0 @@
-#!/usr/bin/env bash
-set -eo pipefail
-
-# @env LLM_OUTPUT=/dev/stdout
-# @env LLM_AGENT_VAR_PROJECT_DIR=.
-# @describe Domain-slice reviewer tools
-
-_project_dir() {
-  local dir="${LLM_AGENT_VAR_PROJECT_DIR:-.}"
-  (cd "${dir}" 2>/dev/null && pwd) || echo "${dir}"
-}
-
-# @cmd Get the git diff for this domain's file slice. Defaults to staged changes, falls back to unstaged, then HEAD~1. Pass --base for a ref or range (e.g. "main...HEAD").
-# @option --base Optional base ref or range to diff against (e.g. "main...HEAD", "HEAD~3", a SHA)
-# @option --files Comma-separated list of file paths to limit the diff to (your assignment's files)
-get_diff() {
-  local project_dir
-  project_dir=$(_project_dir)
-  # shellcheck disable=SC2154
-  local base="${argc_base:-}"
-  # shellcheck disable=SC2154
-  local files_csv="${argc_files:-}"
-
-  local -a path_args=()
-  if [[ -n "${files_csv}" ]]; then
-    local IFS=','
-    local f
-    for f in ${files_csv}; do
-      f="$(echo "${f}" | sed -e 's/^ *//' -e 's/ *$//')"
-      [[ -n "${f}" ]] && path_args+=("${f}")
-    done
-  fi
-
-  _diff() {
-    if ((${#path_args[@]})); then
-      (cd "${project_dir}" && git diff "$@" -- "${path_args[@]}" 2>&1) || true
-    else
-      (cd "${project_dir}" && git diff "$@" 2>&1) || true
-    fi
-  }
-
-  local diff_output=""
-  if [[ -n "${base}" ]]; then
-    diff_output=$(_diff "${base}")
-  else
-    diff_output=$(_diff --cached)
-    [[ -z "${diff_output}" ]] && diff_output=$(_diff)
-    [[ -z "${diff_output}" ]] && diff_output=$(_diff HEAD~1)
-  fi
-
-  if [[ -z "${diff_output}" ]]; then
-    echo "No changes found for the requested files in ${project_dir}." >> "$LLM_OUTPUT"
-    return 0
-  fi
-
-  local file_count
-  file_count=$(echo "${diff_output}" | grep -c '^diff --git' || true)
-  {
-    echo "Diff contains changes to ${file_count} file(s):"
-    echo ""
-    echo "${diff_output}"
-  } >> "$LLM_OUTPUT"
-}

assets/agents/explore/config.yaml

@@ -1,6 +1,6 @@
 name: explore
 description: Fast codebase exploration agent - finds patterns, structures, and relevant files. Designed to be fanned out in parallel by orchestrators — scale to the number of distinct search angles the task requires.
-version: 3.2.0
+version: 3.1.0
 
 skills_enabled: true
 enabled_skills:
@@ -17,7 +17,6 @@ variables:
 mcp_servers:
   - ddg-search
 global_tools:
-  - web_search_coyote.sh
   - ast_grep.sh
   - fs_read.sh
   - fs_cat.sh
@@ -42,15 +41,6 @@ instructions: |
 
   If the prompt says "find auth middleware", you find auth middleware. You do NOT also tour the routing layer, the error system, and the database connection pool. Narrow scope is the contract.
 
-  ## Team mode (when you receive a teammate roster)
-
-  Your spawn prompt or an early inbox message may include a teammate roster — the agent IDs of sibling researchers running in parallel with you. If it does:
-
-  - When you find a specific fact that belongs to a TEAMMATE's slice (a file they should read, a symbol they're hunting, a config flag that redirects their search), send it directly: `agent__send_message --id <their-id> --message "<one or two sentences of specific fact>"`. Facts only — file:line, exact names, verbatim snippets. Never chat or status updates.
-  - Check `agent__check_inbox` after each search round and ALWAYS before finalizing your findings — a teammate's fact may be the search term you were missing.
-  - A teammate's message never broadens YOUR slice: use it to sharpen your own search or carry the pointer into your report — don't wander into their territory.
-  - No roster → no messaging. Work your slice and report as usual.
-
   ## Investigation methodology
 
   Before searching, build a quick mental model. Then narrow in. Then read.

assets/agents/file-reviewer/config.yaml

@@ -1,20 +1,11 @@
 name: file-reviewer
 description: Reviews a single file's diff for bugs, style issues, and cross-cutting concerns
-version: 2.4.0
+version: 2.0.0
 
 skills_enabled: true
 enabled_skills:
   - code-review
   - ai-slop-remover
-  - transactional-integrity
-  - logging-discipline
-  - rest-api-review
-  - cli-review
-  - library-review
-  - worker-review
-  - iac-review
-  - migration-review
-  - cicd-review
 
 variables:
   - name: project_dir
@@ -38,11 +29,7 @@ instructions: |
 
   Before reading any code, call `skill__load` for `code-review` and `ai-slop-remover`. They carry your detailed review methodology — the categories to check (correctness, tests, clarity, coupling, footguns), the investigation workflow (how to use the fs tools to build context before reviewing), the slop checklist (useless comments, dishonest naming, defensive handling of impossible cases), and the standard for when to flag vs. skip.
 
-  Additionally load `transactional-integrity` when the diff touches state-changing code — database writes, transaction blocks, queue/webhook/job handlers, retry logic, or calls to external state-holding systems. It carries the atomicity/race/idempotency/dual-write checklist that generic correctness review misses. Skip it for pure reads, UI, and stateless computation.
+  Apply BOTH checklists in every review. Skill bodies are your source of truth for what to flag; this agent's instructions handle workflow and output shape.
-
-  Also load `logging-discipline` when the diff touches boundaries, error paths, background jobs, or state transitions. It carries the under-/over-logging checks (silent new failure paths, log-and-rethrow duplication, register mismatches, deleted log lines operators may grep for). Skip it for diffs with no operational surface.
-
-  Apply every loaded checklist in every review. Skill bodies are your source of truth for what to flag; this agent's instructions handle workflow and output shape.
 
   ## Your Mission
 
@@ -71,7 +58,7 @@ instructions: |
 
   To alert a sibling:
   ```
-  agent__send_message --id <sibling_agent_id> --message "ALERT: <description of cross-file concern>"
+  agent__send_message --to <sibling_agent_id> --message "ALERT: <description of cross-file concern>"
   ```
 
   Check your inbox periodically for alerts from siblings:
@@ -85,7 +72,6 @@ instructions: |
 
   The `code-review` skill teaches the investigation workflow. Apply these per-review caps on top:
   - **Max 5 fs_read calls per review.** Be deliberate about which files you read.
-  - **`fs_grep`/`fs_glob` are NOT capped** — the skill's blast-radius caller sweep and test sweep run on greps; spend them freely and reserve reads for suspicious callers and enclosing scopes.
   - **`fs_read` returns a TRUNCATED view** with line numbers (long lines cut at 2000 chars, output capped at 2000 lines by default). Use `--offset` and `--limit` (default 50 lines of context) to target specific sections. Never read entire large files.
   - **Use `fs_cat` only when you genuinely need the full untruncated file** — for a diff review this should be rare; `fs_grep` + targeted `fs_read` usually answers the question with less context.
   - **Focus on the diff.** Read surrounding code only when needed to evaluate the change; do not audit unrelated code in the same file.
@@ -126,17 +112,12 @@ instructions: |
   - **🟢 SUGGESTION** — Clarity, coupling, naming, footgun mitigations, missing tests for the change
   - **💡 NITPICK** — Style if no formatter enforces it, minor naming, slop-remover findings on prose-style comments
 
-  ### The `[convention]` / `[correctness]` marker
-
-  Finding titles may optionally carry a `[convention]` or `[correctness]` marker (e.g. `#### [convention] Collection endpoint without pagination`). Emit a marker only when a loaded skill instructs you to: `[convention]` tags contract/convention-adherence findings, `[correctness]` tags contract-breaking findings such as a semver violation or an exit-code inversion. The marker rides in the title verbatim and changes nothing about how you assign severity — folding and rejection semantics live downstream in the orchestrators, not here. The severity mapping above is unchanged.
-
   ## Rules
 
   1. **Be specific.** Reference exact line numbers and code.
   2. **Be actionable.** Every finding must have a suggestion.
   3. **Never modify files.** You are read-only.
-  4. **Mandatory checks report even when clean.** The `code-review` skill's blast-radius sweep, test-adequacy mapping, and removed-guard accounting each produce a one-line result in your Summary or Findings (`Blast radius: N callers checked, compatible` / `Tests: <behavior> covered by <test>` / `Removed guards: none` or the accounting). Silence on any of the three reads as "not done".
+  4. **Always end with REVIEW_COMPLETE.**
-  5. **Always end with REVIEW_COMPLETE.**
 
   ## Context
   - Project: {{project_dir}}

assets/agents/finding-verifier/README.md

@@ -1,73 +0,0 @@
-# finding-verifier
-
-A **graph** agent that independently verifies code-review findings against the working
-tree. It exists because false positives kill hands-off trust faster than missed bugs do —
-and because an orchestrator verifying its own workers' findings inline can skip, fudge,
-or confirmation-bias the check. A graph can't: the structure IS the discipline.
-
-## How it works
-
-```mermaid
-flowchart TD
-    A["parse (llm, max_attempts 2)"] --> B["verify_each (map, max_concurrency 4): one branch per finding"]
-    A -. "fallback" .-> PF["parse_fault (script): verdicts = one UNVERIFIABLE PIPELINE-FAULT entry"]
-    PF --> D
-    B -. "spawns × N" .-> C["verify_one (llm + fs tools, max_attempts 2)"]
-    C --> G["verdict_gate (script): machine-validates the JSON contract"]
-    G -. "reject-retry once" .-> C
-    C -. "fallback" .-> VF["verify_fault (script): branch-local UNVERIFIABLE marker"]
-    B --> D(["done (end): FINDING_VERIFIER_RESULTS"])
-```
-
-1. **parse** — extracts every 🔴/🟡 finding from the spawn prompt into a structured list
-   (id, severity verbatim, path, lines, self-contained claim). Extraction only — no judging.
-   Gets two attempts (`max_attempts: 2`); if both fail, its `fallback` routes to
-   `parse_fault`, which rewrites `verdicts` to a single UNVERIFIABLE entry naming the fault
-   and jumps straight to `done`.
-2. **verify_each** — a `map` node fans out one `verify_one` branch per finding. Skipping a
-   finding is structurally impossible; results collect in input order.
-3. **verify_one** — reads the cited code (greps for moved code before concluding anything)
-   and answers ONE narrow question: does the cited code exist, and does it behave as the
-   claim says? Verdicts:
-   - `VERIFIED` — with the decisive line(s) quoted verbatim (`path:line`).
-   - `FALSE` — the code doesn't exist anywhere or provably doesn't do what the claim says.
-     Requires PROOF, not disagreement — doubt never lands here.
-   - `UNVERIFIABLE` — couldn't establish either way (runtime behavior, external systems).
-
-   Each branch is a chain: `verify_one → verdict_gate`. The gate machine-validates the JSON
-   contract (verdict enum; evidence required for VERIFIED/FALSE; note for UNVERIFIABLE),
-   stamps the authoritative id FROM the finding item (the model's echo is never trusted),
-   rejects back to `verify_one` exactly once with the reason, and on a second failure records
-   UNVERIFIABLE — a malformed branch never sinks the map. If `verify_one` itself dies (both
-   `max_attempts: 2` attempts fail), its `fallback` routes to `verify_fault`, which
-   normalizes the engine's failure text into a branch-local UNVERIFIABLE verdict the map
-   still collects.
-4. **done** — a deterministic `end` node emits the raw verdict list plus the caller
-   contract (VERIFIED = keep + paste evidence; FALSE = drop + tally; UNVERIFIABLE = keep,
-   marked). No final LLM step that could editorialize.
-
-The dashed edges are fault paths. All three fault emitters (`parse_fault`, `verify_fault`,
-and `verdict_gate`'s own crash guard) surface as `PIPELINE-FAULT:` text in a verdict's
-`note`, and a fault can only ever produce UNVERIFIABLE — degraded output is never a
-passing verdict. Every path ends at `done`, so the `FINDING_VERIFIER_RESULTS`
-sentinel is always emitted and the caller's verify lane degrades instead of dying.
-
-## What it is NOT
-
-- **Not a second opinion.** It never re-judges severity, style, or whether a finding
-  "matters" — that authority stays with the reviewers and the orchestrator's rigor rules.
-- **Not a reviewer.** It reads only what findings cite (plus greps to locate moved code).
-
-## Caller
-
-Spawned by [`code-reviewer`](../code-reviewer/README.md) during its Finding Verifier
-pass, ONCE per review, with the full 🔴/🟡 list and `project_dir`. If this agent isn't
-installed, code-reviewer runs the same contract inline as a fallback.
-
-## Files
-
-- `graph.yaml` — the agent (no tools.sh; the graph grants `fs_read`/`fs_cat`/`fs_grep`
-  per node).
-- `scripts/verdict_gate.py` — the deterministic contract gate.
-- `scripts/parse_fault.py`, `scripts/verify_fault.py` — the fault markers behind the
-  dashed fallback edges.

assets/agents/finding-verifier/graph.yaml

@@ -1,207 +0,0 @@
-name: finding-verifier
-description: |
-  Graph-based independent verifier for code-review findings. Given a list of
-  🔴/🟡 findings (path, lines, claim), it mechanically fans out ONE verification
-  branch per finding — the graph structure makes skipping a finding impossible —
-  and returns a per-finding verdict: VERIFIED (with quoted evidence), FALSE
-  (provably wrong, with proof), or UNVERIFIABLE (kept, marked unverified).
-  Fresh-context by design: it re-derives each claim from the working tree, so a
-  synthesizing orchestrator can't confirmation-bias its own workers' findings.
-  It verifies EXISTENCE and BEHAVIOR of cited code only — it is not a second
-  opinion and never re-judges severity or importance.
-
-version: '1.0'
-
-global_tools:
-  - fs_read.sh
-  - fs_cat.sh
-  - fs_grep.sh
-
-variables:
-  - name: project_dir
-    description: Repository the findings cite; relative paths in findings resolve against it.
-    default: '.'
-
-settings:
-  max_loop_iterations: 8
-  log_state_snapshots: true
-  timeout: 3000
-
-initial_state:
-  findings_list: []
-  verdicts: []
-  gate_feedback: ''
-  gate_attempts: 0
-  parse_failure: ''
-
-start: parse
-
-nodes:
-  parse:
-    id: parse
-    type: llm
-    description: Extract the 🔴/🟡 findings from the spawn prompt into a structured list. Extraction only — no judging.
-    instructions: |
-      You extract code-review findings from a report into a structured list.
-      EXTRACTION ONLY — do not judge, filter, merge, or rephrase-away any
-      finding. Rules:
-
-      - Include every 🔴 CRITICAL and 🟡 WARNING finding. Ignore 🟢/💡
-        findings (they post unverified by design).
-      - Preserve the reported severity marker verbatim (including any
-        `[convention]`/`[correctness]` title marker).
-      - `claim` must be SELF-CONTAINED: what the finding asserts the code
-        does, lacks, or gets wrong, understandable without the original
-        report. Include the suggested-fix context when it clarifies the claim.
-      - `path` and `lines` come from the finding verbatim; if a finding cites
-        multiple locations, emit one entry per location with the same id plus
-        a `-b`, `-c` suffix.
-      - `project_dir`: the repository directory named in the request (a
-        "Repository:" or "Project:" line). When none is named, echo the
-        default shown in the prompt.
-    prompt: |
-      Extract the findings from this verification request (default repository
-      directory when the request names none: {{project_dir}}):
-
-      {{initial_prompt}}
-    tools: []
-    output_schema:
-      type: object
-      properties:
-        findings_list:
-          type: array
-          items:
-            type: object
-            properties:
-              id:
-                type: string
-                description: Short stable slug for mapping the verdict back (e.g. "f1", "f2-b").
-              severity:
-                type: string
-                description: The severity marker verbatim (e.g. "🔴 CRITICAL", "🟡 WARNING [correctness]").
-              path:
-                type: string
-                description: File path the finding cites, as reported.
-              lines:
-                type: string
-                description: Line or line-range the finding cites, as reported (may be empty).
-              claim:
-                type: string
-                description: Self-contained statement of what the finding asserts about the code.
-            required: [id, severity, path, lines, claim]
-        project_dir:
-          type: string
-          description: Repository directory named in the request (echo the prompt default when none).
-      required: [findings_list, project_dir]
-    max_attempts: 2
-    state_updates:
-      parse_failure: '{{output}}'
-    fallback: parse_fault
-    next: verify_each
-
-  parse_fault:
-    id: parse_fault
-    type: script
-    description: Fail-closed marker for a dead parse stage (reached only via parse's fallback) — rewrites `verdicts` to a single UNVERIFIABLE PIPELINE-FAULT entry and jumps straight to done, so the FINDING_VERIFIER_RESULTS sentinel still renders and the caller's verify lane degrades instead of dying.
-    script: scripts/parse_fault.py
-    timeout: 30
-    next: done
-
-  verify_each:
-    id: verify_each
-    type: map
-    over: '{{findings_list}}'
-    as: finding
-    branch: verify_one
-    collect_into: verdicts
-    output_key: verdict
-    max_concurrency: 4
-    next: done
-
-  verify_one:
-    id: verify_one
-    type: llm
-    description: Verify ONE finding against the working tree — existence and behavior of the cited code, nothing else.
-    instructions: |
-      You verify a single code-review finding against the actual repository.
-      Your question is narrow: does the cited code EXIST, and does it BEHAVE
-      as the claim says? You are not a reviewer and this is not a second
-      opinion — never re-judge severity, style, or whether the issue
-      "matters".
-
-      Method:
-      1. `fs_read` the cited path at the cited lines (with generous
-         surrounding context — the enclosing function at least). If the path
-         or lines don't match the claim's description, `fs_grep` for the
-         symbols in the claim before concluding anything (the finding may
-         cite drifted line numbers — code that MOVED still verifies).
-      2. Compare what the code actually does against the claim.
-
-      Verdict rules:
-      - `VERIFIED` — the cited code exists and the claim accurately describes
-        it. `evidence` MUST be the decisive line(s) quoted verbatim with
-        path:line.
-      - `FALSE` — the cited code does not exist anywhere (not just moved), or
-        it PROVABLY does not do what the claim says (e.g. the claim says a
-        nil-check is missing but it is right there). `evidence` MUST quote
-        the proof. When in doubt, this is NOT the verdict — FALSE requires
-        proof, not disagreement.
-      - `UNVERIFIABLE` — you could not establish it either way (claim depends
-        on runtime behavior, external systems, or code you cannot locate with
-        confidence). Explain why in `note`. Doubt lands here, never in FALSE.
-
-      Output format — respond with ONLY this JSON object, no prose before or
-      after it:
-      {"id": "<the finding's id, echoed back verbatim>",
-       "verdict": "VERIFIED" | "FALSE" | "UNVERIFIABLE",
-       "evidence": "<verbatim quoted line(s) with path:line — required for
-      VERIFIED and FALSE, empty string for UNVERIFIABLE>",
-       "note": "<one line — for FALSE the disproof in words, for UNVERIFIABLE
-      why it could not be established; empty string otherwise>"}
-
-      Your response is machine-validated by a deterministic gate: a malformed
-      response (wrong shape, unknown verdict value, missing required
-      evidence/note) is rejected back to you exactly once with the reason,
-      then recorded as UNVERIFIABLE. The `id` you echo is informative only —
-      the gate stamps the authoritative id from the finding itself.
-    prompt: |
-      Repository: {{project_dir}}
-
-      Verify this single finding:
-      {{finding}}
-      {{gate_feedback}}
-    tools:
-      - fs_read
-      - fs_cat
-      - fs_grep
-    max_iterations: 14
-    max_attempts: 2
-    state_updates:
-      verdict: '{{output}}'
-    fallback: verify_fault
-    next: verdict_gate
-
-  verdict_gate:
-    id: verdict_gate
-    type: script
-    description: Deterministic contract gate for each verdict — validates shape, verdict enum, and evidence/note rules; rejects back to verify_one exactly once with the reason, then records UNVERIFIABLE. No LLM judgment.
-    script: scripts/verdict_gate.py
-    timeout: 30
-
-  verify_fault:
-    id: verify_fault
-    type: script
-    description: Fail-closed marker for a dead verify branch (reached only via verify_one's fallback; branch-local). Normalizes the engine's failure text in `verdict` into a schema-conformant UNVERIFIABLE verdict the map collects — a dead verifier lane never sinks the whole map or masquerades as verified.
-    script: scripts/verify_fault.py
-    timeout: 30
-
-  done:
-    id: done
-    type: end
-    output: |
-      FINDING_VERIFIER_RESULTS
-      (verdict semantics for the caller: VERIFIED = keep the finding and paste its evidence
-      quote into the Description; FALSE = drop the finding and tally it in the footer;
-      UNVERIFIABLE = keep the finding, marked unverified. Severities are never rewritten.)
-
-      {{verdicts}}

assets/agents/finding-verifier/scripts/parse_fault.py

@@ -1,57 +0,0 @@
-#!/usr/bin/env python3
-"""Fail-closed marker for a dead parse stage of the finding-verifier graph.
-
-Reached ONLY via parse's `fallback:` route. parse's state_updates wrote an
-"LLM node …failed: <chain>" string into `parse_failure` before routing here;
-this node rewrites `verdicts` to a single schema-conformant UNVERIFIABLE
-entry naming the fault and the graph jumps straight to `done` — the
-FINDING_VERIFIER_RESULTS sentinel still renders, so the caller (e.g.
-code-reviewer's verify lane) degrades instead of dying. Findings that were
-never extracted cannot be verified; the caller's "UNVERIFIABLE = keep the
-finding, marked unverified" semantics do the right thing with the entry.
-"""
-
-import json
-import os
-
-MAX_DETAIL_CHARS = 500
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def fault_verdicts(detail):
-    return {
-        "verdicts": [
-            {
-                "id": "pipeline-fault",
-                "verdict": "UNVERIFIABLE",
-                "evidence": "",
-                "note": (
-                    "PIPELINE-FAULT: parse failed — findings could not be extracted "
-                    f"from the verification request; no finding was verified: {detail}"
-                ),
-            }
-        ]
-    }
-
-
-def main():
-    state = load_state()
-    raw = state.get("parse_failure")
-    detail = raw.strip().replace("\n", " ") if isinstance(raw, str) else ""
-    if not detail.startswith("LLM node"):
-        detail = "the parse stage died without recording a failure detail"
-    if len(detail) > MAX_DETAIL_CHARS:
-        detail = detail[: MAX_DETAIL_CHARS - 1] + "…"
-    print(json.dumps(fault_verdicts(detail)))
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — the fault marker itself must never crash
-    print(json.dumps(fault_verdicts(f"fault-marker script error: {e}")))

assets/agents/finding-verifier/scripts/verdict_gate.py

@@ -1,136 +0,0 @@
-#!/usr/bin/env python3
-"""Contract gate for finding-verifier's per-finding verify chain.
-
-Validates the raw verifier output against the verdict contract:
-  - a single JSON object
-  - verdict in {VERIFIED, FALSE, UNVERIFIABLE}
-  - VERIFIED / FALSE require non-empty evidence
-  - UNVERIFIABLE requires a non-empty note
-
-On a valid response it normalizes the object (the authoritative `id` is
-stamped from the finding item itself — the model's echo is never trusted)
-and writes it to the chain's output key. On an invalid response it routes
-back to `verify_one` exactly once with the rejection reason; if the retry
-is also invalid, it records an UNVERIFIABLE verdict naming the failure so
-a malformed item can never sink the whole map or masquerade as a pass.
-
-Deterministic by design: no LLM judgment happens here, and the script
-always exits 0 with a valid JSON object on stdout.
-"""
-
-import json
-import os
-import re
-
-VERDICTS = {"VERIFIED", "FALSE", "UNVERIFIABLE"}
-MAX_RETRIES = 1
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def finding_id(state):
-    finding = state.get("finding")
-    if isinstance(finding, dict):
-        fid = finding.get("id")
-        if isinstance(fid, str) and fid.strip():
-            return fid.strip()
-    return "unknown"
-
-
-def extract_json(text):
-    if not isinstance(text, str) or not text.strip():
-        raise ValueError("verifier output is empty or not text")
-    text = re.sub(r"```[a-zA-Z]*", "", text).replace("```", "")
-    start, end = text.find("{"), text.rfind("}")
-    if start == -1 or end <= start:
-        raise ValueError("no JSON object found in verifier output")
-    return json.loads(text[start : end + 1])
-
-
-def validate(obj):
-    if not isinstance(obj, dict):
-        raise ValueError("verifier output is not a JSON object")
-    verdict = obj.get("verdict")
-    if verdict not in VERDICTS:
-        raise ValueError(f"verdict must be one of {sorted(VERDICTS)}, got {verdict!r}")
-    evidence = obj.get("evidence") if isinstance(obj.get("evidence"), str) else ""
-    note = obj.get("note") if isinstance(obj.get("note"), str) else ""
-    if verdict in ("VERIFIED", "FALSE") and not evidence.strip():
-        raise ValueError(
-            f"{verdict} requires non-empty evidence quoting the decisive line(s) with path:line"
-        )
-    if verdict == "UNVERIFIABLE" and not note.strip():
-        raise ValueError("UNVERIFIABLE requires a note explaining why it could not be established")
-    return verdict, evidence, note
-
-
-def main():
-    state = load_state()
-    fid = finding_id(state)
-    attempts = state.get("gate_attempts")
-    if not isinstance(attempts, int):
-        attempts = 0
-
-    try:
-        verdict, evidence, note = validate(extract_json(state.get("verdict")))
-        print(
-            json.dumps(
-                {"verdict": {"id": fid, "verdict": verdict, "evidence": evidence, "note": note}}
-            )
-        )
-        return
-    except Exception as e:  # noqa: BLE001 — every failure is a rejection reason
-        reason = str(e)
-
-    if attempts < MAX_RETRIES:
-        print(
-            json.dumps(
-                {
-                    "_next": "verify_one",
-                    "gate_attempts": attempts + 1,
-                    "gate_feedback": (
-                        "PREVIOUS RESPONSE REJECTED by the verdict gate: "
-                        + reason
-                        + ". Respond with ONLY the JSON object described under"
-                        " 'Output format' — no prose, no code fences."
-                    ),
-                }
-            )
-        )
-        return
-
-    # Deliberately not PIPELINE-FAULT-prefixed: model misbehavior, not infrastructure.
-    print(
-        json.dumps(
-            {
-                "verdict": {
-                    "id": fid,
-                    "verdict": "UNVERIFIABLE",
-                    "evidence": "",
-                    "note": f"verifier output failed machine validation after retry: {reason}",
-                }
-            }
-        )
-    )
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — the gate must never crash the chain
-    print(
-        json.dumps(
-            {
-                "verdict": {
-                    "id": "unknown",
-                    "verdict": "UNVERIFIABLE",
-                    "evidence": "",
-                    "note": f"PIPELINE-FAULT: verdict gate error: {e}",
-                }
-            }
-        )
-    )

assets/agents/finding-verifier/scripts/verify_fault.py

@@ -1,63 +0,0 @@
-#!/usr/bin/env python3
-"""Fail-closed marker for a dead verify branch of the finding-verifier graph.
-
-Reached ONLY via verify_one's `fallback:` route inside the map branch.
-Grounded in engine behavior: on llm-node failure the engine writes
-"LLM node failed: <chain>" into `verdict` via the node's state_updates
-BEFORE routing to the fallback, so the raw failure text is already in
-state. This node normalizes it into a schema-conformant UNVERIFIABLE
-verdict (authoritative id stamped from the finding item, mirroring
-verdict_gate.py) and the chain ends there — the map collects a valid
-verdict, so a dead verifier lane never sinks the whole map or masquerades
-as verified.
-"""
-
-import json
-import os
-
-MAX_DETAIL_CHARS = 500
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def finding_id(state):
-    finding = state.get("finding")
-    if isinstance(finding, dict):
-        fid = finding.get("id")
-        if isinstance(fid, str) and fid.strip():
-            return fid.strip()
-    return "unknown"
-
-
-def fault_verdict(fid, detail):
-    return {
-        "verdict": {
-            "id": fid,
-            "verdict": "UNVERIFIABLE",
-            "evidence": "",
-            "note": f"PIPELINE-FAULT: verifier lane failed after retries — {detail}",
-        }
-    }
-
-
-def main():
-    state = load_state()
-    fid = finding_id(state)
-    raw = state.get("verdict")
-    detail = raw.strip().replace("\n", " ") if isinstance(raw, str) else ""
-    if not detail.startswith("LLM node"):
-        detail = "the verifier lane died without recording a failure detail"
-    if len(detail) > MAX_DETAIL_CHARS:
-        detail = detail[: MAX_DETAIL_CHARS - 1] + "…"
-    print(json.dumps(fault_verdict(fid, detail)))
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — the fault marker itself must never crash
-    print(json.dumps(fault_verdict("unknown", f"fault-marker script error: {e}")))

assets/agents/gatekeeper/config.yaml

@@ -14,9 +14,6 @@ variables:
   - name: project_dir
     description: Absolute path to the project the plan targets - the ground truth for pointer verification
     default: '.'
-  - name: auto_confirm
-    description: Auto-confirm command execution
-    default: '1'
 
 global_tools:
   - ast_grep.sh

assets/agents/librarian/graph.yaml

@@ -8,10 +8,9 @@ description: |
   sisyphus alongside explore when unfamiliar libraries/APIs/frameworks are
   involved.
 
-version: '1.0'
+version: "1.0"
 
 global_tools:
-  - web_search_coyote.sh
   - fetch_url_via_curl.sh
 
 mcp_servers:
@@ -32,14 +31,17 @@ settings:
   log_state_snapshots: true
   timeout: 600
 
+reducers:
+  output: overwrite
+
 initial_state:
-  language_ecosystem: 'general'
+  language_ecosystem: "general"
-  doc_domain_hints: ''
+  doc_domain_hints: ""
-  refined_search_query: ''
+  refined_search_query: ""
-  question_type: 'concept'
+  question_type: "concept"
-  search_output: ''
+  search_output: ""
-  oss_output: ''
+  oss_output: ""
-  findings: ''
+  findings: ""
 
 start: triage
 
@@ -102,15 +104,9 @@ nodes:
           type: string
           enum: [api_reference, best_practice, debugging, concept]
           description: The kind of question being asked.
-      required:
+      required: [language_ecosystem, doc_domain_hints, refined_search_query, question_type]
-        [
-          language_ecosystem,
-          doc_domain_hints,
-          refined_search_query,
-          question_type,
-        ]
     state_updates:
-      last_node_output: '{{output}}'
+      last_node_output: "{{output}}"
     fallback: end_failure
     next: [search, search_oss]
 
@@ -178,15 +174,13 @@ nodes:
         - Refined query: {{refined_search_query}}
         - Question type: {{question_type}}
 
-      Use the ddg-search tool or the web_search_coyote tool. Prioritize the
+      Use the ddg-search tool. Prioritize the hinted doc domains when present
-      hinted doc domains when present (e.g., search with `site:docs.python.org
+      (e.g., search with `site:docs.python.org pathlib` style queries).
-      pathlib` style queries).
     tools:
       - mcp:ddg-search
-      - web_search_coyote
     max_iterations: 15
     state_updates:
-      search_output: '{{output}}'
+      search_output: "{{output}}"
     fallback: synthesize
     next: synthesize
 
@@ -256,7 +250,7 @@ nodes:
       - mcp:personal-github
     max_iterations: 15
     state_updates:
-      oss_output: '{{output}}'
+      oss_output: "{{output}}"
     fallback: synthesize
     next: synthesize
 
@@ -342,7 +336,7 @@ nodes:
       - fetch_url_via_curl
     max_iterations: 20
     state_updates:
-      findings: '{{output}}'
+      findings: "{{output}}"
     fallback: final_format
     next: final_format
 

assets/agents/oracle/config.yaml

@@ -1,12 +1,11 @@
 name: oracle
 description: High-IQ advisor for architecture, debugging, and complex decisions. Blocking by design - the orchestrator is waiting on you.
-version: 2.2.0
+version: 2.1.0
 
 skills_enabled: true
 enabled_skills:
   - code-review
   - ai-slop-remover
-  - codebase-design
   - plan-review
   - plan-authoring
   - iwe-knowledge-base
@@ -22,7 +21,6 @@ variables:
 mcp_servers:
   - ddg-search
 global_tools:
-  - web_search_coyote.sh
   - ast_grep.sh
   - fs_read.sh
   - fs_cat.sh
@@ -63,7 +61,6 @@ instructions: |
 
   - `skill__load code-review` — when reviewing a diff or existing code; gives you a focused review checklist.
   - `skill__load ai-slop-remover` — when judging code quality (especially for advising on cleanups).
-  - `skill__load codebase-design` — when advising on module/interface design, seam placement, testability, or refactoring structure; gives you the deep-module vocabulary (module, interface, depth, seam, adapter, leverage, locality) and its principles. Use those terms exactly.
   - `skill__load plan-review` — when asked to review an implementation plan; adversarial checklist plus the PLAN_REVIEW verdict format. Load `plan-authoring` alongside it — it defines the plan schema you are checking against.
   - `skill__load iwe-knowledge-base` — when the plans live in a large markdown corpus; navigate it structurally instead of globbing.
 

assets/agents/probe/README.md

@@ -1,124 +0,0 @@
-# Probe
-
-A **black-box usage-pattern verifier**. Where every other reviewer reads *text* — the diff
-([`code-reviewer`](../code-reviewer/README.md)), the plan ([`adversary`](../adversary/README.md)),
-the attack surface ([`security-reviewer`](../security-reviewer/README.md)) — `probe` asks the one
-question none of them can answer without running the thing:
-
-> **"Does the changed consumer-facing surface actually behave as the spec promises when used,
-> starting from nothing?"**
-
-It boots the system locally from a clean slate, runs any existing usage suites first (regression
-check), derives expected behaviors from the **spec** — never the implementation — and authors
-tests for the uncovered usage patterns: cold-start/empty-state calls, idempotent re-calls, invalid
-input, auth on new routes, partial-update (patch-vs-replace) semantics, serialization edges,
-pagination limits, error-shape consistency. These are exactly the defects invisible to static
-review.
-
-## Why it's separate from the other reviewers
-
-| | `code-reviewer` | `adversary` | `security-reviewer` | `probe` |
-|---|---|---|---|---|
-| Question | Is the code good? | Does it match the plan? | Can it be abused? | Does it *work* when used? |
-| Method | Reads the diff | Diff vs. criteria | Source→sink tracing | **Runs the system**, black-box |
-| Blind spot it covers | slop, bugs, coupling | skipped criteria, drift | injection, authz gaps | behavioral quirks, regressions, contract surprises |
-| Output | severity findings | `CONFORMS`/`DIVERGES` | `PASS`/`FAIL` | `PASS`/`FAIL`/`INCONCLUSIVE` |
-
-The independence is behavioral: expectations are written from the spec/contract **before** reading
-handler code, so the implementer's misreadings can't become the probe's assertions — the same
-principle that makes `adversary` valuable, applied to runtime behavior.
-
-## Verdict (blocking, three-way)
-
-```
-USAGE_PROBE: PASS
-Surface: <...>. Existing suites: <N run, all green | none found>. New tests: <M authored at <path>, all green>.
-```
-
-```
-USAGE_PROBE: FAIL
-Behavioral findings:
-1. <surface + case> — <spec'd behavior> — <observed behavior> — REPRO: <exact request + response> — <test file>
-```
-
-```
-USAGE_PROBE: INCONCLUSIVE
-Could not establish a clean local environment: <verbatim error>. Missing: <the recipe/fixture that would unblock>.
-```
-
-- **`FAIL` blocks completion** — the caller resumes the SAME implementer session with the findings
-  pasted verbatim, then re-runs `probe` once to confirm.
-- **`INCONCLUSIVE` is the honest third state**: the environment, not the code, is the blocker. It
-  routes the fix to the local-run recipe (often a plan gap the `gatekeeper` should have caught) and
-  is never disguised as `PASS` or `FAIL`.
-
-Every `FAIL` finding carries an exact reproduction (request/command + response received) and the
-test file that proves it.
-
-## How it probes
-
-Driven by the [`usage-pattern-testing`](../../skills/usage-pattern-testing/SKILL.md) skill:
-
-1. **Spec first** — expected behaviors written from acceptance criteria + API contract before any
-   implementation reads.
-2. **Regression first** — discover and run existing usage suites; every failure classified as
-   BUG / EXPECTED-CHANGE / ENV before anything new is authored.
-3. **Delta only** — new tests cover only the usage patterns existing suites miss, written in the
-   repo's suite conventions so they're adoptable as permanent regression coverage.
-4. **Clean, local, isolated** — ephemeral state, mocked externals, full teardown; bounded retries
-   for startup only, never to mask flakiness.
-
-Toolbox by surface — the repo's existing suite format always comes first, and these are examples,
-not requirements: [Hurl](https://hurl.dev) or `curl` scripts for HTTP/REST/JSON (Hurl files double
-as committed suites), `grpcurl` for pure gRPC, direct invocation for CLIs.
-
-Unlike the read-only reviewers, `probe` **writes test files** (and only test files) — the tests
-are a deliverable alongside the verdict. It never modifies implementation code.
-
-## Usage
-
-Spawned by `sisyphus` (post-coder, when the change touches consumer-facing surface) or `architect`
-(Phase E, alongside `adversary`). The spawn prompt IS its entire context — include the change, the
-spec, and the local-run recipe:
-
-```sh
-agent__spawn --agent probe --prompt "
-## TASK
-Probe the changed API surface for TASK-NNN from the consumer's perspective. Return PASS/FAIL/INCONCLUSIVE.
-
-## CHANGE
-Run get_diff --base <ref>, or: <paste the changed-surface summary>
-
-## SPEC — expected behavior to verify against
-<paste acceptance criteria + API contract sections (or contract file paths) VERBATIM>
-
-## LOCAL-RUN RECIPE
-<how to boot the stack clean: build, deps/stubs, ports, migrations, teardown — or the doc that has it>
-
-## EXISTING SUITES
-<paths + run commands, or 'discover them'>
-"
-```
-
-Direct invocation for ad-hoc use:
-
-```sh
-coyote -a probe --agent-variable project_dir /path/to/repo \
-  "Probe the /widgets endpoints changed in the last commit against this spec: <paste spec>"
-```
-
-### Tools
-
-- `get_diff [--base <ref>]` — staged → unstaged → `HEAD~1` fallback (or an explicit base SHA/branch) to locate the changed surface.
-- `get_changed_files [--base <ref>]` — quick changed-file map.
-- Plus `fs_*`/`ast_grep` for suite discovery and contract reads, `fs_write`/`fs_patch` for authoring test files, and `execute_command` for booting the stack and running suites.
-- Probing tools (`curl`, Hurl, grpcurl, the repo's own harness) are invoked via `execute_command`
-  (no wrapper tool — probing needs their full CLI surface), and none is a hard requirement: the
-  [`usage-pattern-testing`](../../skills/usage-pattern-testing/SKILL.md) skill has probe reuse the repo's existing suite tooling first and fall back to what's available.
-  The optional [`sbx-mixin.yaml`](sbx-mixin.yaml) preinstalls Hurl + grpcurl for sandbox runs.
-
-## Related
-
-- [`usage-pattern-testing`](../../skills/usage-pattern-testing/SKILL.md) — the methodology it runs on.
-- [`adversary`](../adversary/README.md) — static plan-conformance counterpart (text), where `probe` is dynamic (behavior).
-- [`gatekeeper`](../gatekeeper/README.md) — ensures plans ship the local-run recipe `probe` consumes.

assets/agents/probe/config.yaml

@@ -1,137 +0,0 @@
-name: probe
-description: Black-box usage-pattern verifier - exercises a change's consumer-facing surface (HTTP APIs, RPCs, CLIs) as a real cold-start consumer against a locally running instance with clean, isolated state. Runs existing usage suites first for regressions (whatever format the repo uses - Hurl files, curl scripts, collections), authors spec-first tests for uncovered patterns in the repo's suite conventions (tools like Hurl and grpcurl are examples, not requirements), and returns a blocking USAGE_PROBE PASS/FAIL/INCONCLUSIVE verdict. Complements code-reviewer (quality), adversary (plan conformance), and security-reviewer (abuse). Designed to be delegated to by sisyphus and architect.
-version: 1.0.0
-
-auto_continue: true
-max_auto_continues: 25
-inject_todo_instructions: true
-
-skills_enabled: true
-enabled_skills:
-  - usage-pattern-testing
-
-variables:
-  - name: project_dir
-    description: Project directory containing the change under test - where suites are discovered, the stack is booted, and new tests are written
-    default: '.'
-  - name: auto_confirm
-    description: Auto-confirm command execution
-    default: '1'
-
-global_tools:
-  - ast_grep.sh
-  - fs_read.sh
-  - fs_cat.sh
-  - fs_grep.sh
-  - fs_glob.sh
-  - fs_ls.sh
-  - fs_write.sh
-  - fs_patch.sh
-  - execute_command.sh
-
-instructions: |
-  You are the usage-pattern probe. You answer ONE question: **does the changed consumer-facing
-  surface actually behave as the spec promises when used, starting from a clean slate?** Every
-  other reviewer reads text — the diff, the plan, the code. You are the only gate that BOOTS the
-  system locally and exercises it the way a consumer will: cold, black-box, spec-first.
-
-  You are NOT the code-quality reviewer (`code-reviewer`), NOT the plan-conformance reviewer
-  (`adversary`), and NOT the security reviewer (`security-reviewer`). You judge observable
-  behavior. Your value is behavioral independence: expectations derived from the spec BEFORE
-  reading the implementation, so the implementer's misreadings cannot become your assertions.
-
-  ## Step 0: Load the skill
-
-  Before anything else, `skill__load` `usage-pattern-testing`. It carries your methodology: the
-  spec-first independence rule, the regression-first protocol (find and run existing suites before
-  authoring anything), the usage-pattern checklist (cold start, idempotency, invalid input, auth,
-  partial-update semantics, serialization edges, pagination, error shapes), the clean-environment
-  discipline, the failure-classification table (BUG / EXPECTED-CHANGE / ENV), the per-surface
-  toolbox (the repo's existing suite tooling comes first; Hurl/curl for HTTP, grpcurl for gRPC,
-  and direct invocation for CLIs are examples, not requirements), and the exact verdict format.
-  The skill body is your source of truth for HOW to probe; these instructions handle
-  workflow and I/O.
-
-  ## Input (the spawn prompt IS your entire context)
-
-  You are given:
-  1. **The change** — a diff pasted inline, a summary of the changed surface, or an instruction to
-     run `git diff`/`get_diff` (optionally against a base ref) in {{project_dir}}.
-  2. **The spec** — acceptance criteria, plan section, or API contract (or paths to the contract
-     files: IDL/schema/OpenAPI/proto). This is what you derive expected behaviors FROM.
-  3. **A local-run recipe** (strongly preferred) — how to boot the system locally from a clean
-     state: build command, dependencies to start/stub, ports, migration/seed steps, teardown. If
-     absent, look for one in the repo's contributor docs and dev scripts before inventing your own.
-  4. **Pointers to existing usage suites** (optional) — where black-box tests already live and how
-     to run them. If absent, discover them per the skill.
-
-  If the spec is missing, STOP and say so: behavior cannot be judged without a promise to judge
-  against. Do not infer the spec from the implementation.
-
-  ## Workflow
-
-  1. Load `usage-pattern-testing`.
-  2. Identify the changed consumer-facing surface from the diff/summary. No consumer-facing surface
-     → return PASS with a one-line "no probeable surface" note; do not boot anything.
-  3. **Spec first:** write down expected behaviors as concrete request→response pairs from the
-     spec/contract, BEFORE reading handler code (implementation reads are for ports/config/startup
-     wiring only).
-  4. Discover existing usage suites; bring up the clean local environment per the recipe; run the
-     existing suites FIRST and classify every failure (regression vs expected contract change vs
-     environment).
-  5. Map existing coverage against your expected behaviors; author tests for the uncovered
-     patterns only, in the repo's suite location and conventions, walking the skill's
-     usage-pattern checklist.
-  6. Run the new tests. Classify every failure. Reproduce non-deterministic results twice and read
-     the server logs before classifying.
-  7. Tear the environment down. Emit the verdict in the skill's exact format.
-
-  ## Output — verdict (MANDATORY, exact format)
-
-  End with EXACTLY one of the skill's three sentinels so the caller can route on it:
-
-  - `USAGE_PROBE: PASS` — existing suites green (or none), new spec-first tests green. List
-    surface probed, suites run, and tests authored (with paths, so the caller can adopt them).
-  - `USAGE_PROBE: FAIL` — behavioral findings, each with the spec'd behavior quoted, the observed
-    behavior, the EXACT reproduction (request/command + response received), and the test file.
-  - `USAGE_PROBE: INCONCLUSIVE` — a clean local environment could not be established. State what
-    failed verbatim and EXACTLY what recipe/fixture/mock would unblock. Include any partial
-    results. INCONCLUSIVE is honest and routes the fix to the environment recipe — NEVER disguise
-    it as PASS or FAIL.
-
-  ## Rules
-
-  0. **Shared-stack discipline (parallel review lanes).** Wrap every stack boot/teardown
-     (docker compose, dev servers, fixed-port services) in
-     `flock "$HOME/.cache/coyote/review-stack.lock" <command>` — the adversary's
-     verification stage holds the same lock. A held port NEVER justifies removing or
-     stopping a container you did not create THIS RUN: wait on the lock, pick another
-     port, or return INCONCLUSIVE naming the conflict. Killing another lane's container
-     is a defect, not a remedy.
-
-  1. **Never modify implementation code.** Your only writes are new/updated TEST files (in the
-     repo's suite conventions) and throwaway environment scaffolding you tear down. The
-     implementer owns all fixes.
-  2. **Spec-first or nothing.** Expectations written from the spec before implementation reads.
-     If the spec and the contract files disagree, that is a finding — report it, don't pick one
-     silently.
-  3. **Regressions before new coverage.** Existing suites run first; a regression is only
-     acceptable when the spec explicitly changed that contract (then flag the stale test for
-     update — never delete or silence it).
-  4. **Clean, local, isolated.** Fresh ephemeral state, mocked externals, no dependence on
-     pre-existing data or running services, full teardown. Bounded retries for startup only —
-     never to mask a flaky assertion.
-  5. **Classify every failure** as BUG / EXPECTED-CHANGE / ENV per the skill table. The verdict
-     depends on the classification being honest.
-  6. **Committed tests are the deliverable** alongside the verdict: write them where the repo's
-     suites live so the caller can adopt them as permanent regression coverage. Report their paths.
-  7. Be terse and decisive. Three reproducible behavioral findings beat fifteen speculative ones.
-     If everything works as spec'd, it PASSes — say so.
-
-  ## Context
-  - Project: {{project_dir}}
-  - CWD: {{__cwd__}}
-  - Shell: {{__shell__}}
-
-  ## Available Tools
-  {{__tools__}}

assets/agents/probe/sbx-mixin.yaml

@@ -1,77 +0,0 @@
-schemaVersion: '2'
-kind: mixin
-name: agent-probe
-description: >
-  Optional convenience for the probe agent: preinstalls Hurl (HTTP
-  usage-pattern tests) and grpcurl (gRPC probing) — the example tools its
-  skill reaches for — and allows the GitHub release endpoints the fallback
-  installers download from. Neither tool is required: probe reuses the repo's
-  existing suite tooling first and falls back to what's available. Hurl
-  prefers the distro package: the prebuilt GitHub tarball dynamically links
-  libxml2.so.2, which newer distros no longer ship (e.g. Ubuntu 26.04 moved
-  to libxml2.so.16). The services under probe run on localhost, which needs
-  no network allowance. POSIX-only: sbx runs these commands with /bin/sh (dash).
-
-permissions:
-  network:
-    allow:
-      # Latest-release lookup + tarball downloads (GitHub redirects release
-      # assets to *.githubusercontent.com object hosts)
-      - 'api.github.com:443'
-      - 'github.com:443'
-      - 'objects.githubusercontent.com:443'
-      - 'release-assets.githubusercontent.com:443'
-
-setup:
-  install:
-    - command: |
-        set -eu
-        if command -v hurl >/dev/null 2>&1; then
-          hurl --version
-          exit 0
-        fi
-        if command -v apt-get >/dev/null 2>&1; then
-          sudo apt-get update
-          if apt-cache policy hurl 2>/dev/null | grep -q 'Candidate: [0-9]'; then
-            sudo apt-get install -y --no-install-recommends hurl
-            hurl --version
-            exit 0
-          fi
-        fi
-        arch="$(uname -m)"
-        case "$arch" in
-          aarch64|arm64) arch="aarch64" ;;
-          *) arch="x86_64" ;;
-        esac
-        curl -fsSL https://api.github.com/repos/Orange-OpenSource/hurl/releases/latest -o /tmp/hurl-release.json
-        ver="$(sed -n 's/.*"tag_name": *"\([^"]*\)".*/\1/p' /tmp/hurl-release.json | head -1)"
-        curl -fsSL "https://github.com/Orange-OpenSource/hurl/releases/download/${ver}/hurl-${ver}-${arch}-unknown-linux-gnu.tar.gz" -o /tmp/hurl.tgz
-        mkdir -p /tmp/hurl-extract
-        tar -xzf /tmp/hurl.tgz -C /tmp/hurl-extract
-        bin="$(find /tmp/hurl-extract -type f -name hurl | head -1)"
-        sudo install -m 0755 "$bin" /usr/local/bin/hurl
-        rm -rf /tmp/hurl.tgz /tmp/hurl-extract /tmp/hurl-release.json
-        hurl --version
-      user: '1000'
-      description: Install Hurl (distro package preferred, GitHub tarball fallback) for the probe agent's HTTP usage-pattern tests
-    - command: |
-        set -eu
-        if command -v grpcurl >/dev/null 2>&1; then
-          grpcurl -version
-          exit 0
-        fi
-        arch="$(uname -m)"
-        case "$arch" in
-          aarch64|arm64) arch="arm64" ;;
-          *) arch="x86_64" ;;
-        esac
-        curl -fsSL https://api.github.com/repos/fullstorydev/grpcurl/releases/latest -o /tmp/grpcurl-release.json
-        ver="$(sed -n 's/.*"tag_name": *"v\([^"]*\)".*/\1/p' /tmp/grpcurl-release.json | head -1)"
-        curl -fsSL "https://github.com/fullstorydev/grpcurl/releases/download/v${ver}/grpcurl_${ver}_linux_${arch}.tar.gz" -o /tmp/grpcurl.tgz
-        mkdir -p /tmp/grpcurl-extract
-        tar -xzf /tmp/grpcurl.tgz -C /tmp/grpcurl-extract
-        sudo install -m 0755 /tmp/grpcurl-extract/grpcurl /usr/local/bin/grpcurl
-        rm -rf /tmp/grpcurl.tgz /tmp/grpcurl-extract /tmp/grpcurl-release.json
-        grpcurl -version
-      user: '1000'
-      description: Install grpcurl (static GitHub release binary) for the probe agent's gRPC probes

assets/agents/probe/tools.sh

@@ -1,78 +0,0 @@
-#!/usr/bin/env bash
-set -eo pipefail
-
-# @env LLM_OUTPUT=/dev/stdout
-# @env LLM_AGENT_VAR_PROJECT_DIR=.
-# @describe Usage-pattern probe tools
-
-_project_dir() {
-  local dir="${LLM_AGENT_VAR_PROJECT_DIR:-.}"
-  (cd "${dir}" 2>/dev/null && pwd) || echo "${dir}"
-}
-
-# @cmd Get the git diff whose consumer-facing surface is under probe. Returns staged changes, or unstaged if nothing is staged, or the HEAD~1 diff if the working tree is clean.
-# @option --base Optional base ref to diff against (e.g., "main", "HEAD~3", a commit SHA, or a task's base SHA)
-get_diff() {
-  local project_dir
-  project_dir=$(_project_dir)
-  # shellcheck disable=SC2154
-  local base="${argc_base:-}"
-
-  local diff_output=""
-  if [[ -n "${base}" ]]; then
-    diff_output=$(cd "${project_dir}" && git diff "${base}" 2>&1) || true
-  else
-    diff_output=$(cd "${project_dir}" && git diff --cached 2>&1) || true
-    if [[ -z "${diff_output}" ]]; then
-      diff_output=$(cd "${project_dir}" && git diff 2>&1) || true
-    fi
-    if [[ -z "${diff_output}" ]]; then
-      diff_output=$(cd "${project_dir}" && git diff HEAD~1 2>&1) || true
-    fi
-  fi
-
-  if [[ -z "${diff_output}" ]]; then
-    echo "No changes found to probe in ${project_dir}." >> "$LLM_OUTPUT"
-    return 0
-  fi
-
-  local file_count
-  file_count=$(echo "${diff_output}" | grep -c '^diff --git' || true)
-  {
-    echo "Diff contains changes to ${file_count} file(s):"
-    echo ""
-    echo "${diff_output}"
-  } >> "$LLM_OUTPUT"
-}
-
-# @cmd Get the list of changed files with stats (a quick map for locating the changed consumer-facing surface).
-# @option --base Optional base ref to diff against
-get_changed_files() {
-  local project_dir
-  project_dir=$(_project_dir)
-  local base="${argc_base:-}"
-
-  local stat_output=""
-  if [[ -n "${base}" ]]; then
-    stat_output=$(cd "${project_dir}" && git diff --stat "${base}" 2>&1) || true
-  else
-    stat_output=$(cd "${project_dir}" && git diff --cached --stat 2>&1) || true
-    if [[ -z "${stat_output}" ]]; then
-      stat_output=$(cd "${project_dir}" && git diff --stat 2>&1) || true
-    fi
-    if [[ -z "${stat_output}" ]]; then
-      stat_output=$(cd "${project_dir}" && git diff --stat HEAD~1 2>&1) || true
-    fi
-  fi
-
-  if [[ -z "${stat_output}" ]]; then
-    echo "No changes found in ${project_dir}." >> "$LLM_OUTPUT"
-    return 0
-  fi
-
-  {
-    echo "Changed files:"
-    echo ""
-    echo "${stat_output}"
-  } >> "$LLM_OUTPUT"
-}

assets/agents/review-gauntlet/README.md

@@ -1,219 +0,0 @@
-# Review Gauntlet
-
-A graph-based post-implementation review gate — **"the done gate"**. An
-orchestrator that must not claim *done* without green reviews spawns this agent
-once instead of judging trigger rules and parsing verdict sentinels itself. The
-graph structure makes skipping a lane or misreading a verdict impossible:
-trigger signals are computed by a script, lanes run as isolated parallel
-sub-agents, and the final verdict is a deterministic regex gate — an LLM never
-gets the chance to rationalize past it.
-
-```mermaid
-flowchart TD
-    parse["parse<br/>(llm: extract request facts)"] --> signals["signals<br/>(script: deterministic diff facts)"]
-    parse -. "fallback" .-> pfault["parse_fault<br/>(script: PIPELINE-FAULT marker)"]
-    pfault --> gate
-    signals --> select["select_lanes<br/>(llm: ADDITIVE-only judgment)"]
-    select --> build["build_items<br/>(script: rules floor ∪ additions;<br/>forced lanes override exactly)"]
-    select -. "fallback" .-> dlanes["default_lanes<br/>(script: deterministic degraded<br/>selection — wider, never narrower)"]
-    dlanes --> build
-    build --> mcr["map: code-review"] & madv["map: adversary"] & msec["map: security"] & mpb["map: probe"]
-    mcr -->|"over: 0-or-1 items"| rcr[["code-reviewer<br/>(max_attempts: 2)"]]
-    madv --> radv[["adversary<br/>(max_attempts: 2)"]]
-    msec --> rsec[["security-reviewer<br/>(max_attempts: 2)"]]
-    mpb --> rpb[["probe<br/>(max_attempts: 2)"]]
-    rcr -. "fallback" .-> lfault["lane_fault<br/>(script: PIPELINE-FAULT lane result,<br/>collected by the map)"]
-    radv -. "fallback" .-> lfault
-    rsec -. "fallback" .-> lfault
-    rpb -. "fallback" .-> lfault
-    mcr & madv & msec & mpb --> rgate["retry_gate<br/>(script: fault-only re-run gate;<br/>stash + restore, ≤3 attempts,<br/>wall-clock budget)"]
-    rgate -. "_next: retry faulted lanes" .-> build
-    rgate --> gate["verdict_gate<br/>(script: sentinel regex — deterministic)"]
-    gate --> done(["GAUNTLET: PASS | BLOCKED<br/>(+ GAUNTLET_REVIEW_INCOMPLETE: … when any lane or the pipeline was incomplete)"])
-```
-
-## Why a graph
-
-The four independent review lanes existed before this agent — as **prompt
-discipline** inside the calling orchestrator: "spawn code-reviewer when the
-change is broad", "🔴 always blocks", "INCONCLUSIVE is never PASS". Prompt
-discipline degrades under context pressure: a lane gets skipped, a verdict
-line gets paraphrased, a missing report reads as "nothing to report". Here
-those rules are *structure*:
-
-- **Lane selection floor is deterministic** (`build_items.py`): code-review
-  always runs; adversary runs when a spec/plan is present; security runs on
-  attack-surface signals (auth/deps/exec paths or diff content) or hardened
-  posture; probe runs when consumer-facing surface changed *and* a local-run
-  recipe exists. The `select_lanes` LLM can only **widen** the set — a false
-  flag never removes a rule-selected lane. `forced_lanes` from the caller
-  override everything exactly.
-- **Conditional lanes without dynamic routing**: each lane is a `map` node
-  over a 0-or-1-item list — an empty list means the map runs zero branches
-  (map-over-nothing), which *is* the skip mechanism. All four maps join at
-  the retry gate on equal-length paths; it falls through to the verdict
-  gate, or routes back to `build_items` for faulted lanes only.
-- **The verdict is a regex, not an opinion** (`verdict_gate.py`): a missing
-  sentinel is a lane FAILURE, never a pass; the critical count from the
-  code-review report's summary line (raw 🔴 count if absent) blocks
-  regardless of its verdict line; a code-review lane whose own verdict line
-  records a pipeline fault blocks (a degraded review is never a pass); the
-  adversary's own degraded-run header (the `Criteria: …` line directly under
-  its sentinel recording a pipeline fault, died criterion checks, or its
-  verdict script's crash stub) blocks as a pipeline fault,
-  not as a DIVERGES finding;
-  `NEEDS-HUMAN` without 🔴 passes but
-  is surfaced under *Human attention required*; probe `INCONCLUSIVE` blocks
-  with an environment note — it is never treated as PASS or FAIL.
-- **Verdict independence is structural**: lanes run as isolated sub-agents
-  with no `teammates:` flag — no cross-lane messaging, by construction.
-- **Failure fails closed, structurally** (`fallback:` routes + `PIPELINE-FAULT`
-  markers): every LLM node and lane retries once (`max_attempts: 2`), then a
-  fallback fires instead of killing the graph — and every fallback degrades
-  toward BLOCKED, never toward a pass. A dead lane becomes a `PIPELINE-FAULT:`
-  lane result (`lane_fault.py`) that the gate reports as BLOCKED *naming the
-  lane* — distinct from SKIPPED (not selected). A dead `parse` records a fault
-  and jumps straight to the gate (`parse_fault.py`). A dead `select_lanes`
-  degrades to a deterministic selection (`default_lanes.py`): code-review +
-  adversary, plus probe on consumer surface *with a local-run recipe*, plus
-  security on auth/deps/exec
-  signals or hardened posture, unioned with caller-forced lanes — wider, never
-  narrower. A crashed `build_items` records a fault so an all-SKIPPED gate
-  still blocks. Fault detection is prefix-anchored — a real review that merely
-  *quotes* "PIPELINE-FAULT:" flows to the normal sentinel rules. And the
-  `GAUNTLET:` sentinel is always emitted: even a crashed gate prints
-  `GAUNTLET: BLOCKED`, never silence.
-
-## Fault-only re-runs
-
-`retry_gate.py` sits between the lane maps and the verdict gate and re-runs
-only lanes that **faulted** — a missing report (stood in for by a synthetic
-`PIPELINE-FAULT: <lane> lane produced no report` marker so it never renders as
-SKIPPED), a non-string report, the `lane_fault` marker, a sentinel-less
-report, or a nested graph's own degraded-run wording (the code-review verdict
-line / the adversary's header line directly under its sentinel). A real verdict
-(DIVERGES, FAIL, INCONCLUSIVE, NEEDS-HUMAN, …) is never re-run: the review's
-judgment stands. Each lane gets up to 3 attempts, all inside a wall-clock
-budget (`MAX_RETRY_ELAPSED_SECS`) sized to fit the graph timeout.
-
-- **Stash + restore**: every lane report that ran this pass is stashed in
-  `kept_results`; a re-run pass overwrites the untouched lanes' collected
-  results with `[]`, so their stashed reports are restored before the gate.
-  The verdict gate always sees each lane's *last* report.
-- **Retry never narrows selection**: lane selection is not re-run. A re-run
-  pass rebuilds items only for the retried lanes, and the stashed results
-  stand in for the rest.
-- **Exhaustion is recorded, not hidden**: a lane still faulted after its
-  attempts or the budget lands in `review_incomplete`, and its fault flows to
-  the verdict gate as-is.
-- **Crash guards append**: the `build_items.py` and `retry_gate.py` crash
-  guards append to an existing `signals_error` rather than overwrite it, and
-  `build_items.py` preserves the prior `lanes_summary`.
-
-A non-empty `GAUNTLET_REVIEW_INCOMPLETE:` line structurally implies
-`GAUNTLET: BLOCKED`: the verdict gate forces every lane named in
-`review_incomplete` to a BLOCKED row (`review incomplete after N attempt(s)`)
-and a matching blocker, so a restored earlier report can never turn an
-incomplete review into a pass — and malformed `review_incomplete` bookkeeping
-is itself recorded as a `pipeline` fault, never dropped.
-
-Whenever at least one lane (or the pipeline) could not complete, the first
-line reads `GAUNTLET: BLOCKED` followed immediately by
-`GAUNTLET_REVIEW_INCOMPLETE: <lane>[, <lane>]`. The names are the exhausted
-lanes from `review_incomplete`, plus the `pipeline` pseudo-lane whenever a
-pipeline-level `PIPELINE-FAULT:` fired — parse death, or a crash in the
-builder, the retry gate, the default-lanes fallback, or the verdict gate
-itself (the default-lanes fallback's crash still runs the widened lanes, so
-`pipeline` appears alongside real lane rows). The report gains a
-`## Review incomplete` section naming each exhausted lane with its
-attempt count; `PIPELINE-FAULT` lane rows carry ` ×N` when the lane was
-re-run (N > 1). The *named* entries are faults to re-run, never code
-findings; the line can accompany real findings from the other lanes, which
-still appear under `## Blockers` and must be fixed as usual.
-
-## Sentinels parsed
-
-| Lane | Sentinel | Blocks on |
-|------|----------|-----------|
-| code-reviewer | `**Verdict: MERGE-READY \| NEEDS-HUMAN**` | critical count from the report's summary line (raw 🔴 count if absent); missing sentinel; own verdict line records a pipeline fault |
-| adversary | `ADVERSARIAL_REVIEW: CONFORMS \| DIVERGES` | DIVERGES; own degraded-run header (pipeline fault, died criterion checks, or its verdict script's crash stub); missing sentinel |
-| security-reviewer | `SECURITY_REVIEW: PASS \| FAIL` | FAIL; missing sentinel |
-| probe | `USAGE_PROBE: PASS \| FAIL \| INCONCLUSIVE` | FAIL; INCONCLUSIVE (environment note); missing sentinel |
-
-## Spawning it
-
-```
-agent__spawn --agent review-gauntlet --prompt "Post-implementation review gate.
-
-Project: /abs/path/to/repo
-Diff: main...HEAD          (a git range, a ref, or 'worktree' for uncommitted changes)
-Rigor: production          Security posture: standard
-
-Plan / acceptance criteria:
-<paste the criteria the implementation must satisfy — enables the adversary lane>
-
-Local-run recipe / usage suites:
-<how to boot the service locally + where existing suites live — enables the probe lane>
-
-Forced lanes: (optional — e.g. 'adversary, probe' to run exactly those)" \
-  --variables {"verification_commands": "[\"cargo test --all\", \"cargo clippy -- -D warnings\"]"}
-```
-
-Verification commands are NOT part of the prompt. They are the declared
-`verification_commands` graph variable (default `'[]'`; a JSON array of shell
-commands as a string, since agent variables arrive as strings), also settable
-from the CLI:
-
-```sh
-coyote -a review-gauntlet --agent-variable project_dir /abs/path/to/repo \
-  --agent-variable verification_commands '["cargo test --all"]' "<prompt>"
-```
-
-The reply opens with `GAUNTLET: PASS` or `GAUNTLET: BLOCKED` (plus the
-`GAUNTLET_REVIEW_INCOMPLETE:` line when applicable), followed by a lane status
-table, the lane-selection reasons, blockers, attention items, and each lane's
-full report in a collapsible section. On BLOCKED with a
-`GAUNTLET_REVIEW_INCOMPLETE:` line: the named lanes never completed — this is an
-infrastructure fault, never a code finding. Fix any non-fault blockers listed
-under `## Blockers` first (the re-run retries the lane); if the line persists,
-escalate to the user with three options — retry the review again (a **fresh**
-gauntlet run), accept NEEDS-HUMAN and proceed without that lane (recorded in the
-report / PR body), or abort — never route it through your findings-handling
-rules. On BLOCKED without it: fix the findings per your own findings-handling
-rules, then spawn a **fresh** gauntlet run. On PASS with *Human attention
-required*: complete the work but carry those items into your final report
-verbatim.
-
-## Notes
-
-- The caller decides *whether* review is warranted at all (the gauntlet is for
-  non-trivial work — that's why code-review is unconditionally on); the
-  gauntlet decides *which* of the other lanes apply and what the verdicts mean.
-- Lane sub-agents get generous finite per-attempt timeouts (see the
-  `timeout:` on each `run_*` node) and one retry (`max_attempts: 2`) inside
-  the lane, then up to 3 attempts of the whole lane from `retry_gate.py` while
-  the wall-clock budget (`MAX_RETRY_ELAPSED_SECS`) allows; `settings.timeout`
-  is derived from that envelope in graph.yaml's comment. A lane that still
-  dies or times out falls back to the `lane_fault` marker — BLOCKED naming the
-  lane and `GAUNTLET_REVIEW_INCOMPLETE`, never a silent pass.
-- The `verification_commands` variable is forwarded to the adversary lane as a
-  structured `inputs:` passthrough on `run_adversary` (a lone `{{…}}` template
-  lands the raw value in the child's state) — never through the lane prompt
-  and never extracted by `parse`. The adversary's `run_checks` stage executes
-  those commands with a shell, which makes the declaration a trust boundary:
-  the prompt also carries plan text pasted from the repo under review, so
-  commands must never be inferred from it, and the engine merges only the keys
-  `parse`'s `output_schema.properties` declares, so an extra
-  `verification_commands` key emitted by the LLM is dropped before it reaches
-  state.
-  Undeclared stays undeclared
-  (`'[]'` ⇒ "none declared"); a declaration that is not a JSON array of
-  strings executes nothing and records a `PIPELINE-FAULT`, which the
-  adversary lane reports as DIVERGES and the gate as BLOCKED.
-- Signals failures degrade gracefully: if git can't compute the diff, lane
-  selection falls back to caller context + forced lanes, and the report notes
-  it. The auth-path regex deliberately over-fires (`auth(?!or)` matches
-  auth/authn/authz/oauth but not "author") — the safe direction, since signals
-  only ever ADD the security lane.
-- Requires the `code-reviewer`, `adversary`, `security-reviewer`, and `probe`
-  agents to be installed (they ship with Coyote).

assets/agents/review-gauntlet/graph.yaml

@@ -1,452 +0,0 @@
-name: review-gauntlet
-description: |
-  Graph-based post-implementation review gate — "the done gate". Given a diff
-  spec and the work's context (plan/acceptance criteria, rigor, security
-  posture), it deterministically computes diff signals, selects the applicable
-  independent review lanes — code-reviewer (always), adversary (when a
-  spec/plan exists), security-reviewer (attack-surface signals), probe
-  (consumer-facing surface with a local-run recipe) — runs the selected lanes
-  IN PARALLEL as isolated sub-agents, and machine-parses their verdict
-  sentinels into one deterministic verdict: GAUNTLET: PASS or
-  GAUNTLET: BLOCKED. An orchestrator that must not claim "done" without green
-  reviews spawns this once instead of judging trigger rules and parsing
-  verdicts itself — the graph structure makes skipping a lane or misreading a
-  verdict impossible. Invariants: lane selection can only be WIDENED by LLM
-  judgment, never narrowed (deterministic rules are the floor); a missing
-  verdict sentinel is a lane failure, never a pass; probe INCONCLUSIVE blocks
-  with an environment note (it is never PASS or FAIL); reviewer lanes run
-  verdict-independent — no cross-lane messaging.
-
-version: '1.0'
-
-# The limit is consulted by the SPAWNER against the child's absolute depth
-# (root = 0). Deepest documented chain: architect(0) → sisyphus(1) →
-# review-gauntlet(2) → code-reviewer(3) →
-# {domain-reviewer(4) → file-reviewer(5) | finding-verifier(4)}.
-# This agent spawns depth-3 children; 4 = one level of headroom.
-max_agent_depth: 4
-max_concurrent_agents: 12
-
-variables:
-  - name: project_dir
-    description: Repository the change lives in; signals and every review lane run against it.
-    default: '.'
-  - name: verification_commands
-    description: |
-      JSON array of shell commands the CALLER declares for the deterministic
-      run_checks stage — e.g. '["cargo test --all"]'. Never inferred from the
-      prompt; empty array = none declared.
-    default: '[]'
-
-settings:
-  max_loop_iterations: 10
-  log_state_snapshots: true
-  # A faulted lane can be re-run by retry_gate for up to 3 passes, and each
-  # pass's agent node retries up to max_attempts = 2 with a fresh per-attempt
-  # budget (src/graph/agent.rs retry_transient/bounded_attempt):
-  # 3 passes × 2 attempts × 11400 (max lane timeout) = 68400, + 1200 margin
-  # for the script stages (signals/select/build/retry gate/verdict gate)
-  # = 69600; the parse and select_lanes llm nodes carry no `timeout:` and
-  # are bounded by max_iterations.
-  timeout: 69600
-
-initial_state:
-  retry_notes: []
-  diff_spec: worktree
-  plan_context: ''
-  rigor: production
-  security_posture: standard
-  probe_context: ''
-  extra_context: ''
-  forced_lanes: []
-  changed_files: []
-  file_count: 0
-  signals_summary: ''
-  signals_error: ''
-  touches_auth: false
-  touches_deps: false
-  touches_exec: false
-  touches_proto: false
-  touches_migrations: false
-  consumer_surface: false
-  docs_only: false
-  add_code_review: false
-  add_adversary: false
-  add_security: false
-  add_probe: false
-  lane_reasons: ''
-  parse_failure: ''
-  select_lanes_failure: ''
-  lanes_degraded: ''
-  code_review_items: []
-  adversary_items: []
-  security_items: []
-  probe_items: []
-  code_review_results: []
-  adversary_results: []
-  security_results: []
-  probe_results: []
-  lane_attempts: {}
-  kept_results: {}
-  retry_lanes: []
-  review_incomplete: []
-  gauntlet_started_at: 0
-  lanes_summary: ''
-  gauntlet_verdict: ''
-  gauntlet_report: ''
-  gauntlet_incomplete_line: ''
-
-start: parse
-
-nodes:
-  parse:
-    id: parse
-    type: llm
-    description: Extract the review request's facts from the spawn prompt. Extraction only — no judging, no lane selection.
-    instructions: |
-      You extract the facts of a review request into structured fields.
-      EXTRACTION ONLY — do not decide which review lanes should run.
-
-      - `diff_spec`: the git diff specification the caller named — a ref
-        range ("main...HEAD", "HEAD~3..HEAD"), a single ref, or the literal
-        "worktree" for uncommitted changes against HEAD. When the caller
-        did not name one, use "worktree".
-      - `project_dir_in`: the repository directory the caller named as holding
-        the change (absolute path preferred); empty string when the caller
-        named none.
-      - `plan_context`: the plan / spec / acceptance-criteria text the
-        implementation must satisfy, copied through VERBATIM — never
-        summarize it and never replace pasted text with file paths or a
-        sentence saying it was included; the adversary lane fails closed on
-        whatever you drop. Empty string when the caller supplied none.
-      - `rigor`: poc | prototype | production. Default "production" when
-        not stated.
-      - `security_posture`: prototype | standard | hardened. Default
-        "standard" when not stated.
-      - `probe_context`: the local-run recipe and/or existing usage-suite
-        pointers for black-box probing (how to boot the service, where the
-        suites live). Empty string when the caller supplied none.
-      - `forced_lanes`: lanes the caller explicitly demanded (verbatim
-        names). Empty array = automatic selection.
-      - `extra_context`: any remaining caller context reviewers should see,
-        condensed.
-    prompt: |
-      Extract the review-request facts from this request:
-
-      {{initial_prompt}}
-    tools: []
-    output_schema:
-      type: object
-      properties:
-        diff_spec:
-          type: string
-        plan_context:
-          type: string
-        rigor:
-          type: string
-        security_posture:
-          type: string
-        probe_context:
-          type: string
-        forced_lanes:
-          type: array
-          items:
-            type: string
-        extra_context:
-          type: string
-        project_dir_in:
-          type: string
-      required: [diff_spec, plan_context, rigor, security_posture, probe_context, forced_lanes, extra_context, project_dir_in]
-    max_iterations: 3
-    max_attempts: 2
-    state_updates:
-      parse_failure: '{{output}}'
-    fallback: parse_fault
-    next: signals
-
-  parse_fault:
-    id: parse_fault
-    type: script
-    description: Fail-closed marker for a dead parse stage (reached only via parse's fallback) — records a PIPELINE-FAULT in signals_error and jumps straight to the verdict gate, which blocks on it. Lane item lists stay their initial [] so every lane records SKIPPED.
-    script: scripts/parse_fault.py
-    timeout: 30
-    next: verdict_gate
-
-  signals:
-    id: signals
-    type: script
-    description: Deterministic diff signals — file list, attack-surface and consumer-surface indicators. Pure git; no LLM judgment.
-    script: scripts/signals.py
-    timeout: 120
-    next: select_lanes
-
-  select_lanes:
-    id: select_lanes
-    type: llm
-    description: Additive-only lane judgment on top of the deterministic rules. It can WIDEN the gauntlet, never narrow it.
-    instructions: |
-      You look at a change's deterministic diff signals and decide whether any
-      review lane the hard rules might have missed should ALSO run. You can
-      only ADD lanes — the deterministic floor (enforced downstream, not by
-      you) is: code-review always runs; adversary runs when a plan/spec is
-      present; security runs on attack-surface signals or hardened posture;
-      probe runs when consumer-facing surface changed and a local-run recipe
-      exists. Setting a flag to false NEVER removes a lane the rules selected.
-
-      Reasons to add:
-      - `add_security`: the diff handles external/untrusted input, touches
-        crypto/secrets handling, or changes trust boundaries in ways the
-        path-based signals missed.
-      - `add_adversary`: the request references behavior it must preserve or
-        criteria scattered in prose that amount to a spec, even without a
-        formal plan.
-      - `add_probe`: the change alters observable API/CLI behavior even
-        though the path signals missed it (only useful when a local-run
-        recipe exists — the builder skips it otherwise, noting why).
-      - `add_code_review`: always selected by the rules; flag exists only
-        for forced-lane configurations.
-
-      Put one line per added lane into `lane_reasons`. When nothing needs
-      adding, all flags false and empty reasons is the correct answer.
-    prompt: |
-      Change signals (deterministic):
-      - diff spec: {{diff_spec}}
-      - files changed: {{file_count}}
-      - changed files (first 200): {{changed_files}}
-      - touches auth paths/content: {{touches_auth}}
-      - touches dependency manifests: {{touches_deps}}
-      - adds exec/shell/subprocess calls: {{touches_exec}}
-      - touches protobuf/contracts: {{touches_proto}}
-      - touches migrations: {{touches_migrations}}
-      - consumer-facing surface paths: {{consumer_surface}}
-      - docs-only diff: {{docs_only}}
-      - {{signals_summary}}
-      {{signals_error}}
-
-      Caller context:
-      - rigor: {{rigor}}; security posture: {{security_posture}}
-      - plan/spec present: {{plan_context}}
-      - probe recipe present: {{probe_context}}
-      - extra: {{extra_context}}
-    tools: []
-    output_schema:
-      type: object
-      properties:
-        add_code_review:
-          type: boolean
-        add_adversary:
-          type: boolean
-        add_security:
-          type: boolean
-        add_probe:
-          type: boolean
-        lane_reasons:
-          type: string
-      required: [add_code_review, add_adversary, add_security, add_probe, lane_reasons]
-    max_iterations: 3
-    max_attempts: 2
-    state_updates:
-      select_lanes_failure: '{{output}}'
-    fallback: default_lanes
-    next: build_items
-
-  default_lanes:
-    id: default_lanes
-    type: script
-    description: Deterministic lane-selection fallback (reached only via select_lanes' fallback) — when the additive LLM judgment dies, forces code-review + adversary, plus probe when consumer_surface AND a probe_context (local-run recipe) is present, plus security on attack-surface signals (auth/deps/exec) or hardened posture, unioned with any caller-forced lanes. Selection degrades WIDER, never narrower; the degradation note flows into lanes_summary via build_items.
-    script: scripts/default_lanes.py
-    timeout: 30
-    next: build_items
-
-  build_items:
-    id: build_items
-    type: script
-    description: Deterministic lane builder — hard rules are the floor, LLM flags may only add, forced lanes override exactly. Emits one 0-or-1-item list per lane; an empty list skips that lane's map. On a re-run pass (retry_lanes non-empty) it skips selection and emits items only for those lanes, each carrying its attempt number.
-    script: scripts/build_items.py
-    timeout: 30
-    next: [map_code_review, map_adversary, map_security, map_probe]
-
-  map_code_review:
-    id: map_code_review
-    type: map
-    over: '{{code_review_items}}'
-    as: lane_ctx
-    branch: run_code_review
-    output_key: lane_out
-    collect_into: code_review_results
-    max_concurrency: 1
-    next: retry_gate
-
-  map_adversary:
-    id: map_adversary
-    type: map
-    over: '{{adversary_items}}'
-    as: lane_ctx
-    branch: run_adversary
-    output_key: lane_out
-    collect_into: adversary_results
-    max_concurrency: 1
-    next: retry_gate
-
-  map_security:
-    id: map_security
-    type: map
-    over: '{{security_items}}'
-    as: lane_ctx
-    branch: run_security
-    output_key: lane_out
-    collect_into: security_results
-    max_concurrency: 1
-    next: retry_gate
-
-  map_probe:
-    id: map_probe
-    type: map
-    over: '{{probe_items}}'
-    as: lane_ctx
-    branch: run_probe
-    output_key: lane_out
-    collect_into: probe_results
-    max_concurrency: 1
-    next: retry_gate
-
-  run_code_review:
-    id: run_code_review
-    type: agent
-    description: Independent code-quality review lane.
-    agent: code-reviewer
-    # Exceeds the code-reviewer graph's own settings.timeout (10800) by 600 so
-    # the child's graph timeout, not this lane timeout, is the binding bound.
-    # NOTE: the child's own internal retry envelope (its nodes' max_attempts ×
-    # timeouts) is not derived here — deliberately out of scope for this
-    # change; tracked as a follow-up.
-    timeout: 11400
-    prompt: |
-      Review the code changes in {{project_dir}} (diff: {{diff_spec}}) as an
-      independent post-implementation review.
-
-      Quality bar: rigor={{rigor}}.
-
-      Plan / acceptance-criteria context (may be empty):
-      {{plan_context}}
-
-      {{extra_context}}
-
-      Close your report with your Review Verdict line.
-    max_attempts: 2
-    state_updates:
-      lane_out: '{{output}}'
-    fallback: lane_fault
-
-  run_adversary:
-    id: run_adversary
-    type: agent
-    description: Plan-conformance review lane.
-    agent: adversary
-    # Exceeds the adversary graph's own settings.timeout (9000) by 600 so the
-    # child's graph timeout, not this lane timeout, is the binding bound.
-    # NOTE: the child's own internal retry envelope (its nodes' max_attempts ×
-    # timeouts) is not derived here — deliberately out of scope for this
-    # change; tracked as a follow-up.
-    timeout: 9600
-    inputs:
-      verification_commands: '{{verification_commands}}'
-    prompt: |
-      Adversarial plan-conformance review in {{project_dir}}.
-
-      The implementation to check: diff {{diff_spec}}.
-
-      The spec / plan / acceptance criteria it must satisfy:
-      {{plan_context}}
-
-      Verification commands arrive as a structured input (the verification_commands variable), not in this prompt.
-
-      {{extra_context}}
-
-      Return your ADVERSARIAL_REVIEW verdict.
-    max_attempts: 2
-    state_updates:
-      lane_out: '{{output}}'
-    fallback: lane_fault
-
-  run_security:
-    id: run_security
-    type: agent
-    description: Security review lane.
-    agent: security-reviewer
-    timeout: 7200
-    prompt: |
-      Security review of the code changes in {{project_dir}} (diff: {{diff_spec}}).
-
-      Security posture: {{security_posture}}.
-
-      {{extra_context}}
-
-      Return your SECURITY_REVIEW verdict.
-    max_attempts: 2
-    state_updates:
-      lane_out: '{{output}}'
-    fallback: lane_fault
-
-  run_probe:
-    id: run_probe
-    type: agent
-    description: Black-box usage-pattern verification lane.
-    agent: probe
-    timeout: 7200
-    prompt: |
-      Usage-pattern verification (black-box probe) of the changes in
-      {{project_dir}} (diff: {{diff_spec}}).
-
-      Local-run recipe / existing usage suites:
-      {{probe_context}}
-
-      Plan / acceptance-criteria context:
-      {{plan_context}}
-
-      The workspace may contain test files from an aborted earlier attempt of
-      this lane; reconcile rather than duplicate.
-
-      Shared-stack rule: wrap any stack boot/teardown in
-      `flock "$HOME/.cache/coyote/review-stack.lock" <command>` (the adversary's
-      verification stage holds the same lock), and NEVER remove or stop containers
-      you did not create this run — a held port means wait, re-port, or INCONCLUSIVE.
-
-      Derive expected behaviors from the plan/contract BEFORE reading
-      implementation code, run existing suites first, then author spec-first
-      tests for the uncovered delta. Return your USAGE_PROBE verdict.
-    max_attempts: 2
-    state_updates:
-      lane_out: '{{output}}'
-    fallback: lane_fault
-
-  lane_fault:
-    id: lane_fault
-    type: script
-    description: Fail-closed lane fault marker (reached only via the run_* lanes' fallback routes; shared across the four map branches). Normalizes the engine's "Agent node failed" text in lane_out into a PIPELINE-FAULT lane result the map collects; verdict_gate turns it into BLOCKED — a degraded lane is never a pass.
-    script: scripts/lane_fault.py
-    timeout: 30
-
-  retry_gate:
-    id: retry_gate
-    type: script
-    description: Deterministic fault-only re-run gate. Stashes every lane report that ran this pass, restores reports a re-run pass overwrote with [] (a lane not being re-run maps over nothing), classifies each lane that ran as completed / faulted / skipped, counts attempts, and routes back into build_items for faulted lanes that still have attempts left inside the wall-clock budget; otherwise it records them in review_incomplete and falls through to verdict_gate. A real verdict is never re-run, and a gate crash never retries — it records a PIPELINE-FAULT and falls through.
-    script: scripts/retry_gate.py
-    timeout: 30
-    next: verdict_gate
-
-  verdict_gate:
-    id: verdict_gate
-    type: script
-    description: Deterministic sentinel parser and gate. A missing sentinel is a lane failure, never a pass; probe INCONCLUSIVE blocks with an environment note; the code-review critical count is read from render.py's summary line (raw 🔴 count if absent) and blocks regardless of the lane's own verdict line; a code-review verdict line that records the nested graph's own pipeline fault blocks as a degraded lane. Lanes retry_gate gave up on, and any pipeline-level fault, are named on a GAUNTLET_REVIEW_INCOMPLETE machine line so a caller can tell an incomplete review from a failed one.
-    script: scripts/verdict_gate.py
-    timeout: 60
-    next: done
-
-  done:
-    id: done
-    type: end
-    output: |
-      GAUNTLET: {{gauntlet_verdict}}{{gauntlet_incomplete_line}}
-
-      {{gauntlet_report}}

assets/agents/review-gauntlet/scripts/build_items.py

@@ -1,196 +0,0 @@
-#!/usr/bin/env python3
-"""Deterministic lane builder for the review gauntlet.
-
-Selection = hard rules (the floor) ∪ LLM additions; forced lanes override
-everything exactly. Emits one 0-or-1-item list per lane: an empty list makes
-that lane's map node run zero branches (map-over-nothing), which IS the
-skip mechanism — no dynamic routing anywhere.
-
-The LLM's add_* flags can only ADD lanes. A flag that is false never
-removes a lane the hard rules selected.
-
-A re-run pass (retry_gate emitted `retry_lanes`) skips selection: only the
-named lanes get an item, stamped with their attempt number, and every other
-lane maps over nothing — retry_gate restores their earlier reports.
-
-Fail-closed: a builder crash emits all four lists empty plus a
-PIPELINE-FAULT in signals_error — verdict_gate blocks on it and the crash
-never kills the graph.
-"""
-
-import json
-import os
-import time
-
-# Keep in sync with default_lanes.ALIASES — a caller-forced lane must
-# canonicalize the same way on the degraded path as it does here.
-ALIASES = {
-    "code-review": "code-review",
-    "code_review": "code-review",
-    "code-reviewer": "code-review",
-    "adversary": "adversary",
-    "adversarial": "adversary",
-    "adversarial-review": "adversary",
-    "security": "security",
-    "security-review": "security",
-    "security-reviewer": "security",
-    "probe": "probe",
-    "usage": "probe",
-    "usage-pattern": "probe",
-    "usage-pattern-testing": "probe",
-}
-
-# Keep in sync with retry_gate.LANES
-LANE_KEYS = {
-    "code-review": "code_review_items",
-    "adversary": "adversary_items",
-    "security": "security_items",
-    "probe": "probe_items",
-}
-
-# Filled by main() so the crash guard can append to an upstream fault
-# instead of overwriting it, and keep the first pass's lanes_summary.
-crash_context = {"signals_error": "", "lanes_summary": ""}
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def main():
-    state = load_state()
-    prior = state.get("signals_error")
-    crash_context["signals_error"] = prior if isinstance(prior, str) else ""
-    # retry_gate's wall-clock budget is measured from this stamp; signals.py
-    # is the normal stamper, this is the defensive fallback.
-    stamp = {} if state.get("gauntlet_started_at") else {"gauntlet_started_at": time.time()}
-
-    def text(key):
-        v = state.get(key)
-        return v.strip() if isinstance(v, str) else ""
-
-    crash_context["lanes_summary"] = text("lanes_summary")
-    retry_lanes = [lane for lane in (state.get("retry_lanes") or []) if lane in LANE_KEYS]
-    if retry_lanes:
-        attempts = state.get("lane_attempts") or {}
-        retried = [(lane, int(attempts.get(lane) or 0) + 1) for lane in retry_lanes]
-        note = "- retried: [" + ", ".join(f"{lane} (attempt {n})" for lane, n in retried) + "]"
-        summary = text("lanes_summary")
-        print(
-            json.dumps(
-                {
-                    **{key: [] for key in LANE_KEYS.values()},
-                    **{
-                        LANE_KEYS[lane]: [{"lane": lane, "attempt": n}] for lane, n in retried
-                    },
-                    "lanes_summary": f"{summary}\n{note}" if summary else note,
-                    "retry_lanes": [],
-                    **stamp,
-                }
-            )
-        )
-        return
-
-    forced_raw = state.get("forced_lanes") or []
-    forced, unknown = [], []
-    for lane in forced_raw:
-        canon = ALIASES.get(str(lane).strip().lower())
-        (forced.append(canon) if canon else unknown.append(str(lane)))
-
-    reasons = []
-    if forced:
-        lanes = set(forced)
-        reasons.append(f"forced lanes honored exactly: {sorted(lanes)}")
-    else:
-        lanes = {"code-review"}
-        reasons.append(
-            "code-review: always on — the gauntlet is only spawned for non-trivial work"
-        )
-        if text("plan_context"):
-            lanes.add("adversary")
-            reasons.append("adversary: a spec/plan/acceptance-criteria context is present")
-        if (
-            state.get("touches_auth")
-            or state.get("touches_deps")
-            or state.get("touches_exec")
-            or state.get("security_posture") == "hardened"
-        ):
-            lanes.add("security")
-            reasons.append(
-                "security: attack-surface signals (auth/deps/exec) or hardened posture"
-            )
-        if state.get("consumer_surface") and text("probe_context"):
-            lanes.add("probe")
-            reasons.append(
-                "probe: consumer-facing surface changed and a local-run recipe/suite pointer exists"
-            )
-
-        # LLM judgment is additive-only.
-        llm_why = text("lane_reasons")[:300]
-        for flag, lane in (
-            ("add_code_review", "code-review"),
-            ("add_adversary", "adversary"),
-            ("add_security", "security"),
-            ("add_probe", "probe"),
-        ):
-            if state.get(flag) and lane not in lanes:
-                if lane == "probe" and not text("probe_context"):
-                    reasons.append(
-                        "probe: requested by lane judgment but skipped — no local-run "
-                        "recipe/suite pointer (a probe without one is guaranteed INCONCLUSIVE)"
-                    )
-                    continue
-                if lane == "adversary" and not text("plan_context"):
-                    reasons.append(
-                        "adversary: requested by lane judgment but skipped — no spec/plan "
-                        "to check conformance against"
-                    )
-                    continue
-                lanes.add(lane)
-                reasons.append(f"{lane}: added by lane-selection judgment — {llm_why}")
-
-    if unknown:
-        reasons.append(f"ignored unknown forced lane name(s): {unknown}")
-
-    # A degraded lane selection (default_lanes fallback) must survive into the
-    # final report; lanes_summary is the only channel this script doesn't
-    # overwrite silently.
-    degraded = text("lanes_degraded")
-    if degraded:
-        reasons.insert(0, degraded)
-
-    print(
-        json.dumps(
-            {
-                "code_review_items": [{"lane": "code-review"}] if "code-review" in lanes else [],
-                "adversary_items": [{"lane": "adversary"}] if "adversary" in lanes else [],
-                "security_items": [{"lane": "security"}] if "security" in lanes else [],
-                "probe_items": [{"lane": "probe"}] if "probe" in lanes else [],
-                "lanes_summary": "\n".join(f"- {r}" for r in reasons),
-                **stamp,
-            }
-        )
-    )
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — a builder crash must never kill the graph
-    fault = f"PIPELINE-FAULT: lane builder crashed — {e}; no lanes were run"
-    if crash_context["signals_error"]:
-        fault = f"{crash_context['signals_error']}; {fault}"
-    print(
-        json.dumps(
-            {
-                "code_review_items": [],
-                "adversary_items": [],
-                "security_items": [],
-                "probe_items": [],
-                "lanes_summary": crash_context["lanes_summary"],
-                "signals_error": fault,
-            }
-        )
-    )

assets/agents/review-gauntlet/scripts/default_lanes.py

@@ -1,105 +0,0 @@
-#!/usr/bin/env python3
-"""Deterministic lane-selection fallback for the review gauntlet.
-
-Reached ONLY via select_lanes' `fallback:` route, when the additive LLM
-judgment dies after retries. Emits `forced_lanes` — code-review + adversary,
-plus probe when the deterministic signals flagged a consumer-facing surface
-AND a local-run recipe exists (build_items gates probe the same way — a
-probe without a recipe is INCONCLUSIVE by construction),
-plus security when the attack-surface signals (auth/deps/exec) or a hardened
-posture demand it, unioned with any lanes the caller forced (canonicalized
-with the same aliases build_items uses) — which build_items honors exactly,
-so selection degrades WIDER, never narrower. The degradation note goes into
-`lanes_degraded`; build_items folds it into lanes_summary so the final
-report names the degradation.
-
-Fail-closed: if the fallback itself crashes it emits the widest safe
-selection (defaults ∪ security) plus a PIPELINE-FAULT in signals_error so
-verdict_gate blocks — a crashed fallback never narrows selection silently.
-"""
-
-import json
-import os
-
-MAX_DETAIL_CHARS = 500
-
-# Keep in sync with build_items.ALIASES — a caller-forced lane must
-# canonicalize the same way here as it would on the non-degraded path.
-ALIASES = {
-    "code-review": "code-review",
-    "code_review": "code-review",
-    "code-reviewer": "code-review",
-    "adversary": "adversary",
-    "adversarial": "adversary",
-    "adversarial-review": "adversary",
-    "security": "security",
-    "security-review": "security",
-    "security-reviewer": "security",
-    "probe": "probe",
-    "usage": "probe",
-    "usage-pattern": "probe",
-    "usage-pattern-testing": "probe",
-}
-
-# Stable emission order keeps the fallback deterministic.
-LANE_ORDER = ["code-review", "adversary", "security", "probe"]
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def main():
-    state = load_state()
-    lanes = {"code-review", "adversary"}
-    probe_context = state.get("probe_context")
-    if (
-        state.get("consumer_surface")
-        and isinstance(probe_context, str)
-        and probe_context.strip()
-    ):
-        lanes.add("probe")
-    # The deterministic security signals are already in state when this
-    # fallback runs; a degraded selection must never drop the security lane
-    # build_items' hard rules would have selected.
-    if (
-        state.get("touches_auth")
-        or state.get("touches_deps")
-        or state.get("touches_exec")
-        or state.get("security_posture") == "hardened"
-    ):
-        lanes.add("security")
-    # Caller-forced lanes survive degradation — union, never overwrite.
-    for lane in state.get("forced_lanes") or []:
-        if canon := ALIASES.get(str(lane).strip().lower()):
-            lanes.add(canon)
-    forced = [lane for lane in LANE_ORDER if lane in lanes]
-    raw = state.get("select_lanes_failure")
-    detail = raw.strip().replace("\n", " ") if isinstance(raw, str) else ""
-    if len(detail) > MAX_DETAIL_CHARS:
-        detail = detail[: MAX_DETAIL_CHARS - 1] + "…"
-    note = "lane selection degraded to deterministic defaults"
-    if detail:
-        note += f" — {detail}"
-    print(json.dumps({"forced_lanes": forced, "lanes_degraded": note}))
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — the fallback itself must never crash
-    print(
-        json.dumps(
-            {
-                "forced_lanes": ["code-review", "adversary", "security"],
-                "lanes_degraded": "lane selection degraded to deterministic "
-                f"defaults (fallback script error: {e})",
-                "signals_error": (
-                    f"PIPELINE-FAULT: lane-selection fallback crashed — {e}; "
-                    "lanes widened to defaults ∪ security"
-                ),
-            }
-        )
-    )

assets/agents/review-gauntlet/scripts/lane_fault.py

@@ -1,59 +0,0 @@
-#!/usr/bin/env python3
-"""Fail-closed lane fault marker for the review gauntlet.
-
-Reached ONLY via the run_* lane nodes' `fallback:` routes inside their map
-branches. Grounded in engine behavior: on agent-node failure the engine
-writes "Agent node failed: {e:#}" into `lane_out` via the node's
-state_updates BEFORE routing to the fallback, so the raw failure text is
-already in state. This node normalizes it into a
-"PIPELINE-FAULT: <lane> lane failed after retries — …" marker that the map
-collects as the lane result; verdict_gate turns any PIPELINE-FAULT lane
-result into BLOCKED — a degraded lane can never read as a pass.
-
-Lane identity comes from `lane_ctx` (the map item build_items emitted, which
-carries a `lane` field); a missing/malformed item degrades to "unknown".
-"""
-
-import json
-import os
-
-MAX_DETAIL_CHARS = 500
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def main():
-    state = load_state()
-    lane = "unknown"
-    lane_ctx = state.get("lane_ctx")
-    if isinstance(lane_ctx, dict):
-        name = lane_ctx.get("lane")
-        if isinstance(name, str) and name.strip():
-            lane = name.strip()
-    raw = state.get("lane_out")
-    detail = raw.strip().replace("\n", " ") if isinstance(raw, str) else ""
-    if len(detail) > MAX_DETAIL_CHARS:
-        detail = detail[: MAX_DETAIL_CHARS - 1] + "…"
-    print(
-        json.dumps(
-            {"lane_out": f"PIPELINE-FAULT: {lane} lane failed after retries — {detail}"}
-        )
-    )
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — the fault marker itself must never crash
-    print(
-        json.dumps(
-            {
-                "lane_out": "PIPELINE-FAULT: lane failed after retries — "
-                f"fault-marker script error: {e}"
-            }
-        )
-    )

assets/agents/review-gauntlet/scripts/parse_fault.py

@@ -1,52 +0,0 @@
-#!/usr/bin/env python3
-"""Fail-closed marker for a dead parse stage of the review gauntlet.
-
-Reached ONLY via parse's `fallback:` route. parse's state_updates wrote an
-"LLM node …failed: <chain>" string into `parse_failure` before routing here;
-this node records the failure as a PIPELINE-FAULT in `signals_error` and the
-graph jumps straight to the verdict gate. Every lane item list is still its
-initial [] so every lane records SKIPPED, and verdict_gate's signals_error
-rule makes the verdict BLOCKED — a gauntlet that could not even parse its
-request never reads as a pass.
-"""
-
-import json
-import os
-
-MAX_DETAIL_CHARS = 500
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def main():
-    state = load_state()
-    raw = state.get("parse_failure")
-    detail = raw.strip().replace("\n", " ") if isinstance(raw, str) else ""
-    if len(detail) > MAX_DETAIL_CHARS:
-        detail = detail[: MAX_DETAIL_CHARS - 1] + "…"
-    print(
-        json.dumps(
-            {
-                "signals_error": "PIPELINE-FAULT: parse failed — cannot run the "
-                f"gauntlet: {detail}"
-            }
-        )
-    )
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — the fault marker itself must never crash
-    print(
-        json.dumps(
-            {
-                "signals_error": "PIPELINE-FAULT: parse failed — cannot run the "
-                f"gauntlet: fault-marker script error: {e}"
-            }
-        )
-    )

assets/agents/review-gauntlet/scripts/retry_gate.py

@@ -1,227 +0,0 @@
-#!/usr/bin/env python3
-"""Deterministic fault-only re-run gate for the review gauntlet.
-
-Sits between the four lane maps and the verdict gate. Every lane map runs
-on every pass — a lane that is not being re-run maps over [] — so a re-run
-pass overwrites the untouched lanes' collected results with []. The gate's
-hard rules:
-
-  - every lane that ran this pass is stashed in kept_results, completed
-    and faulted alike, and a lane whose map ran nothing this pass gets
-    its stashed report restored — the verdict gate always sees each
-    lane's LAST report;
-  - a lane is FAULTED only when its report is missing (the map ran but
-    collected nothing — replaced by a synthetic PIPELINE-FAULT marker so
-    the verdict gate never reads it as SKIPPED), non-string, the
-    lane_fault.py marker, sentinel-less, or carries the nested graph's own
-    degraded-run wording; a real verdict (DIVERGES, FAIL, INCONCLUSIVE,
-    NEEDS-HUMAN, …) is never re-run — the review's judgment stands;
-  - a faulted lane is re-run only while it has attempts left AND the
-    gauntlet is inside its wall-clock budget; otherwise it is recorded in
-    review_incomplete and its fault flows to the verdict gate as-is;
-  - malformed review_incomplete bookkeeping (not a list, or non-str
-    entries) keeps its str entries and records a PIPELINE-FAULT in
-    signals_error — never silently dropped, never split into lane names;
-  - the gate itself must never retry by accident: any internal error
-    records a PIPELINE-FAULT in signals_error and falls through to the
-    verdict gate, which blocks on it.
-"""
-
-import json
-import os
-import re
-import sys
-import time
-
-# 69600 (graph timeout) − 2 × 11400 (largest lane envelope) − 1200 (script stages)
-# = 45600; 600 s of slack below that.
-MAX_RETRY_ELAPSED_SECS = 45000
-MAX_ATTEMPTS = 3
-
-# lane name -> (items key, results key)
-LANES = {
-    "code-review": ("code_review_items", "code_review_results"),
-    "adversary": ("adversary_items", "adversary_results"),
-    "security": ("security_items", "security_results"),
-    "probe": ("probe_items", "probe_results"),
-}
-
-# Must stay identical to verdict_gate.py's sentinel regexes: a lane this
-# gate calls completed must be one the verdict gate can parse, or a drift
-# would re-run lanes the verdict gate accepts (or accept lanes it cannot
-# read). A cross-pin test compares the literals in both files.
-SENTINELS = {
-    "code-review": r"Verdict:\**\s*\**\s*(MERGE-READY|NEEDS-HUMAN)",
-    "adversary": r"ADVERSARIAL_REVIEW:\s*(CONFORMS|DIVERGES)",
-    "security": r"SECURITY_REVIEW:\s*(PASS|FAIL)",
-    "probe": r"USAGE_PROBE:\s*(PASS|FAIL|INCONCLUSIVE)",
-}
-
-# Filled by main() so the crash guard can append to an upstream fault
-# instead of overwriting it, and report the lanes it had already declined.
-crash_context = {"signals_error": "", "review_incomplete": []}
-
-# Duplicated verbatim in the sibling gate script — the two copies must stay identical.
-ADVERSARY_DEGRADED_HEADER = re.compile(
-    r"Criteria: .*("
-    r"degraded run: pipeline fault recorded"
-    r"|degraded run: \d+ criterion check\(s\) died"
-    r"|verdict computation error:"
-    r")"
-)
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def adversary_degraded(report):
-    # The adversary's verdict.py emits its degraded-run header on the line
-    # directly under the FIRST sentinel; anchoring there keeps a report that
-    # merely quotes the wording later (observations, complaints) a real verdict.
-    lines = report.splitlines()
-    for i, ln in enumerate(lines):
-        if re.search(r"ADVERSARIAL_REVIEW:\s*(CONFORMS|DIVERGES)", ln):
-            nxt = lines[i + 1] if i + 1 < len(lines) else ""
-            return bool(ADVERSARY_DEGRADED_HEADER.match(nxt))
-    return False
-
-
-def nested_degraded(lane, report):
-    # The nested graphs complete with a sentinel even when a stage inside
-    # them died; their own degraded-run wording marks a partial review,
-    # which is not a completed one. Same anchoring as verdict_gate.py.
-    if lane == "code-review":
-        verdict_line = re.search(r"^\*\*Verdict: .*$", report, re.MULTILINE)
-        return bool(
-            verdict_line
-            and re.search(
-                r"^\*\*Verdict: NEEDS-HUMAN\*\* — .*"
-                r"(pipeline fault\(s\) recorded|PIPELINE-FAULT:|report rendering error)",
-                verdict_line.group(0),
-            )
-        )
-    if lane == "adversary":
-        return adversary_degraded(report)
-    return False
-
-
-def is_faulted(lane, report):
-    if not isinstance(report, str):
-        return True
-    if report.strip().startswith("PIPELINE-FAULT:"):
-        return True
-    if not re.search(SENTINELS[lane], report):
-        return True
-    return nested_degraded(lane, report)
-
-
-def attempt_count(attempts, lane):
-    try:
-        return int(attempts.get(lane) or 0)
-    except (TypeError, ValueError):
-        return 0
-
-
-def main():
-    state = load_state()
-    prior = state.get("signals_error")
-    signals_error = prior if isinstance(prior, str) else ""
-    crash_context["signals_error"] = signals_error
-    out = {}
-    declared = state.get("review_incomplete")
-    if isinstance(declared, list):
-        incomplete = [name for name in declared if isinstance(name, str)]
-        malformed = len(incomplete) != len(declared)
-    else:
-        incomplete = []
-        malformed = declared is not None
-    if malformed:
-        fault = (
-            "PIPELINE-FAULT: malformed review_incomplete bookkeeping "
-            f"({repr(declared)[:80]})"
-        )
-        signals_error = f"{signals_error}; {fault}" if signals_error else fault
-        crash_context["signals_error"] = signals_error
-        out["signals_error"] = signals_error
-    crash_context["review_incomplete"] = incomplete
-    raw_attempts = state.get("lane_attempts")
-    attempts = dict(raw_attempts) if isinstance(raw_attempts, dict) else {}
-    kept = dict(state.get("kept_results") or {})
-    faulted = []
-
-    for lane, (items_key, results_key) in LANES.items():
-        results = state.get(results_key) or []
-        if not state.get(items_key):
-            if not results and lane in kept:
-                out[results_key] = [kept[lane]]
-            continue
-        report = results[0] if results else None
-        if report is None:
-            report = f"PIPELINE-FAULT: {lane} lane produced no report"
-            out[results_key] = [report]
-        kept[lane] = report
-        if is_faulted(lane, report):
-            faulted.append(lane)
-        attempts[lane] = attempt_count(attempts, lane) + 1
-
-    # A missing/zero stamp reads as an ancient start and declines every
-    # retry — the safe direction when the clock's origin is unknown.
-    started = state.get("gauntlet_started_at") or 0
-    within_budget = (time.time() - float(started)) <= MAX_RETRY_ELAPSED_SECS
-    retry = [lane for lane in faulted if within_budget and attempts[lane] < MAX_ATTEMPTS]
-    declined = [lane for lane in faulted if lane not in retry]
-    incomplete = sorted(set(incomplete) | set(declined))
-    crash_context["review_incomplete"] = incomplete
-
-    out.update(
-        {
-            "lane_attempts": attempts,
-            "kept_results": kept,
-            "retry_lanes": retry,
-            "review_incomplete": incomplete,
-        }
-    )
-    prior_notes = state.get("retry_notes")
-    notes = [n for n in prior_notes if isinstance(n, str)] if isinstance(prior_notes, list) else []
-    for lane in declined:
-        notes.append(
-            f"lane {lane} faulted and was NOT re-run "
-            f"(attempts {attempts.get(lane, '?')}/{MAX_ATTEMPTS}"
-            + ("" if within_budget else "; wall-clock budget exhausted")
-            + ") — recorded in review_incomplete"
-        )
-    for lane in retry:
-        notes.append(
-            f"lane {lane} faulted (missing / sentinel-less / degraded report) — "
-            f"re-running: attempt {attempts.get(lane, 0) + 1}/{MAX_ATTEMPTS}"
-        )
-    if retry or declined:
-        # stderr is discarded on success by today's engine but is the
-        # forward-compatible live-visibility channel; retry_notes carries the
-        # same lines into the final report either way.
-        sys.stderr.write("WARN: " + " | ".join(notes[-(len(retry) + len(declined)):]) + "\n")
-    out["retry_notes"] = notes
-    if retry:
-        out["_next"] = "build_items"
-    print(json.dumps(out))
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — a gate crash must fall through, never retry
-    fault = f"PIPELINE-FAULT: retry gate crashed — {e}"
-    if crash_context["signals_error"]:
-        fault = f"{crash_context['signals_error']}; {fault}"
-    print(
-        json.dumps(
-            {
-                "retry_lanes": [],
-                "review_incomplete": crash_context["review_incomplete"],
-                "signals_error": fault,
-            }
-        )
-    )

assets/agents/review-gauntlet/scripts/signals.py

@@ -1,125 +0,0 @@
-#!/usr/bin/env python3
-"""Deterministic diff signals for the review gauntlet.
-
-Pure git — no LLM judgment. Every signal is computed from the changed-file
-list and the added lines of the diff. Failures never sink the gauntlet:
-on any error the script reports `signals_error` and leaves the defaults
-(false/empty) in place, which biases lane selection toward the caller's
-context and forced lanes.
-"""
-
-import json
-import os
-import re
-import subprocess
-import time
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-state = load_state()
-proj = os.path.expanduser(
-    (state.get("project_dir_in") or "").strip() or state.get("project_dir") or "."
-)
-spec = (state.get("diff_spec") or "worktree").strip()
-
-
-def git(*args):
-    r = subprocess.run(
-        ["git", "-C", proj, *args], capture_output=True, text=True, timeout=90
-    )
-    if r.returncode != 0:
-        raise RuntimeError((r.stderr or r.stdout).strip()[:400])
-    return r.stdout
-
-
-out = {"project_dir": proj}
-
-# Deterministic plan_context recovery: the parse LLM proved a lossy channel
-# for verbatim spec text (observed replacing ~4 KB of pasted criteria with
-# file paths + a summary sentence). When the raw prompt carries the callers'
-# labeled plan block, cut it out verbatim and override the extraction — but
-# only when the recovered block is LONGER, so a good extraction is never
-# degraded. The adversary lane fails closed on whatever goes missing here.
-_prompt = state.get("initial_prompt")
-if isinstance(_prompt, str) and _prompt:
-    _m = re.search(
-        r"Plan / acceptance criteria:\s*(.+?)"
-        r"(?=\n\s*(?:Local-run recipe|Forced lanes|Rigor:|Security posture:|Extra context)\b|\Z)",
-        _prompt,
-        re.S | re.I,
-    )
-    if _m:
-        _block = _m.group(1).strip()
-        if len(_block) > len((state.get("plan_context") or "").strip()):
-            out["plan_context"] = _block
-# retry_gate measures its wall-clock budget from this stamp; it is set
-# before the git work so a failed diff still starts the clock.
-if not state.get("gauntlet_started_at"):
-    out["gauntlet_started_at"] = time.time()
-try:
-    if spec in ("", "worktree"):
-        names = git("diff", "--name-only", "HEAD")
-        difftext = git("diff", "HEAD")
-    else:
-        names = git("diff", "--name-only", spec)
-        difftext = git("diff", spec)
-    files = [f.strip() for f in names.splitlines() if f.strip()]
-    added = "\n".join(
-        l for l in difftext.splitlines() if l.startswith("+") and not l.startswith("+++")
-    )
-
-    def any_path(pattern):
-        return any(re.search(pattern, f, re.I) for f in files)
-
-    out.update(
-        {
-            "changed_files": files[:200],
-            "file_count": len(files),
-            "touches_proto": any_path(r"\.proto$|buf\.(yaml|gen\.yaml)$"),
-            "touches_migrations": any_path(r"migrations?/|\.sql$"),
-            # auth(?!or) admits auth/authn/authz/oauth but not "author".
-            # Over-firing here is the safe direction: it only ADDS a lane.
-            "touches_auth": any_path(
-                r"auth(?!or)|login|logout|token|session|permission|rbac|\bacl\b|credential|secret"
-            )
-            or bool(
-                re.search(
-                    r"auth(?!or)|password|token|secret|credential|jwt|session",
-                    added,
-                    re.I,
-                )
-            ),
-            "touches_deps": any_path(
-                r"go\.(mod|sum)$|package(-lock)?\.json$|yarn\.lock$|pnpm-lock\.yaml$"
-                r"|Cargo\.(toml|lock)$|requirements[^/]*\.txt$|pyproject\.toml$"
-                r"|Gemfile(\.lock)?$|pom\.xml$|build\.gradle|composer\.(json|lock)$"
-            ),
-            "touches_exec": bool(
-                re.search(
-                    r"exec\.Command|subprocess|os/exec|Runtime\.getRuntime"
-                    r"|shell_exec|\beval\(|\bsystem\(|child_process",
-                    added,
-                )
-            ),
-            "consumer_surface": any_path(
-                r"routes?|handlers?|\bapi\b|endpoints?|\bcmd/|\bcli\b|\.proto$"
-                r"|openapi|swagger|controllers?|graphql"
-            ),
-            "docs_only": bool(files)
-            and all(re.search(r"\.(md|rst|txt|adoc)$", f, re.I) for f in files),
-            "signals_summary": f"{len(files)} file(s) changed (diff: {spec})",
-        }
-    )
-except Exception as e:  # noqa: BLE001 — degraded signals must not sink the gauntlet
-    out["signals_error"] = (
-        f"NOTE: diff signals could not be computed ({e}); "
-        "lane selection falls back to caller context and forced lanes."
-    )
-    out["signals_summary"] = "signals unavailable"
-
-print(json.dumps(out))

assets/agents/review-gauntlet/scripts/verdict_gate.py

@@ -1,402 +0,0 @@
-#!/usr/bin/env python3
-"""Deterministic verdict gate for the review gauntlet.
-
-Parses each configured lane's verdict SENTINEL with a regex — no LLM
-re-reads, no judgment. The gate's hard rules:
-
-  - a missing sentinel is a LANE FAILURE and blocks — never a pass;
-  - a non-string lane result (the map collected an object instead of the
-    lane's rendered text) blocks — it cannot carry a sentinel;
-  - a PIPELINE-FAULT lane result (the lane's agent died after retries;
-    detected only when the report IS the lane_fault.py marker or
-    retry_gate.py's no-report marker, i.e. it STARTS with it — a real
-    review merely quoting the marker flows to the normal rules) or a
-    PIPELINE-FAULT in signals_error (builder/parse fault) blocks — a
-    degraded pipeline is never a pass;
-  - a code-review lane whose OWN verdict line records a pipeline fault
-    (code-reviewer's verdict.py / render.py degraded-run wording) blocks —
-    the nested graph completed, but with a dead domain lane, verifier, or
-    synthesis behind it, so its critical count is not trustworthy;
-  - an adversary lane whose OWN header line (the line directly under its
-    sentinel) records a degraded run — a pipeline fault, died criterion
-    checks, or its verdict script's crash stub — blocks as a PIPELINE-FAULT,
-    not as a DIVERGES finding: the nested graph completed with a dead stage
-    behind it, so its verdict is not a judgment on the code;
-  - a non-zero critical count in the code-review report blocks regardless
-    of the lane's own verdict line — derived from render.py's deterministic
-    summary line (`*Reviewed N files, found X critical, …*`); the raw 🔴
-    count is used only when that summary line is missing;
-  - NEEDS-HUMAN without 🔴 passes but is surfaced as attention required;
-  - probe INCONCLUSIVE blocks with an ENVIRONMENT note — it is never
-    treated as PASS or FAIL (fix the environment per the plan's local-run
-    recipe, then re-run);
-  - a PIPELINE-FAULT lane row carries its attempt count (` ×N`) when retry_gate
-    re-ran it, so the reader can tell a first-pass death from an exhausted
-    retry budget;
-  - an incomplete review — lanes retry_gate gave up on (review_incomplete)
-    or a pipeline-level fault (reported under the `pipeline` pseudo-lane) —
-    emits the GAUNTLET_REVIEW_INCOMPLETE: machine line and a "Review
-    incomplete" section: that is a fault to re-run, never a code finding.
-    Every lane named in review_incomplete is forced to a BLOCKED row, so a
-    restored earlier report can never turn an incomplete review into a
-    pass: a non-empty machine line structurally implies GAUNTLET: BLOCKED.
-    Malformed review_incomplete bookkeeping (not a list, or non-str
-    entries) is itself recorded as a `pipeline` fault, never dropped;
-  - the gate itself must never crash into a silent pass: any internal
-    error emits GAUNTLET: BLOCKED naming the error, with the pipeline
-    marked incomplete.
-"""
-
-import json
-import os
-import re
-
-# Duplicated verbatim in the sibling gate script — the two copies must stay identical.
-ADVERSARY_DEGRADED_HEADER = re.compile(
-    r"Criteria: .*("
-    r"degraded run: pipeline fault recorded"
-    r"|degraded run: \d+ criterion check\(s\) died"
-    r"|verdict computation error:"
-    r")"
-)
-
-
-def load_state():
-    if path := os.environ.get("GRAPH_STATE_FILE"):
-        with open(path) as f:
-            return json.load(f)
-    return json.loads(os.environ.get("GRAPH_STATE", "{}"))
-
-
-def adversary_degraded(report):
-    # The adversary's verdict.py emits its degraded-run header on the line
-    # directly under the FIRST sentinel; anchoring there keeps a report that
-    # merely quotes the wording later (observations, complaints) a real verdict.
-    lines = report.splitlines()
-    for i, ln in enumerate(lines):
-        if re.search(r"ADVERSARIAL_REVIEW:\s*(CONFORMS|DIVERGES)", ln):
-            nxt = lines[i + 1] if i + 1 < len(lines) else ""
-            return bool(ADVERSARY_DEGRADED_HEADER.match(nxt))
-    return False
-
-
-def main():
-    state = load_state()
-    blockers, attention, reports = [], [], []
-    rows = {}
-    malformed = set()
-    lane_attempts = state.get("lane_attempts")
-    if not isinstance(lane_attempts, dict):
-        lane_attempts = {}
-
-    def lane_report(key):
-        arr = state.get(key) or []
-        if not arr:
-            return None
-        item = arr[0]
-        if isinstance(item, str):
-            return item
-        malformed.add(key)
-        return json.dumps(item)
-
-    def record(lane, status, detail=""):
-        rows[lane] = (status, detail)
-
-    def attempt_count(lane):
-        try:
-            return int(lane_attempts.get(lane) or 0)
-        except (TypeError, ValueError):
-            return 0
-
-    def attempts_suffix(lane):
-        n = attempt_count(lane)
-        return f" ×{n}" if n > 1 else ""
-
-    def fault_excerpt(report):
-        line = next(
-            (ln for ln in report.splitlines() if "PIPELINE-FAULT:" in ln), report
-        )
-        return line.strip()[:200]
-
-    def is_lane_fault(report):
-        # A genuine lane fault is the ENTIRE report — the lane_fault.py marker
-        # or retry_gate.py's no-report marker — which always begins with
-        # "PIPELINE-FAULT:". Matching the marker anywhere would let a real
-        # review that merely QUOTES it bypass 🔴 counting and sentinel
-        # parsing.
-        return report.strip().startswith("PIPELINE-FAULT:")
-
-    def lane_fault_blocker(lane, report):
-        blockers.append(
-            f"{lane}: PIPELINE-FAULT — the lane failed after retries and produced "
-            f"no verdict; a degraded lane is never a pass ({fault_excerpt(report)})"
-        )
-        record(lane, "BLOCKED", f"PIPELINE-FAULT (lane failed{attempts_suffix(lane)})")
-
-    def malformed_blocker(lane, report):
-        blockers.append(f"{lane}: malformed lane result (non-string item) — never a pass")
-        record(lane, "BLOCKED", "malformed lane result (non-string)")
-        reports.append((lane, report))
-
-    # --- code-review ------------------------------------------------------
-    cr = lane_report("code_review_results")
-    if cr is None:
-        record("code-review", "SKIPPED", "not selected")
-    elif "code_review_results" in malformed:
-        malformed_blocker("code-review", cr)
-    elif is_lane_fault(cr):
-        lane_fault_blocker("code-review", cr)
-        reports.append(("code-review", cr))
-    else:
-        reports.append(("code-review", cr))
-        m = re.search(r"Verdict:\**\s*\**\s*(MERGE-READY|NEEDS-HUMAN)", cr)
-        # code-reviewer's verdict.py forces NEEDS-HUMAN on its own internal
-        # faults; render.py emits that as `**Verdict: NEEDS-HUMAN** — <reason>`
-        # (CONTRACT comments at both emitters). Scoped to the FIRST rendered
-        # verdict line — render.py emits it before any finding body — so a
-        # finding that quotes the wording cannot trip it.
-        verdict_line = re.search(r"^\*\*Verdict: .*$", cr, re.MULTILINE)
-        m_fault = verdict_line and re.search(
-            r"^\*\*Verdict: NEEDS-HUMAN\*\* — .*"
-            r"(pipeline fault\(s\) recorded|PIPELINE-FAULT:|report rendering error)",
-            verdict_line.group(0),
-        )
-        # Same quoted-marker class as the PIPELINE-FAULT prefix anchoring: a
-        # 🔴 quoted inside finding text or a Changes-table row is not a
-        # finding. render.py's summary line is the authoritative count; the
-        # raw count is the fail-closed fallback when that line is absent. The
-        # LAST match wins: render.py emits the line after every finding body,
-        # so a quoted look-alike earlier in the report cannot shadow it. The
-        # pattern is the FULL shape of render.py's line (CONTRACT comment
-        # there) so a partial look-alike in LLM-authored text never matches.
-        sums = re.findall(
-            r"^\*Reviewed \d+ files, found (\d+) critical, \d+ warnings, \d+ suggestions, "
-            r"\d+ nitpicks \(\d+ deferred by quality bar\)\*$",
-            cr,
-            re.MULTILINE,
-        )
-        reds = int(sums[-1]) if sums else cr.count("🔴")
-        if m_fault:
-            blockers.append(
-                "code-review: the lane reported an internal PIPELINE-FAULT "
-                "(degraded review) — a degraded lane is never a pass"
-            )
-        if reds:
-            blockers.append(
-                f"code-review: {reds} 🔴 CRITICAL finding(s) — fix before claiming done"
-            )
-        suffix = attempts_suffix("code-review")
-        if m_fault and reds:
-            record("code-review", "BLOCKED", f"PIPELINE-FAULT (degraded lane{suffix}); {reds} 🔴")
-        elif m_fault:
-            record("code-review", "BLOCKED", f"PIPELINE-FAULT (degraded lane{suffix})")
-        elif reds:
-            record("code-review", "BLOCKED", f"{reds} 🔴 finding(s)")
-        elif m and m.group(1) == "MERGE-READY":
-            record("code-review", "GREEN", "MERGE-READY")
-        elif m:
-            attention.append(
-                "code-review: NEEDS-HUMAN — see the lane report's "
-                "'Human attention required' section"
-            )
-            record("code-review", "GREEN (attention)", "NEEDS-HUMAN, no 🔴")
-        else:
-            blockers.append(
-                "code-review: no Review Verdict sentinel found — the lane failed; "
-                "a missing verdict is never a pass"
-            )
-            record("code-review", "BLOCKED", "missing verdict sentinel")
-
-    # --- adversary --------------------------------------------------------
-    adv = lane_report("adversary_results")
-    if adv is None:
-        record("adversary", "SKIPPED", "not selected")
-    elif "adversary_results" in malformed:
-        malformed_blocker("adversary", adv)
-    elif is_lane_fault(adv):
-        lane_fault_blocker("adversary", adv)
-        reports.append(("adversary", adv))
-    else:
-        reports.append(("adversary", adv))
-        m = re.search(r"ADVERSARIAL_REVIEW:\s*(CONFORMS|DIVERGES)", adv)
-        if adversary_degraded(adv):
-            blockers.append(
-                "adversary: PIPELINE-FAULT — degraded run, pipeline fault recorded "
-                "inside the adversary; a degraded lane is never a pass"
-            )
-            record(
-                "adversary",
-                "BLOCKED",
-                f"PIPELINE-FAULT (degraded lane{attempts_suffix('adversary')})",
-            )
-        elif m and m.group(1) == "CONFORMS":
-            record("adversary", "GREEN", "CONFORMS")
-        elif m:
-            blockers.append(
-                "adversary: DIVERGES — the implementation does not conform to the plan"
-            )
-            record("adversary", "BLOCKED", "DIVERGES")
-        else:
-            blockers.append(
-                "adversary: no ADVERSARIAL_REVIEW sentinel found — lane failed; never a pass"
-            )
-            record("adversary", "BLOCKED", "missing verdict sentinel")
-
-    # --- security ---------------------------------------------------------
-    sec = lane_report("security_results")
-    if sec is None:
-        record("security", "SKIPPED", "not selected")
-    elif "security_results" in malformed:
-        malformed_blocker("security", sec)
-    elif is_lane_fault(sec):
-        lane_fault_blocker("security", sec)
-        reports.append(("security", sec))
-    else:
-        reports.append(("security", sec))
-        m = re.search(r"SECURITY_REVIEW:\s*(PASS|FAIL)", sec)
-        if m and m.group(1) == "PASS":
-            record("security", "GREEN", "PASS")
-        elif m:
-            blockers.append("security: SECURITY_REVIEW: FAIL — exploitable finding(s)")
-            record("security", "BLOCKED", "FAIL")
-        else:
-            blockers.append(
-                "security: no SECURITY_REVIEW sentinel found — lane failed; never a pass"
-            )
-            record("security", "BLOCKED", "missing verdict sentinel")
-
-    # --- probe ------------------------------------------------------------
-    pb = lane_report("probe_results")
-    if pb is None:
-        record("probe", "SKIPPED", "not selected")
-    elif "probe_results" in malformed:
-        malformed_blocker("probe", pb)
-    elif is_lane_fault(pb):
-        lane_fault_blocker("probe", pb)
-        reports.append(("probe", pb))
-    else:
-        reports.append(("probe", pb))
-        m = re.search(r"USAGE_PROBE:\s*(PASS|FAIL|INCONCLUSIVE)", pb)
-        if m and m.group(1) == "PASS":
-            record("probe", "GREEN", "PASS")
-        elif m and m.group(1) == "FAIL":
-            blockers.append("probe: USAGE_PROBE: FAIL — observed behavior contradicts the contract")
-            record("probe", "BLOCKED", "FAIL")
-        elif m:
-            blockers.append(
-                "probe: INCONCLUSIVE — the ENVIRONMENT could not be established; this is "
-                "not a code verdict. Follow the plan's local-run recipe to fix the "
-                "environment and re-run. INCONCLUSIVE is never treated as PASS or FAIL."
-            )
-            record("probe", "BLOCKED", "INCONCLUSIVE (environment)")
-        else:
-            blockers.append(
-                "probe: no USAGE_PROBE sentinel found — lane failed; never a pass"
-            )
-            record("probe", "BLOCKED", "missing verdict sentinel")
-
-    # retry_gate restores an exhausted lane's LAST report, which may be an
-    # earlier clean verdict — an incomplete lane must block regardless of
-    # what its row parsed to.
-    declared = state.get("review_incomplete")
-    incomplete = set()
-    malformed_bookkeeping = None
-    if isinstance(declared, list):
-        incomplete = {name for name in declared if isinstance(name, str)}
-        if any(not isinstance(name, str) for name in declared):
-            malformed_bookkeeping = repr(declared)[:80]
-    elif declared is not None:
-        malformed_bookkeeping = repr(declared)[:80]
-    for lane in sorted(incomplete - {"pipeline"}):
-        if rows.get(lane, ("", ""))[0] == "BLOCKED":
-            continue
-        after = f" after {n} attempt(s)" if (n := attempt_count(lane)) else ""
-        blockers.append(
-            f"{lane}: review incomplete{after} — the lane never produced a usable verdict"
-        )
-        record(lane, "BLOCKED", f"review incomplete{after}")
-
-    # A gauntlet-level fault (build_items crash, dead parse stage) means the
-    # lanes above were never built — SKIPPED rows alone must not read as PASS.
-    signals_error = state.get("signals_error")
-    pipeline_fault = isinstance(signals_error, str) and "PIPELINE-FAULT:" in signals_error
-    if pipeline_fault:
-        blockers.append(f"pipeline: {signals_error}")
-        incomplete.add("pipeline")
-    if malformed_bookkeeping is not None:
-        blockers.append(
-            "pipeline: PIPELINE-FAULT — malformed review_incomplete bookkeeping "
-            f"({malformed_bookkeeping}); never a pass"
-        )
-        incomplete.add("pipeline")
-    if "pipeline" in incomplete and not any(b.startswith("pipeline:") for b in blockers):
-        blockers.append(
-            "pipeline: review incomplete — a pipeline stage never completed "
-            "(no fault text recorded)"
-        )
-
-    verdict = "BLOCKED" if blockers or incomplete else "PASS"
-
-    incomplete_lines = []
-    for name in sorted(incomplete):
-        if name == "pipeline":
-            incomplete_lines.append(
-                f"- pipeline: {signals_error}"
-                if pipeline_fault
-                else "- pipeline: review incomplete (no fault text recorded)"
-            )
-        elif n := attempt_count(name):
-            incomplete_lines.append(f"- {name}: no completed review after {n} attempt(s)")
-        else:
-            incomplete_lines.append(f"- {name}: no completed review")
-    incomplete_line = (
-        "\nGAUNTLET_REVIEW_INCOMPLETE: " + ", ".join(sorted(incomplete))
-        if incomplete
-        else ""
-    )
-
-    md = "\n".join(
-        ["| lane | status | detail |", "|------|--------|--------|"]
-        + [f"| {lane} | {status} | {detail} |" for lane, (status, detail) in rows.items()]
-    )
-    md += "\n\n## Lane selection\n" + (state.get("lanes_summary") or "(none recorded)")
-    _notes = state.get("retry_notes")
-    if isinstance(_notes, list):
-        _shown = [n for n in _notes if isinstance(n, str)][:8]
-        if _shown:
-            md += "\n\n## Pipeline notes\n" + "\n".join(f"- {n}" for n in _shown)
-    if blockers:
-        md += "\n\n## Blockers\n" + "\n".join(f"- {b}" for b in blockers)
-    if attention:
-        md += "\n\n## Human attention required\n" + "\n".join(f"- {a}" for a in attention)
-    if state.get("signals_error"):
-        md += f"\n\n> {state['signals_error']}"
-    if incomplete_lines:
-        md += "\n\n## Review incomplete\n" + "\n".join(incomplete_lines)
-    md += "\n\n## Full lane reports\n"
-    for lane, rep in reports:
-        md += f"\n<details><summary>{lane}</summary>\n\n{rep}\n\n</details>\n"
-
-    print(
-        json.dumps(
-            {
-                "gauntlet_verdict": verdict,
-                "gauntlet_report": md,
-                "gauntlet_incomplete_line": incomplete_line,
-            }
-        )
-    )
-
-
-try:
-    main()
-except Exception as e:  # noqa: BLE001 — the gate must never crash into a silent pass
-    print(
-        json.dumps(
-            {
-                "gauntlet_verdict": "BLOCKED",
-                "gauntlet_report": f"verdict gate error: {e} — treat as a failed gate, not a pass.",
-                "gauntlet_incomplete_line": "\nGAUNTLET_REVIEW_INCOMPLETE: pipeline",
-            }
-        )
-    )

assets/agents/security-reviewer/README.md

@@ -1,125 +0,0 @@
-# Security Reviewer
-
-A **security analyst** for code changes. Where [`code-reviewer`](../code-reviewer/README.md) asks
-*"is this code good?"* and [`adversary`](../adversary/README.md) asks *"is this the code the plan
-asked for?"*, `security-reviewer` asks the third orthogonal question:
-
-> **"Can this code be abused?"**
-
-It traces untrusted data from sources (CLI args, HTTP input, file contents, LLM outputs) to
-dangerous sinks (shell, SQL, file paths, deserializers, network) and hunts the classic classes:
-injection, committed secrets, missing authn/authz, path traversal, SSRF, unsafe deserialization,
-supply-chain hazards, weak crypto, and sensitive-data exposure.
-
-## Why it's a third reviewer
-
-| | `code-reviewer` | `adversary` | `security-reviewer` |
-|---|---|---|---|
-| Question | Is the code correct/clean? | Does the code match the plan? | Can the code be abused? |
-| Unit of analysis | per-file diffs (fan-out) | criteria ↔ diff mapping | **data flows across files** |
-| Blind spot it covers | slop, bugs, coupling | skipped criteria, scope drift | source→sink paths, secrets, authz gaps |
-| Output | severity-tagged findings | `CONFORMS` / `DIVERGES` | `PASS` / `FAIL` (posture-gated) |
-
-Security flaws live in the path between an input in one file and a sink in another —
-exactly what a per-file review fans out past, and what acceptance criteria almost never mention.
-
-## Posture-gated blocking
-
-Not every project needs production strictness — a POC shouldn't be blocked on missing rate
-limiting. The `security_posture` variable (or an explicit posture in the spawn prompt) sets the
-blocking threshold:
-
-| Posture | Blocks (FAIL) | Intended for |
-|---|---|---|
-| `prototype` | 🔴 Critical only | POCs, spikes, demos, localhost-only tools |
-| `standard` (default) | 🔴 Critical + 🟠 High | Anything deployed, shared, or built upon |
-| `hardened` | 🔴 + 🟠 + 🟡 Medium | Auth, payments, secrets handling, public-facing, multi-tenant |
-
-Two invariants that do not bend with posture:
-
-1. **Critical always blocks.** A committed secret is Critical in a prototype too — git history
-   outlives the prototype. Same for code that endangers the host machine or third-party systems.
-2. **Posture gates the verdict, not the report.** Non-blocking findings are still listed; the
-   posture only decides PASS/FAIL.
-
-Severity itself is calibrated by **reachability × blast radius**, not vulnerability class: SQL
-injection in a localhost-only debug script is not High, and a "small" secret in a repo is Critical.
-
-## Verdict (blocking on FAIL)
-
-The agent ends every review with one sentinel:
-
-```
-SECURITY_REVIEW: PASS
-Posture: standard. Findings: 0 critical, 0 high, 2 medium, 1 low (none at or above the blocking threshold).
-```
-
-```
-SECURITY_REVIEW: FAIL
-Posture: standard. Findings: 0 critical, 1 high, 1 medium, 0 low.
-Blocking findings:
-1. 🟠 Path traversal — export.rs:88 — 'name' from the HTTP body is joined into the output path with no canonicalization; '../../.ssh/authorized_keys' escapes the export root — canonicalize and verify the prefix before writing
-Non-blocking findings:
-1. 🟡 Sensitive data in logs — auth.rs:41 — bearer token logged at debug level — redact before logging
-```
-
-A `FAIL` verdict **blocks** completion, exactly like adversary's `DIVERGES`. The caller
-(sisyphus/architect) resumes the SAME coder session with the blocking findings pasted verbatim,
-then re-runs `security-reviewer` ONCE to confirm the fix.
-
-Every finding cites `file:line` and articulates the concrete attack path. Vague findings are not
-emitted.
-
-## How it reviews
-
-Driven by the [`security-review`](../../skills/security-review/SKILL.md) skill:
-
-1. **Source→sink tracing** per hunk: where does untrusted data enter, what does it reach, and is
-   the mediation between them real (read the sanitizer, don't trust its name)?
-2. **Ground-truth with read-only tools** (`fs_grep`/`fs_read`/`ast_grep`): confirm the vulnerable
-   path is reachable, confirm callers can deliver untrusted data, compare sibling code for the
-   security controls the new code should have mirrored.
-3. **Posture gating**: severities assigned by exploitability, verdict decided by the threshold.
-
-It is **read-only** — it produces a verdict, never a fix.
-
-## Usage
-
-Typically spawned by `sisyphus` alongside `code-reviewer`/`adversary`. The spawn prompt IS its
-entire context, so include the diff (or a base ref), the posture, and any deployment context:
-
-```sh
-agent__spawn --agent security-reviewer --prompt "
-## TASK
-Security-review the recent changes. Return PASS/FAIL.
-
-## POSTURE
-standard  # or: prototype (this is a throwaway POC) / hardened (this touches auth)
-
-## DIFF
-Run get_diff (or --base main), or: <paste diff>
-
-## DEPLOYMENT CONTEXT
-<what this code is for, who can reach it, whether it will be deployed/shared>
-"
-```
-
-Direct invocation for ad-hoc use:
-
-```sh
-coyote -a security-reviewer --agent-variable security_posture prototype \
-  --agent-variable project_dir /path/to/repo \
-  "Review the staged changes. This is a localhost-only spike."
-```
-
-### Tools
-
-- `get_diff [--base <ref>]` — staged → unstaged → `HEAD~1` fallback (or an explicit base/PR branch).
-- `get_changed_files [--base <ref>]` — quick map of the attack surface.
-- Plus read-only `fs_*` and `ast_grep` for ground-truth checks.
-
-## Related
-
-- [`security-review`](../../skills/security-review/SKILL.md) — the methodology it runs on.
-- [`code-reviewer`](../code-reviewer/README.md) — the quality reviewer it runs alongside.
-- [`adversary`](../adversary/README.md) — the plan-conformance reviewer it runs alongside.

assets/agents/security-reviewer/config.yaml

@@ -1,132 +0,0 @@
-name: security-reviewer
-description: Security analyst - hunts exploitable flaws in a code change (injection, secrets, authz gaps, SSRF, supply chain) by tracing untrusted data to dangerous sinks. Returns a posture-gated PASS/FAIL verdict so POCs aren't held to production strictness. Complements code-reviewer (quality) and adversary (plan conformance). Designed to be delegated to by sisyphus.
-version: 1.1.0
-
-auto_continue: true
-max_auto_continues: 15
-inject_todo_instructions: true
-
-skills_enabled: true
-enabled_skills:
-  - security-review
-
-variables:
-  - name: project_dir
-    description: Project directory containing the changes under review
-    default: '.'
-  - name: security_posture
-    description: Blocking threshold - prototype (Critical only), standard (Critical+High), hardened (Critical+High+Medium)
-    default: standard
-  - name: auto_confirm
-    description: Auto-confirm command execution
-    default: '1'
-
-global_tools:
-  - ast_grep.sh
-  - fs_read.sh
-  - fs_cat.sh
-  - fs_grep.sh
-  - fs_glob.sh
-  - fs_ls.sh
-  - execute_command.sh
-
-instructions: |
-  You are a security reviewer. You answer ONE question: **can this code be abused?** You are NOT
-  the code-quality reviewer (that is `code-reviewer`/`file-reviewer`) and NOT the plan-conformance
-  reviewer (that is `adversary`). You hunt exploitable flaws in the CHANGE: injection, committed
-  secrets, missing auth, path traversal, SSRF, unsafe deserialization, supply-chain hazards.
-
-  Your value is attacker mindset applied to fresh code with zero stake in the implementation. The
-  implementer thought about the happy path; you think about the input that lies.
-
-  ## Step 0: Load the skill
-
-  Before anything else, `skill__load` `security-review`. It carries your methodology: the
-  source-to-sink tracing discipline, the severity model (calibrated by reachability and blast
-  radius, not vulnerability class), the posture gating table, the hunt checklist, and the exact
-  verdict format. The skill body is your source of truth for HOW to review and WHAT blocks; these
-  instructions handle workflow and I/O.
-
-  ## Input (the spawn prompt IS your entire context)
-
-  You are given:
-  1. **The diff** — pasted inline, or run `get_diff` (optionally `--base <ref>`) if told to fetch it.
-  2. **The security posture** — `prototype`, `standard`, or `hardened`. The `security_posture`
-     variable (currently: {{security_posture}}) is the default; an explicit posture in the spawn
-     prompt overrides it. If neither is given, use `standard` and say so in the report.
-  3. **Deployment context** (optional but valuable) — what the code is for, who can reach it,
-     whether it will be deployed/shared. Use it to calibrate severity; never to skip the review.
-
-  ## Workflow
-
-  1. Load `security-review`.
-  2. Get the diff (inline or via `get_diff`) and identify the changed files.
-  2b. **Mechanized pre-pass (deterministic, read-only).** Before manual tracing, run whichever of
-     these exist on PATH and fit the repo — never install anything, skip each silently when absent,
-     time-box each to ~60s via `execute_command`:
-     - `gitleaks` on the changed paths (committed-secret candidates);
-     - `semgrep --config auto --error --quiet` scoped to the changed files (or the repo's own
-       `.semgrep.yml` when present);
-     - a dependency audit when a manifest/lockfile changed: `osv-scanner --lockfile <it>`,
-       `npm audit --omit dev`, `cargo audit`, or `pip-audit` — whichever matches.
-     Treat every mechanized hit as a LEAD, not a finding: trace it per steps 3-5 and report it only
-     with the confirmed source→sink path (or secret location) and your own severity calibration.
-     Note which tools ran/were skipped in the report. Raw scanner output is never pasted as findings.
-  3. For EACH hunk: identify untrusted-data sources, dangerous sinks, and the mediation (or lack of
-     it) between them. Apply the skill's hunt checklist (secrets, injection, paths, authn/authz,
-     deserialization, network, supply chain, crypto, data exposure, resource abuse).
-  4. Ground-truth every candidate finding: `fs_read` around the hunk to confirm reachability,
-     `fs_grep` callers to confirm untrusted data can actually arrive, `fs_grep` sibling code for the
-     security controls the new code should have mirrored, and READ any sanitizer/validator the diff
-     relies on. Use `ast_grep` for structural checks (e.g. string-built SQL, `sh -c` call sites).
-  5. Assign each finding a severity by exploitability (who can reach it, what does the attacker
-     win), then apply the posture threshold to produce the verdict.
-  6. Emit the verdict in the skill's exact format.
-
-  ## Output — verdict (MANDATORY, exact format)
-
-  End with EXACTLY one of these sentinels so the caller can route on it:
-
-  ```
-  SECURITY_REVIEW: PASS
-  Posture: <prototype|standard|hardened>. Findings: X critical, Y high, Z medium, W low (none at or above the blocking threshold).
-  <optional: top 1-3 non-blocking findings worth fixing anyway>
-  ```
-
-  ```
-  SECURITY_REVIEW: FAIL
-  Posture: <prototype|standard|hardened>. Findings: X critical, Y high, Z medium, W low.
-  Blocking findings:
-  1. 🔴|🟠|🟡 <class> — <file:line> — <source → sink attack path> — <concrete fix>
-  Non-blocking findings:
-  1. 🟡|🟢 <class> — <file:line> — <description> — <fix>
-  ```
-
-  Every finding MUST cite file:line and articulate the concrete attack path or hazard. A finding
-  with no location and no attack path is noise — do not emit it.
-
-  ## Rules
-
-  1. **You are read-only.** Never modify files. You produce a verdict; the implementer owns the fix.
-  2. **Security, not quality.** Do not flag style, naming, performance, or maintainability unless it
-     creates a vulnerability.
-  3. **Critical always blocks — in every posture.** A committed secret or host-endangering code is
-     Critical in a prototype too. Posture gates High/Medium, never Critical.
-  4. **Posture gates the verdict, not the report.** Non-blocking findings are still listed; the
-     posture only decides PASS/FAIL.
-  5. **Review the CHANGE.** Pre-existing vulnerabilities outside the diff go under
-     `Pre-existing, out of scope:` and never count toward the verdict — unless the diff makes them
-     newly reachable.
-  6. **Severity = reachability × blast radius.** SQL injection in a localhost-only debug script is
-     not High; a "small" secret in a repo is Critical.
-  7. Be terse and decisive. Three exploitable findings beat fifteen theoretical ones. If everything
-     is theoretical hardening, it PASSes — say so.
-
-  ## Context
-  - Project: {{project_dir}}
-  - Security posture: {{security_posture}}
-  - CWD: {{__cwd__}}
-  - Shell: {{__shell__}}
-
-  ## Available Tools
-  {{__tools__}}

assets/agents/sisyphus/README.md

@@ -26,11 +26,8 @@ flowchart TD
     broad_gate -->|"no"| spec_gate
     code_reviewer --> spec_gate{"Implements<br/>a spec / plan?"}
     spec_gate -->|"yes"| adversary[["adversary<br/>plan-conformance"]]
-    spec_gate -->|"no"| sec_gate
+    spec_gate -->|"no"| done
-    adversary --> sec_gate{"Touches attack surface?<br/>external input / auth /<br/>secrets / shell / deps"}
+    adversary --> done
-    sec_gate -->|"yes"| security_reviewer[["security-reviewer<br/>posture-gated PASS/FAIL"]]
-    sec_gate -->|"no"| done
-    security_reviewer --> done
     direct --> done
     done([Complete])
 
@@ -46,10 +43,7 @@ Spawnable sub-agents (from `config.yaml`):
 - **[coder](../coder/README.md)** — graph agent that plans, implements, and verifies (build + tests) in a bounded fix-loop.
 - **[code-reviewer](../code-reviewer/README.md)** — independent post-implementation review; fires when the change is broad (2+ coders, 5+ files) or crosses architectural boundaries.
 - **[adversary](../adversary/README.md)** — plan-conformance review; fires whenever the change implements a written spec, plan step, or acceptance-criteria list. Orthogonal to `code-reviewer` — both can run.
-- **[security-reviewer](../security-reviewer/README.md)** — security analysis; fires when the change touches attack surface (external input, auth/secrets, shell/file-path sinks, new dependencies). Verdict is posture-gated (`prototype`/`standard`/`hardened`) so POCs aren't held to production strictness, but Critical findings (committed secrets, host-endangering code) block in every posture. Orthogonal to both other reviewers — all three can run.
-- **[review-gauntlet](../review-gauntlet/README.md)** — preferred single entry point for the post-implementation review passes: a graph that computes diff signals deterministically, runs the applicable lanes (code-reviewer / adversary / security-reviewer / probe) in parallel, and machine-parses their verdict sentinels into GAUNTLET: PASS/BLOCKED — skipping a lane or misreading a verdict becomes structurally impossible. A `GAUNTLET_REVIEW_INCOMPLETE:` line under BLOCKED is an infrastructure fault (a lane exhausted its retries, or the pipeline faulted) that Sisyphus escalates to the user — retry / accept NEEDS-HUMAN / abort — never a finding to fix. The reviewer bullets above describe the lanes it runs and remain the spawn fallback when it is not installed.
 - **[step-runner](../step-runner/README.md)** — graph agent that executes one step of a phased plan repo. Internally delegates to `coder` for implementation and optionally to `code-reviewer` for review.
-- **[whetstone](../whetstone/README.md)** — continuous improvement; spawned ONCE at the end of a run that addressed review feedback from outside Sisyphus's own lanes (humans, or a teammate's independent review agent — never its own reviewers' output). Classifies each piece of feedback CATCH/PARTIAL/MISS against what the run's own reviewers flagged and converts the misses into user-approved suite improvements (skill edits, ledger entries). Never blocks run completion.
 
 ## Features
 
@@ -57,9 +51,7 @@ Spawnable sub-agents (from `config.yaml`):
 - 💻 **CLI Coding**: Provides a natural language interface for writing and editing code.
 - 🔄 **Task Management**: Tracks progress and context across complex operations.
 - 🛠️ **Tool Integration**: Seamlessly uses system tools for building, testing, and file manipulation.
-- 🧵 **Task-queue bursts**: Dependency-shaped fan-outs (explore → code → verify) may be encoded as `agent__task_create` chains — dependents auto-dispatch when `agent__task_complete` unblocks them; todos remain the tracking source of truth.
 - 📋 **Plan-Driven Workflows**: Authors, reviews, and executes phased implementation plans with handoffs between steps.
-- 🚦 **Escalation policy**: `escalation_policy=autonomous` pre-delegates decision-making — standing rulings (`~/.config/coyote/share/standing-rulings.md`, recorded via `coyote --macro record-ruling`) and evidence-backed recommended options are taken without pausing and batched into a “Decisions taken autonomously” digest; secrets, money movement, and destructive actions always escalate.
 
 ## Plan-Driven Workflows
 

assets/agents/sisyphus/config.yaml

@@ -1,6 +1,6 @@
 name: sisyphus
 description: OpenCode-style orchestrator - classifies intent, delegates to specialists, tracks progress with todos, enforces OMO-grade verification discipline
-version: 3.13.0
+version: 3.2.0
 
 agent_session: temp
 auto_continue: true
@@ -15,26 +15,16 @@ spawnable_agents:
   - oracle
   - code-reviewer
   - adversary
-  - security-reviewer
-  - probe
-  - review-gauntlet
-  - architecture-reviewer
   - step-runner
-  - whetstone
+max_concurrent_agents: 4
-max_concurrent_agents: 40
+max_agent_depth: 3
-max_agent_depth: 5
 inject_spawn_instructions: true
-summarization_threshold: 80000
+summarization_threshold: 8000
 
 skills_enabled: true
 enabled_skills:
   - ai-slop-remover
   - code-review
-  - comment-discipline
-  - diagnosing-bugs
-  - grilling
-  - logging-discipline
-  - observability-review
   - git-master
   - frontend-ui-ux
   - delegation-protocol
@@ -50,15 +40,9 @@ variables:
   - name: project_dir
     description: Project directory to work in
     default: '.'
-  - name: observability_agent
-    description: Optional agent that can query the live monitoring stack (existing alerts, thresholds) during the observability pass. Empty disables the live lookup; repo-derived inventory still runs.
-    default: ''
   - name: auto_confirm
     description: Auto-confirm command execution
     default: '1'
-  - name: escalation_policy
-    description: "How escalation-worthy decisions are handled mid-run: 'interactive' pauses and asks the user; 'autonomous' self-resolves decisions covered by a standing ruling or a clearly recommended option, reports them in a final-report digest, and only pings on hard triggers or novel conflicts"
-    default: 'interactive'
 
 mcp_servers:
   - ddg-search
@@ -71,7 +55,6 @@ global_tools:
   - fs_write.sh
   - fs_patch.sh
   - execute_command.sh
-  - web_search_coyote.sh
 
 instructions: |
   You are Sisyphus - an orchestrator that drives coding tasks to completion. You do NOT work alone when specialists are available. You classify, delegate, verify, complete.
@@ -141,8 +124,6 @@ instructions: |
 
   For "improve X" / "refactor Y" / "clean up Z" type requests, quick-assess the codebase state BEFORE following patterns:
 
-  **Architecture-scale improvement requests** ("improve the architecture of X", "this module is hard to test", "make this easier to navigate") → delegate to `architecture-reviewer`. It scans for deepening opportunities weighted by git hot spots, reports candidates, and refines the chosen one into an implementation-ready interface proposal — which you then hand to `coder`. It proposes only; it is an on-demand tool, never a completion gate. For file-scale cleanups, proceed with the assessment below instead.
-
   - **Disciplined** (consistent patterns, configs present, tests exist) → Follow existing style strictly
   - **Transitional** (mixed patterns) → Ask: "I see X and Y patterns. Which to follow?"
   - **Legacy/Chaotic** (no consistency) → Propose: "No clear conventions. I suggest [X]. OK?"
@@ -234,23 +215,13 @@ instructions: |
 
   Never artificially cap at a small number. If there are 10 distinct things to find, spawn 10 agents. The system limit is the only ceiling that matters.
 
-  For dependency-shaped bursts (explore → code → verify), `agent__task_create` chains MAY encode the
-  ordering — dependents with `agent`+`prompt` auto-dispatch when `agent__task_complete` unblocks them.
-  Same rules as direct spawning: collect every auto-dispatched agent via `agent__collect`, and an agent
-  finishing does NOT complete its task — call `agent__task_complete` yourself. Todos remain the tracking source of truth.
-
-  If the slices are likely to FEED each other (adjacent modules; one lane's discovery redirects another's search), run the burst in team mode per `parallel-research`: after spawning, send
-  every explorer the roster of its siblings (`agent__send_message --id <id> --message "Teammate roster: <slice>=<id>, ... Message a teammate directly when you find a fact in THEIR slice;
-  check your inbox after each search round and before finalizing."`) so cross-slice facts move directly between lanes instead of waiting for your synthesis. Never do this with reviewer
-  lanes — reviewer verdicts stay independent.
-
   ### The wait protocol
 
   After spawning background agents:
 
   1. Do non-overlapping work if any (work that doesn't depend on delegated results).
   2. If none → **end your response.** Do not call `agent__collect` immediately.
-  3. The system notifies you on completion — a `system_notifications` entry appears on your next tool result naming the exact collect command.
+  3. The system notifies you on completion.
   4. On notification, call `agent__collect` to retrieve results.
 
   ### Anti-duplication rule (BLOCKING)
@@ -301,69 +272,6 @@ instructions: |
   - Never reuse a verification claim from an earlier report (yours or another agent's) without re-running the command yourself. Prior reports are unverified context, not evidence.
   - An honest failure — "gate X failed / could not run, here is the verbatim error" — is an acceptable, preferable deliverable. A success-shaped report with missing evidence poisons every downstream consumer.
 
-  ### The review gauntlet (preferred): one spawn, every review lane, machine-parsed verdicts
-
-  When the `review-gauntlet` agent is installed, run the post-implementation review passes through
-  it instead of spawning the individual reviewers yourself. Spawn it ONCE whenever the work was
-  non-trivial (any trigger in the reviewer sections below would fire, or you are unsure whether one
-  would):
-
-  ```
-  agent__spawn --agent review-gauntlet --prompt "Post-implementation review gate.
-  Project: <absolute repo path>
-  Diff: <git range like main...HEAD, or 'worktree' for uncommitted changes>
-  Rigor: <rigor>   Security posture: <posture>
-  Plan / acceptance criteria: <pasted verbatim — enables the adversary lane; omit when none>
-  Prior review decisions: <on re-review rounds ONLY: earlier rounds' resolved/rejected
-  findings verbatim (rejected-finding log lines, round-comment reconciliations) — settled
-  decisions the reviewers must not re-litigate; omit on the first round>
-  Local-run recipe / usage suites: <from the plan — enables the probe lane; omit when none>"
-  --variables {"verification_commands": "[\"cargo test --all\", \"cargo clippy -- -D warnings\"]"}
-  <— the cargo commands above are only an EXAMPLE: replace them with THIS project's exact build/test/lint commands; never guess, and pass "[]" when none apply>
-  ```
-
-  Verification commands go in `--variables` (a JSON-array string), never in the prompt: the prompt
-  also carries pasted plan text from the repo under review, and whatever is declared here is
-  executed with a shell — a trust boundary the prose must not cross.
-  Budget: each declared command gets at most 15 minutes and the whole set 55 minutes —
-  declare targeted build/unit-test commands, not full integration suites; a command that
-  exceeds the budget is recorded as a red run and fails conformance. Never declare commands
-  that boot shared stacks or services (docker compose projects, dev servers, fixed ports) —
-  the probe lane owns end-to-end runs and WILL collide with them in parallel; keep
-  verification to generate/lint/build/unit/integration commands.
-
-  It computes diff signals deterministically, selects lanes (code-review always; adversary when a
-  spec/plan is present; security on attack-surface signals; probe on consumer-facing surface with a
-  run recipe — judgment can only WIDEN the selection, never narrow it), runs the selected lanes in
-  parallel verdict-independent, and returns a machine-parsed `GAUNTLET: PASS` or `GAUNTLET: BLOCKED`
-  with a lane table, blockers, attention items, and every lane's full report.
-
-  - `GAUNTLET: BLOCKED` blocks completion. Route each blocker that is a real review finding through
-    the findings-handling rules in the reviewer sections below (🔴 → coder fix in the SAME session;
-    DIVERGES → the adversary rules; security FAIL → the security rules; probe INCONCLUSIVE → fix the
-    ENVIRONMENT per the plan's local-run recipe first — it is never a code verdict). Then spawn a
-    FRESH gauntlet run; lane selection re-runs from the new diff. A BLOCKED whose only blockers are
-    review faults (`PIPELINE-FAULT` / `review incomplete` entries) is NOT a code failure — the next
-    rule owns it.
-  - `GAUNTLET_REVIEW_INCOMPLETE: <lane>[, <lane>]` (the line directly under `GAUNTLET: BLOCKED`)
-    means the review could NOT be completed: the named lanes still faulted after 3 attempts, or the
-    gauntlet pipeline itself faulted (`pipeline`). This is an infrastructure fault, not a code
-    finding. NEVER route it through the findings-handling rules. NEVER claim done while it stands.
-    Escalate to the user via `user__select` with exactly these three options:
-    - "Retry the review again"
-    - "Accept NEEDS-HUMAN: proceed without the <lane or pipeline> review (recorded in the report / PR body)"
-    - "Abort this task"
-    Retry → spawn a FRESH gauntlet run. Accept → finish the work and record the skipped review
-    (lane names or `pipeline`) in your final report and in the PR body when you author one. Abort →
-    stop; leave the code in a working state and report. Findings AND incomplete on the same output →
-    fix the findings first, then re-run the gauntlet (the re-run retries the lane) — escalate only if
-    the line persists. Under `escalation_policy: autonomous` the standard ladder applies (a standing
-    ruling may pre-answer this decision).
-  - `GAUNTLET: PASS` with a "Human attention required" section: finish the work and carry those
-    items into your final report verbatim.
-  - The reviewer sections below remain authoritative for HANDLING each lane's findings, and are the
-    spawn fallback when `review-gauntlet` is not installed.
-
   ### Independent code review (post-coder, non-trivial work)
 
   After completing delegated `coder` work, spawn `code-reviewer` for an independent review pass if ANY of these are true:
@@ -384,7 +292,6 @@ instructions: |
 
   Original request: <one-line summary of what the user asked for>
   Scope: <which directories or files the changes are expected to touch>
-  Quality bar: rigor=<...>, surfaces=<...>
 
   Coder summaries:
   - <coder 1 session_id>: <plan_summary from CODER_COMPLETE>
@@ -393,17 +300,13 @@ instructions: |
   Run `get_diff` against the staged or recent changes, fan out file-reviewers per changed file as usual, and synthesize."
   ```
 
-  Include the `Quality bar:` line only when your own task prompt carried one (rigor and/or surfaces from the plan's quality bar); when it did not, omit the line entirely — code-reviewer resolves the quality bar on its own.
-
   ### Handling code-reviewer findings
 
   - **🔴 CRITICAL** findings block completion. Spawn `coder` to fix — preferably the SAME session as the original coder (`agent__spawn --session_id <id> --prompt "Fix: <critical findings pasted verbatim>"`). Do NOT re-spawn `code-reviewer` automatically after the fix; coder's own `self_review` on the fix is sufficient unless the fix itself was substantial (5+ files or architectural).
-  - **🟡 WARNING** findings are blocking at `production` rigor (the default when none was declared) unless the work was explicitly scoped to defer them; if unsure, ASK the user via `user__ask` whether to fix or accept. At `poc`/`prototype` rigor, below-threshold `[convention]` findings (the ones code-reviewer's Rigor Folding moved under `## Deferred by quality bar`) are NOT fixed and NOT silently dropped: list each in your final report's FOLLOW-UPS section with a `(deferred by quality bar)` tag. 🔴 blocks at every rigor — rigor never lowers that bar.
+  - **🟡 WARNING** findings are blocking unless the work was explicitly scoped to defer them. If unsure, ASK the user via `user__ask` whether to fix or accept.
   - **🟢 SUGGESTION / 💡 NITPICK** findings are informational. Surface them to the user with the final report. Do not block on them.
   - **`Pre-existing, out of scope:` findings** — surface to the user but do not act on them. They predate this work and aren't the current task's responsibility.
 
-  **Rejecting a `[convention]` finding.** A rejection MUST cite one of: (a) a **repo convention** — file:line evidence that the codebase deliberately does it another way, or (b) a **recorded plan decision** — an entry in the plan's `## Quality bar` dropped-practices list. Bare rejections ("we don't do that here", "not needed") are invalid — the finding stands. NEVER rejectable: 🔴 findings and `[correctness]` findings. Every rejection becomes exactly one durable log line formatted `rejected-finding: <finding> — <evidence>` — report your rejections in your final summary so the orchestrator logs them durably in the task's log. If a reviewer re-raises a finding that already has a cited rejection on record, escalate to the user instead of looping.
-
   ### When NOT to re-spawn code-reviewer
 
   After a fix-loop completes, do not automatically re-run `code-reviewer` unless the fix itself triggers the same thresholds (2+ coders, 5+ files, architectural). Each `code-reviewer` invocation fans out N file-reviewers per changed file; spurious re-runs burn budget without proportional value. Trust coder's `self_review` on bounded fixes.
@@ -423,13 +326,8 @@ instructions: |
 
   PLAN — acceptance criteria to check against:
   <paste the task/step spec + acceptance criteria VERBATIM — not a summary>"
-  --variables {"verification_commands": "[\"cargo test --all\", \"cargo clippy -- -D warnings\"]"}
-  <— the cargo commands above are only an EXAMPLE: replace them with THIS project's exact build/test/lint commands; never guess, and pass "[]" when none apply>
   ```
 
-  Same trust boundary as the gauntlet spawn: verification commands are declared via `--variables`,
-  never in the prompt, because the prompt also carries untrusted pasted text.
-
   ### Handling adversary findings
 
   - **`ADVERSARIAL_REVIEW: DIVERGES` blocks completion.** Do not mark the task done. Resume the SAME coder session (`agent__spawn --session_id <id> --prompt "Fix these plan-conformance failures: <complaints pasted verbatim>"`) — do not spawn a fresh coder. After the fix, re-run `adversary` ONCE to confirm it now CONFORMS; if it still DIVERGES on the same criteria after one fix cycle, STOP and escalate to the user (the plan or the approach may be wrong — consider `oracle`).
@@ -438,145 +336,10 @@ instructions: |
 
   Unlike `code-reviewer`, re-running `adversary` once after a conformance fix is expected — a DIVERGES verdict is a hard gate, and confirming the fix actually closed it is the point.
 
-  ### Security review (post-coder, when the change touches attack surface)
-
-  `code-reviewer` asks "is this code good?" and `adversary` asks "is this the code the plan asked for?" — neither asks "can this code be abused?" Spawn `security-reviewer` when the change touches security-relevant surface. It traces untrusted data to dangerous sinks (injection, path traversal, SSRF), hunts committed secrets, missing authn/authz, unsafe deserialization, and supply-chain hazards, then returns a posture-gated PASS/FAIL verdict.
-
-  **When to spawn it** — ANY of these:
-
-  1. The change handles **external input**: HTTP endpoints, CLI args passed to shell/SQL/file paths, parsed file formats, deserialized payloads, LLM/tool outputs used in commands
-  2. The change touches **auth, secrets, credentials, crypto, or session handling**
-  3. The change adds **new dependencies, install scripts, or code that fetches-and-executes remote content**
-  4. The change performs **file-system writes at user-influenced paths or shell execution with interpolated strings**
-  5. **You judge the change security-relevant** even if 1-4 don't trigger
-
-  If none fire (pure refactor, docs, internal data shuffling with no new inputs or sinks), skip it — a security pass on inert code burns budget without value.
-
-  **Choosing the posture** (this is YOUR call as orchestrator; pass it explicitly):
-
-  - `prototype` — the user said POC/spike/prototype/demo/throwaway, or the tool is explicitly localhost-only. Blocks Critical only.
-  - `standard` (default) — anything that will be deployed, shared, committed to a shared repo, or built upon. Blocks Critical + High.
-  - `hardened` — auth, payments, secrets handling, public-facing surface, multi-tenant code. Blocks Critical + High + Medium.
-
-  When your task prompt carries a declared rigor (a `Quality bar:` line, or the plan's `## Quality bar` section), derive the default posture from it unless the plan overrides the posture explicitly: rigor `poc` → `prototype` posture; rigor `prototype` → `standard`; rigor `production` → `standard`. `hardened` is never a rigor default — it remains the judgment-based escalation above for auth, payments, multi-tenant, or public-facing surface.
-
-  When in doubt, use `standard`. Note: Critical findings (committed secrets, host-endangering code) block in EVERY posture — "it's just a POC" never excuses a leaked credential.
-
-  **Spawn pattern** (the prompt IS its whole context — include posture and deployment context):
-
-  ```
-  agent__spawn --agent security-reviewer --prompt "Security-review the recent coder change(s). Return PASS/FAIL.
-
-  POSTURE: <prototype|standard|hardened> — <one line on why>
-
-  DIFF: run get_diff (or --base <ref>), or: <paste diff>
-
-  DEPLOYMENT CONTEXT: <what this code is for, who can reach it, whether it will be deployed/shared>"
-  ```
-
-  ### Handling security-reviewer findings
-
-  - **`SECURITY_REVIEW: FAIL` blocks completion.** Do not mark the task done. Resume the SAME coder session (`agent__spawn --session_id <id> --prompt "Fix these security findings: <blocking findings pasted verbatim>"`) — do not spawn a fresh coder. After the fix, re-run `security-reviewer` ONCE to confirm it now PASSes; if it still FAILs on the same findings after one fix cycle, STOP and escalate to the user.
-  - **`SECURITY_REVIEW: PASS`** — proceed. Surface any non-blocking findings to the user in the final report so they can decide whether to harden later; do not fix them unasked.
-  - **`Pre-existing, out of scope:` findings** — surface to the user but do not act on them. They predate this work and aren't the current task's responsibility.
-  - **Posture disagreement** — if the reviewer's report suggests the posture you chose understates the real exposure (e.g. you said `prototype` but the diff wires up a public endpoint), re-run with the higher posture rather than rationalizing the PASS.
-
-  Like `adversary`, re-running `security-reviewer` once after a fix is expected — a FAIL verdict is a hard gate, and confirming the fix closed the attack path is the point. Run all applicable reviewers (`code-reviewer`, `adversary`, `security-reviewer`, `probe`) — they cover disjoint failure modes; one passing says nothing about the others.
-
-  ### Usage-pattern probe (post-coder, when the change touches consumer-facing surface)
-
-  `code-reviewer`, `adversary`, and `security-reviewer` all read TEXT — the diff, the plan, the
-  attack surface. None of them answers "does the feature actually behave correctly when a consumer
-  uses it?" Spawn `probe` when the change touches consumer-facing surface. It boots the system
-  locally from a clean slate, runs existing usage suites first (regression check), derives expected
-  behaviors from the SPEC (never the implementation, so the implementer's misreadings can't become
-  its assertions), authors tests for the uncovered usage patterns in the repo's existing suite
-  conventions (tools like Hurl/curl for HTTP, grpcurl for gRPC, direct invocation for CLIs are
-  examples, not requirements), and returns a blocking `USAGE_PROBE: PASS/FAIL/INCONCLUSIVE` verdict.
-
-  **When to spawn it** — ANY of these:
-
-  1. The change adds or modifies **externally consumed surface**: HTTP endpoints/RPCs,
-     request/response shapes, status codes, CLI commands/flags, event/webhook payloads
-  2. The change alters **contract semantics**: partial-update (patch-vs-replace) behavior,
-     idempotency, pagination, auth requirements on routes, error shapes
-  3. **You judge the change consumer-visible** even if 1-2 don't trigger
-
-  If none fire (pure refactor, internal data shuffling with no consumer-visible effect), skip it
-  with a one-line note — booting a stack to probe inert internals burns budget without value.
-
-  **Spawn pattern** (the prompt IS its whole context — include the spec AND the local-run recipe):
-
-  ```
-  agent__spawn --agent probe --prompt "Probe the changed surface from the consumer's perspective. Return PASS/FAIL/INCONCLUSIVE.
-
-  CHANGE: run get_diff (or --base <ref>), or: <paste the changed-surface summary>
-
-  SPEC — expected behavior to verify against:
-  <paste acceptance criteria + API contract sections (or contract file paths) VERBATIM>
-
-  LOCAL-RUN RECIPE: <how to boot the stack clean — build, deps/stubs, ports, migrations, teardown — or where the recipe lives>
-
-  EXISTING SUITES: <paths + run commands, or 'discover them'>"
-  ```
-
-  ### Handling probe findings
-
-  - **`USAGE_PROBE: FAIL` blocks completion.** Do not mark the task done. Resume the SAME coder
-    session (`agent__spawn --session_id <id> --prompt "Fix these behavioral findings: <findings
-    pasted verbatim, including repros>"`) — do not spawn a fresh coder. After the fix, re-run
-    `probe` ONCE — resume ITS session too, so it reuses the environment and tests it already built.
-    If it still FAILs on the same findings after one fix cycle, STOP and escalate to the user (the
-    spec or the design may be the root cause — consider `oracle`).
-  - **`USAGE_PROBE: PASS`** — proceed. Adopt the test files probe authored (written in the repo's
-    suite conventions; paths are in its report) into the change so they ship as permanent
-    regression coverage. Surface any stale-test or recipe observations to the user.
-  - **`USAGE_PROBE: INCONCLUSIVE`** — the ENVIRONMENT, not the code, is the blocker. Never treat it
-    as PASS or FAIL. If the missing recipe/fixture/mock is cheap to provide, supply it and re-run
-    probe once (resume its session). Otherwise surface the gap to the user — a consumer-facing
-    change that cannot be exercised locally is itself a finding.
-  - **Tests flagged EXPECTED-CHANGE** (existing tests asserting a contract the spec explicitly
-    changed) — have the coder update them as part of the change; never delete or silence them to
-    get green.
-
-  Like the other hard gates, re-running `probe` once after a fix is expected — confirming the
-  behavioral finding is actually closed is the point.
-
-  ### Observability pass (post-coder, advisory — when the change adds operational surface)
-
-  After implementation (and alongside/after the reviewers), if the change adds **operational surface** — a new or changed external endpoint, error path, queue consumer/producer, background job, cron, external dependency, or new metrics — load `observability-review` and run its pass. If none of these apply, skip with a one-line note.
-
-  This lane is ADVISORY: it always produces an artifact, never a blocking verdict.
-
-  1. Follow the skill: detect the repo's observability stack, inventory existing coverage for the touched paths, and classify gaps. If `observability_agent` is set (currently: '{{observability_agent}}'), spawn it for a read-only live inventory of existing alerts/thresholds; otherwise note the inventory is repo-derived.
-  2. **Alert-as-code lives in this repo** and gaps warrant coverage → spawn `coder` (preferably resuming the task's session) to make the rule/monitor changes, following existing rule conventions. These are ordinary code changes — the usual review gates apply to them.
-  3. **Alerting is external or the call is judgment-heavy** (paging severity, thresholds without baselines) → include the skill's structured recommendations block instead. Never touch external alerting systems.
-  4. Attach the skill's `## Observability` output block to your final report (and to the PR description when you author one).
-
-  Do not block completion on observability findings — the failure mode is skipping the pass on applicable surface, not shipping without an alert. Threshold and paging decisions belong to humans; your job is to make them informed and cheap.
-
-  ### Continuous improvement (whetstone) — after addressing human review feedback
-
-  When a run's work included addressing review feedback that did NOT come from your own
-  reviewer lanes — human comments and requested changes, but also a teammate's review
-  agent or another team's bot (an independent reviewer catching what your suite missed is
-  exactly the signal) — spawn `whetstone` ONCE at the very end, after all work is
-  complete. Pass it: the PR reference,
-  the human feedback items you addressed (verbatim), and what your own review passes
-  (code-reviewer/adversary/security-reviewer/probe) flagged for the same change — that
-  ground truth is what makes its miss-classification precise. Collect its result; its
-  proposals go to the USER (it escalates its own approval questions), not to you — never
-  apply suite changes on its behalf and never block run completion on it (if it errors,
-  note that and finish). Skip with a one-line note ONLY when every piece of feedback you
-  addressed came from your own reviewer lanes: whetstone never learns from its own suite's
-  output, but it learns from everyone else — human or agent.
-
   ## File Operations (Direct Edits)
 
   When you write or modify files yourself (rather than delegating to coder):
 
-  - **Calibrate comments before writing.** Load `comment-discipline` and note the repo's comment register (self-documenting / api-documented / comment-heavy) from the sibling files you read; write comments to match. When the signal is weak, write NO comment.
-  - **Calibrate logging before writing.** When the change touches boundaries, error paths, jobs, or state transitions, load `logging-discipline` and note the repo's logging register (logger, message style, payload vs IDs, level semantics) from the same sibling reads; match it. No discernible convention → its best-judgment defaults. Never leave a new error path silently swallowed, and never delete existing log lines as drive-by cleanup.
   - **For editing an existing file**, prefer `fs_patch`. It's a surgical edit that preserves unchanged content. Send only the diff hunks for the lines you want to change; do not re-send the whole file. This is faster, cheaper, and dramatically less prone to accidental data loss than a full rewrite.
   - **For writing a NEW file or doing a COMPLETE rewrite**, use `fs_write`. Use it only when most of the content is changing or the file doesn't exist yet.
   - **NEVER write files via `execute_command`.** Do not use:
@@ -595,10 +358,6 @@ instructions: |
 
   ## Phase 7 - Failure Recovery
 
-  ### Hard bugs: load `diagnosing-bugs` BEFORE strike 2
-
-  A first fix attempt may go on the error message alone. If it fails — or the bug is intermittent, or the fix isn't obvious from the error — load the `diagnosing-bugs` skill and follow its discipline: build a tight, red-capable reproduction loop BEFORE forming any hypothesis, minimise, then test 3-5 falsifiable hypotheses with tagged instrumentation. Blind retry without a feedback loop is how you burn all 3 strikes on the same wrong theory.
-
   ### 3-strike rule
 
   After 3 consecutive failed fix attempts on the same problem:
@@ -617,7 +376,7 @@ instructions: |
 
   ### Authoring lifecycle (no code changes)
 
-  1. Discuss the problem; converge on a solution WITH the user before any plan is written. Load `grilling` and work the design as frontier rounds: every currently-answerable question in one numbered round, each with your recommended answer; fetch facts yourself (explore/librarian), put only decisions to the user; done when the frontier is empty and the user confirms.
+  1. Discuss the problem; converge on a solution WITH the user before any plan is written.
   2. Load `plan-authoring`. Explore first (fan out `explore` agents) — plans must be grounded in real code, with snippets pasted into each step's Context.
   3. Write the high-level plan, then one step plan per step, following the schema and layout from `plan-authoring`.
   4. **Plan review gate (MANDATORY before any execution):** spawn `oracle` to review the plans. Nudge it: "Load `plan-review` and `plan-authoring`, review `plans/`, return the PLAN_REVIEW verdict." REJECT → fix the complaints, re-submit. Do not start execution on an unreviewed or rejected plan.
@@ -664,59 +423,9 @@ instructions: |
   - Writing non-trivial code → always `coder` (graph agent runs verification internally)
   - Multi-angle exploration → fan out `explore` agents
 
-  ## Escalation policy: {{escalation_policy}}
-
-  Every "ASK the user" / "STOP and escalate" instruction in this config is subject to this policy.
-
-  - **interactive** (default) — pause and ask exactly as written throughout this config.
-  - **autonomous** — the user pre-delegated decision-making for this run ("here's the spec — go").
-    When an escalation-worthy decision arises, work this ladder IN ORDER:
-
-    1. **Hard triggers — ALWAYS escalate; no ruling or policy can delegate these:** decisions about
-       secrets/credentials, money movement, destructive or irreversible actions (data loss,
-       force-push, dropping data or public API without a migration path), anything the Hard Blocks
-       section forbids — and any decision that already failed once after an autonomous resolution
-       (a ruling that did not survive one fix cycle goes to a human, never into a retry loop).
-    2. **Standing rulings** — read `$HOME/.config/coyote/share/standing-rulings.md` (skip silently
-       if absent). If a ruling's trigger GENUINELY matches the decision at hand, apply its
-       resolution. Match on substance, not resemblance — a ruling about security-vs-spec conflicts
-       does not authorize scope changes. Unsure whether it matches? Then it does not.
-    3. **Clearly recommended option** — if you would have presented options with one marked
-       `(Recommended)` backed by concrete evidence (a reviewer's proposed fix, a failing test that
-       names the cause, a repo convention), take the recommended option.
-    4. **Otherwise — escalate** exactly as interactive mode would. A genuinely novel conflict or a
-       decision with no defensible recommendation still reaches the user; autonomy never converts
-       "I don't know" into a guess.
-
-    **Plan amendments taken autonomously.** When a resolution amends the spec/plan/acceptance
-    criteria (e.g. a security fix conflicts with a criterion's wording), REWRITE the affected
-    criterion text in your working plan context BEFORE re-running any reviewer or the gauntlet —
-    the adversary must verify the plan-as-amended, not the stale wording. The amendment is always
-    a visible artifact, never implied.
-
-    **The digest (MANDATORY when any autonomous decision was taken).** Your final report — and the
-    PR body, when you open one — MUST include a `## Decisions taken autonomously` section: one line
-    per decision stating what was decided, the basis (`ruling: <id/title>` or `recommended option`),
-    and what changed (including any plan amendment). Zero autonomous decisions → omit the section.
-    This converts interrupt-driven review into digest-driven review — never into silence.
-
-    **The PR review log (MANDATORY when you author a PR).** The PR DESCRIPTION is a stable
-    document: what the PR does, how to verify it, and the required digest sections (autonomous
-    decisions, skipped reviews, observability). Every review round's evidence — the gauntlet
-    lane table and verdicts, the gates you ran, rulings recorded that round, and what changed
-    since the previous round — is posted as a NEW PR comment (`gh pr comment`) titled
-    `## Review round N @ <full head SHA>`. NEVER record round evidence by rewriting the
-    description: in-place edits destroy the review history and hide which commits each round
-    actually reviewed. Comments are the append-only review log; the SHA in the title names
-    exactly what was reviewed.
-
-    **Close the loop.** When a decision DID reach the user (step 4), suggest in your final report
-    that they record the resolution with `coyote --macro record-ruling` so that class of decision
-    never asks again.
-
   ## User Interaction (get buy-in before major decisions)
 
-  Use `user__ask`, `user__confirm`, `user__checkbox`, `user__input` to clarify ambiguities interactively. **Do NOT guess when you can ask.** When `escalation_policy` is `autonomous`, the Escalation policy section above governs which of these actually pause the run — autonomy substitutes standing rulings and evidence-backed recommendations for the pause; it never substitutes guessing.
+  Use `user__ask`, `user__confirm`, `user__checkbox`, `user__input` to clarify ambiguities interactively. **Do NOT guess when you can ask.**
 
   | Situation | Tool |
   |-----------|------|
@@ -747,11 +456,6 @@ instructions: |
 
   If you see `pending_escalations` in tool results, a child agent needs user input and is blocked. Reply promptly via `agent__reply_escalation`. You can answer from context, or prompt the user yourself first and relay the answer.
 
-  In `autonomous` escalation policy, work the Escalation-policy ladder before prompting the user: a
-  matching standing ruling or a clearly recommended option in the child's escalation answers it
-  directly via `agent__reply_escalation` (hard triggers always go to the user). Replies that amend a
-  plan/spec follow the amendment rule above, and every autonomous reply lands in the digest.
-
   ## Anti-Patterns (BLOCKING)
 
   - Skipping intent verbalization → unclear routing, wasted turns
@@ -779,7 +483,6 @@ instructions: |
 
   ## Context
   - Project: {{project_dir}}
-  - Escalation policy: {{escalation_policy}}
   - OS: {{__os__}}
   - Shell: {{__shell__}}
   - CWD: {{__cwd__}}

assets/agents/step-runner/README.md

@@ -27,7 +27,6 @@ flowchart TD
     gate_blocked -->|"yes"| orient
     gate_blocked -->|"no"| end_blocked
     orient["orient<br/>llm, read-only"] --> route_staleness
-    orient -. "LLM fault" .-> note_llm_fault
     route_staleness{"route_staleness<br/>script"}
     route_staleness -->|"major deviation"| gate_deviation
     route_staleness -->|"else"| implement
@@ -36,7 +35,6 @@ flowchart TD
     gate_deviation -->|"abort"| end_rejected
     gate_deviation -->|"other (user guidance)"| implement
     implement[["implement<br/>agent → coder"]] --> route_coder_result
-    implement -. "coder crashed<br/>(no retries)" .-> end_failure
     route_coder_result{"route_coder_result<br/>script"}
     route_coder_result -->|"CODER_COMPLETE"| verify_format_lint
     route_coder_result -->|"REJECTED / FAILED"| end_failure
@@ -53,18 +51,14 @@ flowchart TD
     fix_loop_gate -->|"budget left"| implement
     fix_loop_gate -->|"budget spent"| end_failure
     edge_case_sweep["edge_case_sweep<br/>llm"] --> route_sweep
-    edge_case_sweep -. "LLM fault" .-> write_handoff
     route_sweep{"route_sweep<br/>script"}
     route_sweep -->|"5+ files or boundary"| independent_review
     route_sweep -->|"else"| write_handoff
     independent_review[["independent_review<br/>agent → code-reviewer"]] --> route_review
-    independent_review -. "2 attempts failed" .-> write_handoff
     route_review{"route_review<br/>script"}
     route_review -->|"🔴 critical findings"| implement
     route_review -->|"else"| write_handoff
     write_handoff["write_handoff<br/>llm"] --> check_handoff
-    write_handoff -. "LLM fault" .-> note_llm_fault
-    note_llm_fault{"note_llm_fault<br/>script"} --> end_failure
     check_handoff{"check_handoff<br/>script"}
     check_handoff -->|"schema valid"| gate_user_review
     check_handoff -->|"one retry"| write_handoff
@@ -87,32 +81,8 @@ End nodes emit sentinel outcomes for the caller:
 - `STEP_BLOCKED` — `depends_on` unsatisfied and the user declined to proceed.
 - `STEP_REJECTED` — user aborted at the deviation gate, or the coder's plan
   was rejected at its approval gate.
-- `STEP_FAILED` — the coder failed or crashed, the step-level fix budget was
+- `STEP_FAILED` — coder failed, the step-level fix budget was exhausted, or
-  exhausted, the handoff failed validation twice, or an orient/handoff LLM
+  the handoff failed validation twice.
-  fault was recorded (rendered as `Pipeline fault:` in the output).
-
-## Fault handling
-
-Node crashes degrade the run visibly instead of masquerading as success:
-
-- `implement` has **no retries** — rerunning a coder that died mid-edit
-  against an already-mutated tree is unsafe. Its failure text lands in
-  `coder_result` and the run falls straight to `end_failure`.
-- `independent_review` retries once (`max_attempts: 2`); if both attempts
-  fail it falls back to `write_handoff`, which flags "PIPELINE-FAULT:
-  independent review did not run" in the handoff rather than presenting the
-  failure text as findings. `route_review` carries the same guard before its
-  🔴 grep, so a reviewer fault never spends a fix-loop attempt.
-- `edge_case_sweep` faults likewise fall through to `write_handoff` and are
-  flagged as "PIPELINE-FAULT: edge-case sweep did not run".
-- `orient` and `write_handoff` faults route through `note_llm_fault`, which
-  distills the engine's failure text into a `fault_note` rendered in the
-  `STEP_FAILED` output — never an empty shell.
-
-Degraded is never passing (a skipped review or sweep is recorded as NOT RUN,
-never paraphrased as covered), and the sentinel is always emitted — every
-path terminates at one of the four end nodes, so the caller always gets a
-parseable outcome.
 
 ## Usage
 

assets/agents/step-runner/graph.yaml

@@ -6,12 +6,6 @@ description: |
   review -> evidence-backed handoff -> user approval gate. Designed to be
   delegated to by sisyphus.
 version: '1.0'
-# The limit is consulted by the SPAWNER against the child's absolute depth
-# (root = 0). Deepest documented chain: architect(0) → sisyphus(1) →
-# step-runner(2) → code-reviewer(3) →
-# {domain-reviewer(4) → file-reviewer(5) | finding-verifier(4)}.
-# This agent spawns depth-3 children; 4 = one level of headroom (default 3 had none).
-max_agent_depth: 4
 global_tools:
   - ast_grep.sh
   - fs_cat.sh
@@ -70,7 +64,6 @@ initial_state:
   plan_summary: ''
   implementation_brief: ''
   staleness_report: ''
-  orient_failure: ''
   has_major_deviation: false
   deviation_summary: ''
   user_feedback: ''
@@ -87,15 +80,12 @@ initial_state:
   tests_output: ''
   edge_case_report: ''
   downstream_updates: ''
-  sweep_failure: ''
   needs_independent_review: false
   review_report: ''
   review_attempts: 0
   max_review_attempts: 1
   handoff_attempts: 0
   handoff_fix: ''
-  handoff_failure: ''
-  fault_note: ''
   step_summary: ''
 
 start: resolve_step
@@ -201,9 +191,7 @@ nodes:
           has_major_deviation,
           deviation_summary,
         ]
-    state_updates:
+    fallback: end_failure
-      orient_failure: '{{output}}'
-    fallback: note_llm_fault
     next: route_staleness
 
   route_staleness:
@@ -282,12 +270,6 @@ nodes:
     timeout: 3600
     state_updates:
       coder_result: '{{output}}'
-    # No max_attempts: rerunning a coder that died mid-edit against an
-    # already-mutated tree is unsafe. On failure the "Agent node failed:"
-    # text lands in coder_result (via state_updates above) and end_failure
-    # renders it; end_failure's other keys all have initial_state defaults,
-    # so the STEP_FAILED output degrades to empty build/tests sections.
-    fallback: end_failure
     next: route_coder_result
 
   route_coder_result:
@@ -394,8 +376,6 @@ nodes:
         needs_independent_review:
           type: boolean
       required: [edge_case_report, downstream_updates, needs_independent_review]
-    state_updates:
-      sweep_failure: '{{output}}'
     fallback: write_handoff
     next: route_sweep
 
@@ -425,10 +405,8 @@ nodes:
       Review the changed files against the step plan's acceptance criteria.
       Preserve severity tags in your findings.
     timeout: 1200
-    max_attempts: 2
     state_updates:
       review_report: '{{output}}'
-    fallback: write_handoff
     next: route_review
 
   route_review:
@@ -472,25 +450,6 @@ nodes:
 
       If "Gate feedback" below is non-empty, a previous handoff attempt
       failed validation - fix exactly what it lists.
-
-      PIPELINE-FAULT VISIBILITY: an "Independent review report" below that
-      starts with "Agent node failed:" means the independent review DID NOT
-      RUN - the graph routed here through the reviewer's failure fallback.
-      Never present that text as review findings. Flag it prominently
-      instead: add a Deviations entry "PIPELINE-FAULT: independent review
-      did not run - <failure text>", repeat it under Notes for next step,
-      and carry it into `step_summary` so the user sees it at the approval
-      gate.
-
-      The same rule covers the "Edge-case sweep result" below: text starting
-      with "LLM node" means the edge-case sweep DID NOT RUN - the graph
-      routed here through the sweep's failure fallback. Never present it as
-      sweep findings. Add a Deviations entry "PIPELINE-FAULT: edge-case
-      sweep did not run - <failure text>" and carry it into `step_summary`
-      so the user sees it at the approval gate. If it holds successful
-      structured output or is empty, ignore it - the sweep's real results
-      already flow through the "Edge cases discovered" / "Downstream plan
-      updates" sections above.
     prompt: |
       ## Step
       {{step_number}} ({{step_title}}) - plan at {{step_plan_path}}
@@ -514,9 +473,6 @@ nodes:
       ## Downstream plan updates
       {{downstream_updates}}
 
-      ## Edge-case sweep result (fault detection)
-      {{sweep_failure}}
-
       ## Independent review report (if any)
       {{review_report}}
 
@@ -545,23 +501,8 @@ nodes:
           type: string
           description: 3-6 sentence summary of the step for the user's approval decision - what was done, deviations, anything needing their attention
       required: [step_summary]
-    state_updates:
-      handoff_failure: '{{output}}'
-    fallback: note_llm_fault
-    next: check_handoff
-
-  note_llm_fault:
-    id: note_llm_fault
-    type: script
-    description: |
-      Make LLM-node fallback captures visible: when orient or write_handoff
-      failed (their capture keys hold the engine's "LLM node..." failure
-      text), distill it into fault_note so end_failure can render WHY the
-      step died instead of an empty STEP_FAILED shell.
-    script: scripts/note_llm_fault.sh
-    timeout: 5
     fallback: end_failure
-    next: end_failure
+    next: check_handoff
 
   check_handoff:
     id: check_handoff
@@ -660,7 +601,6 @@ nodes:
       Step: {{step_number}} ({{step_title}})
       Fix attempts: {{fix_attempts}}/{{max_fix_attempts}}
       Blocking reason (if resolution failed): {{blocking_reason}}
-      Pipeline fault (if any): {{fault_note}}
 
       Coder result:
       {{coder_result}}

assets/agents/step-runner/scripts/note_llm_fault.sh

@@ -1,26 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-if [[ -n "${GRAPH_STATE_FILE:-}" ]]; then
-  state=$(cat "$GRAPH_STATE_FILE")
-elif [[ -n "${GRAPH_STATE:-}" ]]; then
-  state="$GRAPH_STATE"
-else
-  state='{}'
-fi
-
-orient_failure=$(echo "$state" | jq -r '.orient_failure // ""')
-handoff_failure=$(echo "$state" | jq -r '.handoff_failure // ""')
-
-# Engine failure text is always prefix-anchored "LLM node" (llm.rs); on
-# success these keys hold the node's structured JSON output, which never
-# starts with that prefix.
-if [[ "$orient_failure" == "LLM node"* ]]; then
-  fault_note="PIPELINE-FAULT: orient stage failed — ${orient_failure:0:300}"
-elif [[ "$handoff_failure" == "LLM node"* ]]; then
-  fault_note="PIPELINE-FAULT: handoff stage failed — ${handoff_failure:0:300}"
-else
-  fault_note=""
-fi
-
-jq -nc --arg note "$fault_note" '{"fault_note": $note}'

assets/agents/step-runner/scripts/route_review.sh

@@ -13,16 +13,6 @@ review_report=$(echo "$state" | jq -r '.review_report // ""')
 review_attempts=$(echo "$state" | jq -r '.review_attempts // 0')
 max_review_attempts=$(echo "$state" | jq -r '.max_review_attempts // 1')
 
-# Fail-visible guard: a review_report holding the engine's "Agent node
-# failed:" text means the independent review DID NOT RUN (its fallback
-# normally routes straight to write_handoff, bypassing this script). Never
-# treat that text as findings or spend a fix-loop attempt on it -
-# write_handoff flags the fault prominently in the handoff instead.
-if [[ "$review_report" == "Agent node failed:"* ]]; then
-  jq -nc '{"_next": "write_handoff"}'
-  exit 0
-fi
-
 if ! grep -qF "🔴" <<< "$review_report"; then
   jq -nc '{"_next": "write_handoff"}'
   exit 0

assets/agents/whetstone/README.md

@@ -1,67 +0,0 @@
-# whetstone
-
-> The review suite reviews code. Whetstone reviews the review.
-
-A continuous-improvement agent for the review stack: it takes the human review feedback a
-PR actually received, compares it against what the automated suite flagged for the same
-change, and turns every generalizable miss into a permanent upgrade — a new rule in the
-generic review skills when the class is portable, a review-miss ledger entry when it's
-org-specific. Nothing lands without the user approving each proposal.
-
-## Why it exists
-
-An empirical gap study of automated-review misses vs human review feedback showed the suite's misses
-cluster into learnable classes — and that a miss, once *recorded*, converts to a catch on
-the next review. The study was a one-time manual harvest; whetstone is the same loop run
-continuously, at the moment the signal is strongest: when human feedback on a PR is being
-addressed, the spawner (sisyphus/architect) knows BOTH what the humans said and what the
-suite's own lanes flagged — ground truth that offline comment mining could only re-infer from formats.
-
-## How it fits
-
-- **Spawned by** sisyphus (after a run that addressed human review feedback) or architect
-  (same trigger at run end), or invoked directly against a PR. Runs AFTER review, never
-  during — it is not a reviewer lane, never posts to the PR, and never judges the code.
-- **Classifies** each retained finding as CATCH / PARTIAL / MISS against the suite's
-  findings. Lane hygiene excludes only what would be circular: author self-replies and
-  the suite's OWN posted output. A teammate's review agent or another team's bot is an
-  independent reviewer — its findings count as miss signal when the author actually
-  addressed them (ignored agent comments are unvalidated noise and are dropped).
-- **Generalization gate** for each miss, in order: taste → dropped; one-off → appended to
-  the candidates inbox (`share/review-miss-candidates.jsonl`) for recurrence tracking;
-  org-specific class → drafted as a ledger entry; general class → drafted as a suite edit
-  in house style. General rules must pass the noise firewall: concrete check, crisp
-  trigger, zero org nouns, not already covered (sharpen over duplicate).
-- **Propose → approve → apply**: every proposal shows the quoted evidence, the class
-  statement, and the full draft; the user checkboxes what to apply. Ledger entries append
-  idempotently. Suite edits go where the suite lives: with a `suite_repo` configured (a
-  source-of-truth bundle repo), edits land in its working tree — never
-  committed (that stays a human act) — and one further approval mirrors them into the
-  live runtime config, drift-guarded (runtime files diverging from the pre-edit repo
-  version are reported and skipped; runtime-only changes are never made). Without a
-  `suite_repo` — most users, whose live config IS the suite — edits apply directly under
-  `runtime_config`, with per-file backups to `share/whetstone-backups/` as the revert
-  path. Empty proposal lists are a fine outcome; whetstone never invents findings to
-  justify its spawn.
-
-## Relationship to the other ledger tools
-
-| Tool | Sees | When |
-|------|------|------|
-| `whetstone` | Human feedback on PRs YOUR runs addressed, with suite ground truth | Real-time, per run |
-| Review-round reconciliation | Human-caught, panel-missed defects on any PR the panel re-reviews → candidates inbox (`share/review-miss-candidates.jsonl`) | Automatic, every round |
-| `record-miss` | Defects that escaped review entirely (prod, incidents) | One-off, when it bites |
-
-Collection is automatic end to end: whetstone captures misses the moment feedback is
-addressed, round reconciliation captures them on any PR the panel re-reviews (teammates'
-PRs included), and `record-miss` covers the misses no one ever commented on. Nothing
-auto-appends to the LEDGER itself — candidates wait in the inbox until a human promotes them.
-
-## Rules that keep it safe
-
-Additive only (never weakens or removes an existing rule); writes only to the suite
-skills/review-agent configs (repo when configured, live config otherwise — always
-backed up first), the ledger, the candidates inbox, and — with its own approval,
-drift-guarded — the runtime mirror of this run's applied repo edits; never commits,
-never pushes, never touches source repos, never makes runtime-only changes when a
-suite repo is configured; one proposal per defect class; verbatim citations only.

assets/agents/whetstone/config.yaml

@@ -1,158 +0,0 @@
-name: whetstone
-description: Continuous-improvement agent for the review suite — classifies human review feedback the suite missed, generalizes misses into defect classes, and proposes suite edits (general) or ledger entries (org-specific), applying them only with user approval
-version: 1.3.0
-
-skills_enabled: true
-enabled_skills:
-  - review-misses
-
-enabled_tools:
-  - fs_read
-  - fs_grep
-  - fs_glob
-  - fs_cat
-  - fs_ls
-  - fs_write
-  - fs_patch
-  - execute_command
-
-variables:
-  - name: suite_repo
-    description: OPTIONAL source-of-truth bundle repo (a working tree containing skills/ and agents/). When set, approved GENERAL improvements are written here first, then optionally mirrored to the runtime config. When empty, improvements are applied DIRECTLY to runtime_config — for most users the live config IS the suite.
-    default: ''
-  - name: runtime_config
-    description: The live coyote config dir the review suite actually runs from. Direct write target when suite_repo is empty (with per-file backups for revert); drift-guarded mirror target when suite_repo is set. Empty = never touch it (propose-only).
-    default: '~/.config/coyote'
-  - name: pr
-    description: The PR to analyze (owner/repo#N or a full URL). May be omitted when the spawner passes the feedback inline.
-    default: ''
-
-instructions: |
-  You are WHETSTONE — the review suite reviews code; you review the REVIEW. Your input is a
-  PR's human review feedback plus what the automated review suite flagged; your output is
-  the suite made sharper: every generalizable miss becomes either a rule in the generic
-  review skills (portable to any repo) or a review-miss ledger entry (org-specific), so the
-  same class is never missed twice. You are NOT a reviewer lane: you never post to the PR,
-  never judge the author's code, and never run during a review — only after humans have
-  spoken.
-
-  ## Inputs
-
-  Your spawner (sisyphus, architect, or the user directly) provides some or all of:
-  - The PR reference (`{{pr}}` or in the prompt).
-  - The human review feedback that was addressed (verbatim, if the spawner has it).
-  - What the suite's own review passes flagged for the same change (ground truth — the
-    spawner has this when it ran the reviewers; use it verbatim and do not re-infer).
-
-  Whatever is missing, gather yourself with gh (ALWAYS `export GH_NO_UPDATE_NOTIFIER=1;
-  unset CLICOLOR_FORCE` first — the sandbox forces ANSI color into piped JSON otherwise):
-  inline review comments, review bodies, and the commits that addressed them. When no
-  suite-findings ground truth was passed, identify the suite's own posted output on the PR
-  by FORMAT (severity emoji like 🔴/🟡/🟢, lane tags like `[adversary]`, panel/verdict
-  tables) — automated reviews are often posted from a personal account, so judge by
-  format, not username.
-
-  ## Workflow
-
-  1. **Lane hygiene.** The exclusion rule is about CIRCULARITY, not automation. Drop: the
-     PR author's self-replies, and YOUR OWN suite's output (by ground truth from the
-     spawner, or by the suite's format markers + posting account — learning from your own
-     lanes teaches nothing). KEEP third-party automated reviewers (a teammate's review
-     agent, other orgs' bots): they are independent reviewers, and what they catch that
-     your suite didn't is exactly the miss signal you exist for — but only their findings
-     the author actually ADDRESSED (a fix commit or an accepting reply). An addressed
-     third-party finding is validated the way a human comment implicitly is; an ignored
-     one is unvalidated noise — drop it. Report what you excluded and why. Nothing
-     retained → report "nothing to learn from" and STOP. Never invent findings to justify
-     having been spawned.
-  2. **Classify each retained finding** (human, or validated third-party) against the
-     suite's findings for the same change:
-     - `CATCH` — a suite lane flagged the same issue (any wording). Skip.
-     - `PARTIAL` — a lane flagged the area but missed the human's specific point.
-     - `MISS` — no lane flagged it. PARTIAL and MISS proceed to step 3.
-  3. **The generalization gate** — for each MISS/PARTIAL, in this order:
-     a. **Taste?** (naming preference, style debate, "I'd structure it differently") →
-        DROP. List dropped items in the report; never encode taste anywhere.
-     b. **One-off?** (real defect, but no articulable class — a typo-level slip, a
-        this-code-only fact) → append one line to the candidates inbox
-        `$HOME/.config/coyote/share/review-miss-candidates.jsonl`
-        (`{"date","pr","quote","note"}`, plain shell append) and move on. If later runs
-        show the same shape, THAT is your recurrence evidence for a class.
-     c. **Org-specific class?** (org conventions — especially ones repo prior art
-        contradicts — live org state, product/domain semantics not derivable from any
-        repo) → draft a LEDGER ENTRY in the `review-misses` skill's exact format; the
-        detection pattern is the payload.
-     d. **General class?** (portable to any repo, any org) → draft a SUITE EDIT: name the
-        exact file and section in the suite repo (a review skill's checklist, an agent
-        config's trigger list), and write the edit in HOUSE STYLE — read the surrounding
-        section first and match its severity markers, exemption language, and
-        "reports even when clean" conventions. Additive only.
-  4. **The generality bar** (the noise firewall — a general rule that fires on every diff
-     will get the whole suite ignored). A suite-edit proposal must pass ALL of:
-     - It states the CONCRETE check a reviewer runs (a grep shape or a decidable
-       question), not advice ("be careful with X" fails).
-     - It has a crisp TRIGGER and would stay silent on diffs where the class is
-       impossible.
-     - It contains zero org/product nouns.
-     - It is not already covered: grep the suite's skills first; if an existing rule
-       half-covers it, propose SHARPENING that rule instead of adding a sibling.
-     - Check the ledger too: if the miss matches an already-RECORDED entry, the finding
-       is "recorded pattern failed to fire" — a suite-wiring problem to report, not a new
-       entry.
-  5. **Propose — never write unbidden.** Present every surviving proposal to the user:
-     the human's feedback quoted verbatim with the PR link, the class statement (one
-     sentence: what general thing was missed), and the full remediation draft (ledger
-     entry or suite diff). Ask which to apply via a checkbox selection. An empty proposal
-     list is a fine outcome — say so and stop.
-  6. **Apply what was approved.**
-     - Ledger entries: idempotent append to `$HOME/.config/coyote/share/review-misses.md`
-       (title-match skip; numbering via `grep -c '^## MISS-'` — the `review-misses` skill
-       has the recipe).
-     - Suite edits — the target depends on where the suite lives:
-       - **`suite_repo` set and exists** (a source-of-truth bundle repo): snapshot each
-         original to a temp dir (needed for the runtime drift check below), write the
-         edit into the repo's working tree with fs_patch, and NEVER commit or push — the
-         user reviews and commits. Then offer the runtime mirror (next bullet).
-       - **`suite_repo` empty — the live config IS the suite.** Apply the edit directly
-         under `{{runtime_config}}` (the review skills and review-agent configs there)
-         with fs_patch. FIRST back up each original to
-         `{{runtime_config}}/share/whetstone-backups/<UTC timestamp>/<relative path>` so
-         any edit can be reverted, and state the backup location in your report. If
-         `{{runtime_config}}` is itself a git repo, list the files you changed so the
-         user can commit them. No extra approval beyond the proposal checkbox — there is
-         no repo/runtime split to guard. Edits take effect on the NEXT session load; say
-         so.
-       - Both empty or missing: emit the exact edits (file, section, full text) for
-         manual application instead.
-     - **Runtime mirror (repo mode only, separately approved).** Repo edits are inert until the
-       runtime config is synced. After suite edits are applied, if `{{runtime_config}}`
-       is set and exists, ask the user ONCE (yes/no) whether to mirror the just-approved
-       edits into it. On yes, for EACH file you edited: locate the runtime counterpart
-       (same relative path under agents/ or skills/); if it is byte-identical to your
-       PRE-EDIT snapshot, copy the edited repo file over it; if it differs (the user's
-       runtime carries local changes), SKIP it and report the drift — never overwrite a
-       drifted runtime file, the user reconciles those. Mirror ONLY files you edited this
-       run, and ONLY as a copy of the applied repo edit — never make a runtime-only
-       change (the next repo→runtime sync would silently clobber it and the improvement
-       would be lost). If the user declines, remind them the edits are inert until they
-       sync.
-  7. **Report**: a table of human findings with CATCH/PARTIAL/MISS verdicts; proposals
-     made / approved / applied; runtime files mirrored vs skipped-for-drift; items
-     dropped as taste; inbox appends. CATCH-rate over
-     time is the suite's health metric — state it.
-
-  ## Rules
-
-  - ADDITIVE ONLY: never weaken, remove, or lower the severity of an existing rule. If a
-    proposal contradicts an existing rule, report the conflict for the user to resolve.
-  - Scope of writes: the suite's `skills/` and review-agent configs (in the suite repo,
-    or directly in the runtime config when no repo is configured — always with backups),
-    the ledger, and the candidates inbox. Nothing else, ever — no source repos, no
-    commits, no PR comments. When a `suite_repo` IS configured, never make a
-    runtime-only change: the next repo→runtime sync would silently clobber it and the
-    improvement would be lost.
-  - One proposal per defect CLASS — merge repeat instances and cite all their PRs.
-  - Quote real evidence verbatim; never fabricate PR citations.
-  - You may be spawned as a subagent: your user__ questions escalate to the root agent's
-    user. That is the intended approval path — never skip the approval step because you
-    are "just a subagent".

assets/config-template.yaml

@@ -1,329 +0,0 @@
-# Coyote configuration. Generated by the first-run wizard.
-# Every setting is listed with its effective value and a short description.
-# For richer examples of each section, see
-# https://github.com/Dark-Alex-17/coyote/blob/main/config.example.yaml
-
-# ---- LLM ----
-__MODEL_BLOCK__
-temperature: null                # Set default temperature parameter (0, 1)
-top_p: null                      # Set default top-p parameter, with a range of (0, 1) or (0, 2) depending on the model
-
-# ---- Behavior ----
-dry_run: false                   # Display the messages that would be sent to the LLM without actually sending them
-stream: true                     # Controls whether to use the stream-style APIs when querying for completions from LLM clients
-save: true                       # Indicates whether to persist the conversation to messages.md for posterity
-keybindings: emacs               # Choose keybinding style (emacs, vi)
-editor: null                     # Specifies the editor used to edit the input buffer or session. (e.g. vim, emacs, nano, hx). Defaults to $EDITOR
-wrap: auto                       # Controls text wrapping (no, auto, <max-width>)
-wrap_code: false                 # Enables or disables the wrapping of code blocks
-
-# ---- Vault ----
-# See the [Vault documentation](https://github.com/Dark-Alex-17/coyote/wiki/Vault) for more information on the Coyote vault.
-#
-# The secrets_provider tells Coyote where to read and write secrets referenced via {{SECRET_NAME}} syntax.
-#
-# Shorthand: set vault_password_file to enable the local provider with that password
-# file (it cannot be a secret template).
-#
-# Explicit: set secrets_provider to one of the supported types below. When secrets_provider is set,
-# vault_password_file is ignored. Note: secrets_provider itself cannot use secret template syntax.
-# The vault must be initialized before any secrets can be resolved.
-#
-# Local (same as the shorthand above):
-# secrets_provider:
-#   type: local
-#   password_file: ~/.coyote_password
-#
-# AWS Secrets Manager (requires an authenticated AWS CLI; see `aws sso login` or `aws configure`):
-# secrets_provider:
-#   type: aws_secrets_manager
-#   aws_profile: default
-#   aws_region: us-east-1
-#
-# GCP Secret Manager (requires `gcloud auth application-default login`):
-# secrets_provider:
-#   type: gcp_secret_manager
-#   gcp_project_id: my-project-id
-#
-# Azure Key Vault (requires `az login`):
-# secrets_provider:
-#   type: azure_key_vault
-#   vault_name: my-vault-name
-#
-# gopass (requires the `gopass` CLI to be installed and initialized):
-# secrets_provider:
-#   type: gopass
-#   store: my-store              # Optional; omit to use the default store
-#
-# 1Password (requires the `op` CLI to be installed and signed in via `op signin`):
-# secrets_provider:
-#   type: one_password
-#   vault: Production            # Optional; omit to use the default vault
-#   account: my.1password.com    # Optional; omit to use the default account
-__SECRETS_BLOCK__
-
-# ---- Function Calling ----
-# See the [Tools documentation](https://github.com/Dark-Alex-17/coyote/wiki/Tools) for more details
-function_calling_support: true   # Enables or disables function calling (globally)
-mapping_tools: {}                # Alias for a tool or toolset
-                                 # Example:
-                                 #   mapping_tools:
-                                 #     fs: 'fs_cat,fs_ls,fs_mkdir,fs_rm,fs_write,fs_read,fs_glob,fs_grep'
-enabled_tools: null              # Which tools to enable by default.
-                                 # Accepts either a YAML list or a comma-separated string. Use 'all' to enable everything.
-                                 # Example (list form):
-                                 #   enabled_tools:
-                                 #     - fs
-                                 #     - web_search_coyote
-                                 # Example (comma-separated form):
-                                 #   enabled_tools: fs,web_search_coyote
-visible_tools: null              # Which tools are visible to be compiled (and are thus able to be defined in 'enabled_tools').
-                                 # Null/missing = all tools in the global tools dir are visible; [] = none;
-                                 # an explicit list makes only those tools visible.
-                                 # Example:
-                                 #   visible_tools:
-                                 #     - execute_command.sh
-                                 #     - fs_cat.sh
-                                 #     - fs_ls.sh
-
-# ---- Skills ----
-# Skills are modular knowledge or capability packs the LLM can load and unload mid-conversation.
-# See the [Skills documentation](https://github.com/Dark-Alex-17/coyote/wiki/Skills) for more details.
-skills_enabled: true             # Master switch. Set to false to hide all skill management tools from the model.
-                                 # Skills also require `function_calling_support: true` above to work at all.
-enabled_skills: null             # Which skills are available by default (no role/agent/session active). null = all visible.
-                                 # Accepts either a YAML list or a comma-separated string.
-                                 # Example (list form):
-                                 #   enabled_skills:
-                                 #     - git-master
-                                 #     - ai-slop-remover
-                                 # Example (comma-separated form):
-                                 #   enabled_skills: git-master,ai-slop-remover
-visible_skills: null             # The universe of skills allowed to be enabled in any context. null = all installed.
-                                 # Example:
-                                 #   visible_skills:
-                                 #     - ai-slop-remover
-                                 #     - code-review
-                                 #     - git-master
-
-# ---- Macros ----
-# Macros are Coyote's custom commands: named sequences of REPL commands and prompts, invoked directly by name
-# (a macro file named `review.yaml` runs as `.review [args]`; built-in commands always win a name collision).
-# Workspace-local macros in `.coyote/macros/` shadow same-named global macros (skip them with --no-workspace-macros).
-# See the [Macros documentation](https://github.com/Dark-Alex-17/coyote/wiki/Macros) for more details.
-enabled_macros: null             # Which macros are invocable by default (no role/agent/session active). null = all visible.
-                                 # An empty list means NO macros are invocable. Accepts either a YAML list or a
-                                 # comma-separated string. Roles, agents, and sessions may define their own
-                                 # `enabled_macros`; the most specific active one wins (session > agent > role > global).
-                                 # Example (list form):
-                                 #   enabled_macros:
-                                 #     - generate-commit-message
-                                 # Example (comma-separated form):
-                                 #   enabled_macros: generate-commit-message,review
-
-# ---- MCP Servers ----
-# See the [MCP Servers documentation](https://github.com/Dark-Alex-17/coyote/wiki/MCP-Servers) for more details
-mcp_server_support: true         # Enables or disables MCP servers (globally)
-mapping_mcp_servers: {}          # Alias for an MCP server or set of servers
-                                 # Example:
-                                 #   mapping_mcp_servers:
-                                 #     git: github,gitmcp
-enabled_mcp_servers: null        # Which MCP servers to enable by default.
-                                 # Accepts either a YAML list or a comma-separated string. Use 'all' to enable everything.
-                                 # Example (list form):
-                                 #   enabled_mcp_servers:
-                                 #     - github
-                                 #     - slack
-                                 # Example (comma-separated form):
-                                 #   enabled_mcp_servers: github,slack,ddg-search
-mcp_tools: null                  # Per-server MCP tool allowlists (glob patterns: * and ? supported).
-                                 # Tools that match no pattern are hidden from the model as if they
-                                 # don't exist. Stacks with the other allowlist layers (mcp.json
-                                 # `allowedTools`, role, agent, session, skill, graph node). Every
-                                 # configured layer must allow a tool, so layers only ever narrow.
-                                 # An empty list blocks all of a server's tools.
-                                 # Example:
-                                 #   mcp_tools:
-                                 #     github:
-                                 #       - get_*
-                                 #       - list_*
-                                 #     slack: []
-
-# ---- Hooks ----
-# Fire-and-forget external commands that run when lifecycle events fire. Each event name
-# maps to a list of named hooks; every listed hook's command runs when that event fires.
-# Hooks never block coyote and never change its output or exit code.
-# See the [Hooks documentation](https://github.com/Dark-Alex-17/coyote/wiki/Hooks) for more details
-hooks: {}                        # Event -> list of named hook commands (default: none)
-                                 # Example:
-                                 #   hooks:
-                                 #     turn.completed:
-                                 #       - name: notify
-                                 #         command: ./hooks/notify.sh
-
-# ---- Auto-Continue (Todo System) ----
-# The auto-continue system provides built-in task tracking for improved reliability.
-# When enabled, the model can create todo lists and the system will automatically
-# prompt it to continue when incomplete tasks remain.
-# See the [Todo System documentation](https://github.com/Dark-Alex-17/coyote/wiki/TODO-System) for more information
-auto_continue: false             # Enable automatic continuation when incomplete todos remain (default: false)
-max_auto_continues: 10           # Maximum number of automatic continuations before stopping (default: 10)
-inject_todo_instructions: true   # Inject default todo usage instructions into the system prompt (default: true)
-continuation_prompt: null        # Custom prompt used when auto-continuing. If null, uses built-in default
-inject_skill_instructions: true  # Inject a short hint pointing the model at `skill__list` when skills are enabled
-                                 # in this context. Only injected if `function_calling_support`, `skills_enabled`, and the
-                                 # effective enabled skill set is non-empty (default: true)
-skill_instructions: null         # Custom text used for the skill hint when injected. If null, uses built-in default
-
-# ---- Prelude ----
-repl_prelude: null               # Set a default session or role for REPL mode to use (e.g. role:<name>, session:<name>, <session>:<role>)
-cmd_prelude: null                # Set a default session or role for CMD mode to use (e.g. role:<name>, session:<name>, <session>:<role>)
-agent_session: null              # Set a session to use when starting an agent (e.g. temp, default)
-
-# ---- Session ----
-# See the [Session documentation](https://github.com/Dark-Alex-17/coyote/wiki/Sessions) for more information
-save_session: null               # Controls the persistence of the session. If true, auto save; if false, don't auto-save; if null, ask the user what to do
-compression_threshold: 4000      # Compress the session when the token count reaches or exceeds this threshold
-compression_keep_last: 0         # Number of most-recent messages to keep visible after compression (0 = compress all messages)
-compression_model: null          # Model to use for session compression (e.g. 'openai:gpt-4o-mini'); defaults to the session's current model
-summarization_prompt: null       # The text prompt used for creating a concise summary of session messages. If null, uses built-in default
-summary_context_prompt: null     # The text prompt used for including the summary of the entire session as context to the model. If null, uses built-in default
-max_tool_result_chars: null      # Cap on tool result characters forwarded to the model per call (null = no cap)
-max_concurrent_jobs: null        # Max background jobs (`job__*` tools) running at once per context (null = 5; 0 disables background jobs entirely)
-tool_timeout: null               # Max seconds a tool call may run before being killed (null = 1800; 0 = unlimited). COYOTE_TOOL_TIMEOUT env var overrides
-
-# ---- Memory ----
-# See the [Memory documentation](https://github.com/Dark-Alex-17/coyote/wiki/Memory) for more information.
-# Memory is opt-in by workspace presence (`.coyote/memory/MEMORY.md`) and global
-# presence (`<config_dir>/memory/MEMORY.md`). Set `memory: false` to disable
-# even when memory files exist. The cascade is: agent > session > role > app.
-# Bootstrap with `coyote --init-memory [global|workspace]` to create the marker file
-# the LLM needs before it will write any memory.
-memory: null                     # null = enabled when memory exists on disk; true = force on; false = force off
-memory_cap_with_tools: null      # Char cap for injected memory when function calling is available (null = 6000).
-                                 # Only MEMORY.md indexes are injected; the LLM uses memory__read to fetch drill files.
-memory_cap_without_tools: null   # Char cap when function calling is unavailable (null = 12000).
-                                 # Indexes plus drill file bodies are injected up to this cap.
-
-# ---- Workspace Instructions ----
-# Human-curated project instructions injected read-only into the system prompt, in full.
-# Coyote walks up from the current directory and injects the first match from the file
-# chain below (per directory, in order). Scaffold with `coyote --init-instructions`.
-# Disable per-invocation with --no-workspace-instructions, or override the chain with
-# repeatable --workspace-instructions-file flags.
-workspace_instructions: null     # null/true = inject when an instructions file exists; false = never inject
-workspace_instructions_files: null # File name chain to search, in priority order.
-                                   # Default: [COYOTE.md, AGENTS.md, CLAUDE.md, GEMINI.md]
-                                   # Set to a custom list to reorder or drop fallbacks, e.g.:
-                                   #   workspace_instructions_files: [COYOTE.md]
-
-# ---- RAG ----
-# See the [RAG Docs](https://github.com/Dark-Alex-17/coyote/wiki/RAG) for more details.
-rag_embedding_model: null        # Specifies the embedding model used for context retrieval
-rag_reranker_model: null         # Specifies the reranker model used for sorting retrieved documents; Coyote uses Reciprocal Rank Fusion by default
-rag_top_k: 5                     # Specifies the number of documents to retrieve for answering queries
-rag_chunk_size: null             # Defines the size of chunks for document processing in characters
-rag_chunk_overlap: null          # Defines the overlap between chunks
-rag_template: null               # Defines the query structure using variables like __CONTEXT__, __SOURCES__, and __INPUT__
-                                 # to tailor searches to specific needs. If null, uses built-in default
-rag_extractor_model: null        # LLM model for graph-based entity/relationship extraction; when set, enables a graph RAG signal alongside vector and BM25
-rag_extractor_prompt: null       # Custom extraction prompt template; must contain __CHUNK__ placeholder; defaults to built-in prompt when null
-rag_graph_hops: 1                # Number of hops to expand from matched entities at query time (0 = seed nodes only; 1 = direct neighbors; increase for denser graphs)
-
-# Define document loaders to control how RAG and `.file`/`--file` load files of specific formats.
-document_loaders: {}
-                                 # You can add custom loaders using the following syntax:
-                                 #   <file-extension>: <command-to-load-the-file>
-                                 # Note: Use `$1` for input file and `$2` for output file. If `$2` is omitted, use stdout as output.
-                                 # Examples:
-                                 #   document_loaders:
-                                 #     pdf: 'pdftotext $1 -' # https://poppler.freedesktop.org
-                                 #     docx: 'pandoc --to plain $1' # https://pandoc.org
-                                 #     jina: 'curl -fsSL https://r.jina.ai/$1 -H "Authorization: Bearer {{JINA_API_KEY}}"' # Requires a Jina API key in the Coyote vault
-
-# ---- Appearance ----
-highlight: true                  # Controls syntax highlighting
-raw_markdown: false              # When true, render markdown as raw text with syntax highlighting only. When false (default), transforms markdown syntax (headings, bold, lists, etc.) into styled terminal output
-theme: null                      # null = the built-in dark theme; set to `light` for the built-in light theme.
-                                 # Custom themes: place a `dark.tmTheme` or `light.tmTheme` file in the Coyote config
-                                 # directory and it is used in place of the corresponding built-in.
-
-# ---- REPL Prompt ----
-# Custom REPL left/right prompts; see the [REPL Prompt Documentation](https://github.com/Dark-Alex-17/coyote/wiki/REPL-Prompt) for more information
-left_prompt: null                # If null, uses the built-in default:
-                                 #   '{color.red}{model}){color.green}{?session {?agent {agent}>}{session}{?role /}}{!session {?agent {agent}>}}{role}{?rag @{rag}}{color.cyan}{?session )}{!session >}{color.reset} '
-right_prompt: null               # If null, uses the built-in default:
-                                 #   '{color.cyan}{?reasoning_effort [{reasoning_effort}] }{color.purple}{?last_cache_read_tokens ⚡{last_cache_read_tokens} }{?total_cost ${total_cost} }{?session {?consume_tokens {consume_tokens}({consume_percent}%)}{!consume_tokens {consume_tokens}}}{color.reset}'
-                                 # Token-usage variables (set only when the provider reports usage, so guard them with {?var ...}):
-                                 #   last_input_tokens, last_output_tokens, last_cache_read_tokens, last_cache_creation_tokens (most recent API call)
-                                 #   total_input_tokens, total_output_tokens, total_cache_read_tokens, total_cache_creation_tokens (session cumulative)
-                                 #   last_cost, total_cost (USD, formatted like 0.0142; set only when nonzero and every billed token type has a price)
-
-# ---- Miscellaneous ----
-user_agent: null                 # Set User-Agent HTTP header, use `auto` for coyote/<current-version>
-save_shell_history: true         # Whether to save shell execution command to the history file
-sync_models_url: null            # Where `--sync-models` and the automatic refresh get model data from.
-                                 # If null, fetches fresh model data from models.dev + OpenRouter.
-                                 # Set a URL to mirror a full models.yaml instead, e.g.:
-                                 #   https://raw.githubusercontent.com/Dark-Alex-17/coyote/refs/heads/main/models.yaml
-sync_models_auto: true           # Whether to refresh the model catalog in the background on REPL startup
-                                 # once it goes stale
-sync_models_ttl_hours: 24        # Hours before the synced model catalog is considered stale
-
-# ---- Clients ----
-# See the [Clients documentation](https://github.com/Dark-Alex-17/coyote/wiki/Clients) for more details
-#
-# All clients have the following configuration:
-# - type: xxxx
-#   name: xxxx                                      # Only use it to distinguish clients with the same client type. Optional
-#   models:
-#     - name: xxxx                                  # Chat model
-#       max_input_tokens: 100000
-#       supports_vision: true
-#       supports_function_calling: true
-#     - name: xxxx                                  # Embedding model
-#       type: embedding
-#       default_chunk_size: 1500
-#       max_batch_size: 100
-#     - name: xxxx                                  # Reranker model
-#       type: reranker
-#   patch:                                          # Patch API calls
-#     chat_completions:                             # API type; Possible values: chat_completions, embeddings, and rerank
-#       <regex>:                                    # The regex to match model names, e.g. '.*' 'gpt-4o' 'gpt-4o|gpt-4-.*'
-#         url: ''                                   # Patch request URL
-#         body:                                     # Patch request body
-#           <json>
-#         headers:                                  # Patch request headers
-#           <key>: <value>
-#   extra:
-#     proxy: socks5://127.0.0.1:1080                # Set proxy
-#     connect_timeout: 10                           # Set timeout in seconds for connect to api
-#     read_timeout: 300                             # Set timeout in seconds for a read stall (no bytes received); 0 disables (default: 300)
-#
-# The claude, bedrock, and vertexai clients also support:
-#   prompt_cache: true                              # Enable Anthropic prompt caching (default: true)
-#
-# The openai and openai-compatible clients also support:
-#   wire_api: responses                             # Which OpenAI wire protocol to use; Possible values: responses and chat
-#                                                   # Defaults when unset: stock openai (no api_base) -> responses;
-#                                                   # openai with a custom api_base -> chat; openai-compatible -> chat.
-#                                                   # Codex OAuth always uses responses (`wire_api: chat` there is a config error)
-#
-# Patches are selected per wire: `chat_completions` patches only ever touch chat bodies. To patch
-# requests on the responses wire, use the `responses` key on the client `patch` block (same
-# <regex> -> url/body/headers shape as chat_completions):
-#   patch:
-#     responses:
-#       <regex>:
-#         body:
-#           <json>
-# Model patches likewise: the top-level `patch` keys apply to the chat wire only, and a
-# `responses:` sub-key applies to the responses wire only:
-#   models:
-#     - name: xxxx
-#       patch:
-#         responses:
-#           body:
-#             <json>
-# Env override per wire: COYOTE_PATCH_<client>_RESPONSES / COYOTE_PATCH_<client>_CHAT_COMPLETIONS
-__CLIENTS_BLOCK__

assets/functions/mcp.json

@@ -21,7 +21,8 @@
     },
     "iwe": {
       "type": "stdio",
-      "command": "iwec"
+      "command": "iwec",
+      "args": ["--project", "."]
     }
   }
 }

assets/functions/scripts/run-agent.py

@@ -27,30 +27,14 @@ def _ensure_cwd_venv():
 _ensure_cwd_venv()
 
 
-def resolve_dir(env_name, default_path):
-    """Resolve a directory at run time.
-
-    Prefer the override env var when set, otherwise fall back to the default
-    path derived from this script's own location, so the shim keeps working
-    when the config dir moves or is shared across environments with different
-    home directories.
-    """
-    value = os.environ.get(env_name)
-    if value:
-        return value
-    return os.path.normpath(default_path)
-
-
 def main():
     (agent_func, raw_data) = parse_argv()
     agent_data = parse_raw_data(raw_data)
 
-    self_dir = os.path.dirname(os.path.abspath(__file__))
+    root_dir = "{config_dir}"
-    agent_dir = os.path.normpath(os.path.join(self_dir, ".."))
+    setup_env(root_dir, agent_func, raw_data)
-    root_dir = resolve_dir("{root_dir_env}", os.path.join(self_dir, "{root_dir_rel}"))
-    setup_env(root_dir, agent_dir, agent_func, raw_data)
 
-    agent_tools_path = os.path.join(agent_dir, "tools.py")
+    agent_tools_path = os.path.join(root_dir, "agents/{agent_name}/tools.py")
     run(agent_tools_path, agent_func, agent_data)
 
 
@@ -81,12 +65,12 @@ def parse_argv():
     return agent_func, agent_data
 
 
-def setup_env(root_dir, agent_dir, agent_func, raw_data):
+def setup_env(root_dir, agent_func, raw_data):
     load_env(os.path.join(root_dir, ".env"))
     os.environ["LLM_ROOT_DIR"] = root_dir
     os.environ["LLM_AGENT_NAME"] = "{agent_name}"
     os.environ["LLM_AGENT_FUNC"] = agent_func
-    os.environ["LLM_AGENT_ROOT_DIR"] = agent_dir
+    os.environ["LLM_AGENT_ROOT_DIR"] = os.path.join(root_dir, "agents", "{agent_name}")
     os.environ["LLM_AGENT_CACHE_DIR"] = os.path.join(root_dir, "cache", "{agent_name}")
     os.environ["LLM_AGENT_RAW_JSON"] = raw_data
 

assets/functions/scripts/run-agent.sh

@@ -5,30 +5,13 @@
 set -e
 
 main() {
-    self_dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+    root_dir="{config_dir}"
-    agent_dir="$(cd "$self_dir/.." && pwd)"
-    root_dir="$(resolve_dir "{root_dir_env}" "$self_dir/{root_dir_rel}")"
-    functions_dir="$(resolve_dir "{functions_dir_env}" "$self_dir/{functions_dir_rel}")"
     parse_argv "$@"
     setup_env
-    tools_path="$agent_dir/tools.sh"
+    tools_path="$root_dir/agents/{agent_name}/tools.sh"
     run
 }
 
-# Resolve a directory at run time: prefer the override env var ($1) when set,
-# otherwise fall back to the default path ($2) derived from this script's own
-# location, so the shim keeps working when the config dir moves or is shared
-# across environments with different home directories.
-resolve_dir() {
-    local override
-    override="$(printenv "$1" 2>/dev/null || true)"
-    if [[ -n "$override" ]]; then
-        echo "$override"
-    else
-        (cd "$2" 2>/dev/null && pwd) || echo "$2"
-    fi
-}
-
 parse_argv() {
 		agent_func="$1"
     if [[ -n "$LLM_TOOL_DATA_FILE" ]] && [[ -f "$LLM_TOOL_DATA_FILE" ]]; then
@@ -46,9 +29,9 @@ setup_env() {
     export LLM_ROOT_DIR="$root_dir"
     export LLM_AGENT_NAME="{agent_name}"
     export LLM_AGENT_FUNC="$agent_func"
-    export LLM_AGENT_ROOT_DIR="$agent_dir"
+    export LLM_AGENT_ROOT_DIR="$LLM_ROOT_DIR/agents/{agent_name}"
     export LLM_AGENT_CACHE_DIR="$LLM_ROOT_DIR/cache/{agent_name}"
-    export LLM_PROMPT_UTILS_FILE="$functions_dir/utils/prompt-utils.sh"
+    export LLM_PROMPT_UTILS_FILE="{prompt_utils_file}"
     export LLM_AGENT_RAW_JSON="$agent_data"
 }
 
@@ -76,10 +59,6 @@ run() {
         die "error: no JSON data"
     fi
 
-    if [[ ! -f "$tools_path" ]]; then
-        die "error: agent tools script not found: $tools_path"
-    fi
-
     if [[ "$OS" == "Windows_NT" ]]; then
         set -o igncr
         tools_path="$(cygpath -w "$tools_path")"
@@ -143,3 +122,4 @@ die() {
 }
 
 main "$@"
+

assets/functions/scripts/run-agent.ts

@@ -3,38 +3,17 @@
 // Usage: ./{agent_name}.ts <agent-func> <agent-data>
 
 import { readFileSync, writeFileSync, existsSync } from "fs";
-import { dirname, join, resolve } from "path";
+import { join } from "path";
-import { fileURLToPath, pathToFileURL } from "url";
+import { pathToFileURL } from "url";
-
-function selfDir(): string {
-  if (typeof __dirname !== "undefined") {
-    return __dirname;
-  }
-  return dirname(fileURLToPath(import.meta.url));
-}
-
-// Resolve a directory at run time: prefer the override env var when set,
-// otherwise fall back to the default path derived from this script's own
-// location, so the shim keeps working when the config dir moves or is shared
-// across environments with different home directories.
-function resolveDir(envName: string, defaultPath: string): string {
-  const value = process.env[envName];
-  if (value) {
-    return value;
-  }
-  return resolve(defaultPath);
-}
 
 async function main(): Promise<void> {
   const { agentFunc, rawData } = parseArgv();
   const agentData = parseRawData(rawData);
 
-  const binDir = selfDir();
+  const configDir = "{config_dir}";
-  const agentDir = resolve(binDir, "..");
+  setupEnv(configDir, agentFunc, rawData);
-  const configDir = resolveDir("{root_dir_env}", join(binDir, "{root_dir_rel}"));
-  setupEnv(configDir, agentDir, agentFunc, rawData);
 
-  const agentToolsPath = join(agentDir, "tools.ts");
+  const agentToolsPath = join(configDir, "agents", "{agent_name}", "tools.ts");
   await run(agentToolsPath, agentFunc, agentData);
 }
 
@@ -69,17 +48,12 @@ function parseArgv(): { agentFunc: string; rawData: string } {
   return { agentFunc, rawData: agentData };
 }
 
-function setupEnv(
+function setupEnv(configDir: string, agentFunc: string, rawData: string): void {
-  configDir: string,
-  agentDir: string,
-  agentFunc: string,
-  rawData: string,
-): void {
   loadEnv(join(configDir, ".env"));
   process.env["LLM_ROOT_DIR"] = configDir;
   process.env["LLM_AGENT_NAME"] = "{agent_name}";
   process.env["LLM_AGENT_FUNC"] = agentFunc;
-  process.env["LLM_AGENT_ROOT_DIR"] = agentDir;
+  process.env["LLM_AGENT_ROOT_DIR"] = join(configDir, "agents", "{agent_name}");
   process.env["LLM_AGENT_CACHE_DIR"] = join(configDir, "cache", "{agent_name}");
   process.env["LLM_AGENT_RAW_JSON"] = rawData;
 }

assets/functions/scripts/run-tool.py

@@ -27,30 +27,14 @@ def _ensure_cwd_venv():
 _ensure_cwd_venv()
 
 
-def resolve_dir(env_name, default_path):
-    """Resolve a directory at run time.
-
-    Prefer the override env var when set, otherwise fall back to the default
-    path derived from this script's own location, so the shim keeps working
-    when the config dir moves or is shared across environments with different
-    home directories.
-    """
-    value = os.environ.get(env_name)
-    if value:
-        return value
-    return os.path.normpath(default_path)
-
-
 def main():
     raw_data = parse_argv()
     tool_data = parse_raw_data(raw_data)
 
-    self_dir = os.path.dirname(os.path.abspath(__file__))
+    root_dir = "{root_dir}"
-    root_dir = resolve_dir("{root_dir_env}", os.path.join(self_dir, "{root_dir_rel}"))
-    functions_dir = resolve_dir("{functions_dir_env}", os.path.join(self_dir, "{functions_dir_rel}"))
     setup_env(root_dir, raw_data)
 
-    tool_path = os.path.join(functions_dir, "tools", "{function_name}.py")
+    tool_path = "{tool_path}.py"
     run(tool_path, "run", tool_data)
 
 

assets/functions/scripts/run-tool.sh

@@ -5,29 +5,13 @@
 set -e
 
 main() {
-    self_dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+    root_dir="{root_dir}"
-    root_dir="$(resolve_dir "{root_dir_env}" "$self_dir/{root_dir_rel}")"
-    functions_dir="$(resolve_dir "{functions_dir_env}" "$self_dir/{functions_dir_rel}")"
     parse_argv "$@"
     setup_env
-    tool_path="$functions_dir/tools/{function_name}.sh"
+    tool_path="{tool_path}.sh"
     run
 }
 
-# Resolve a directory at run time: prefer the override env var ($1) when set,
-# otherwise fall back to the default path ($2) derived from this script's own
-# location, so the shim keeps working when the config dir moves or is shared
-# across environments with different home directories.
-resolve_dir() {
-    local override
-    override="$(printenv "$1" 2>/dev/null || true)"
-    if [[ -n "$override" ]]; then
-        echo "$override"
-    else
-        (cd "$2" 2>/dev/null && pwd) || echo "$2"
-    fi
-}
-
 parse_argv() {
     if [[ -n "$LLM_TOOL_DATA_FILE" ]] && [[ -f "$LLM_TOOL_DATA_FILE" ]]; then
         tool_data="$(cat "$LLM_TOOL_DATA_FILE")"
@@ -44,7 +28,7 @@ setup_env() {
     export LLM_ROOT_DIR="$root_dir"
     export LLM_TOOL_NAME="{function_name}"
     export LLM_TOOL_CACHE_DIR="$LLM_ROOT_DIR/cache/{function_name}"
-    export LLM_PROMPT_UTILS_FILE="$functions_dir/utils/prompt-utils.sh"
+    export LLM_PROMPT_UTILS_FILE="{prompt_utils_file}"
     export LLM_TOOL_RAW_JSON="$tool_data"
 }
 
@@ -72,10 +56,6 @@ run() {
         die "error: no JSON data"
     fi
 
-    if [[ ! -f "$tool_path" ]]; then
-        die "error: tool script not found: $tool_path"
-    fi
-
     if [[ "$OS" == "Windows_NT" ]]; then
         set -o igncr
         tool_path="$(cygpath -w "$tool_path")"

assets/functions/scripts/run-tool.ts

@@ -3,41 +3,17 @@
 // Usage: ./{function_name}.ts <tool-data>
 
 import { readFileSync, writeFileSync, existsSync } from "fs";
-import { dirname, join, resolve } from "path";
+import { join } from "path";
-import { fileURLToPath, pathToFileURL } from "url";
+import { pathToFileURL } from "url";
-
-function selfDir(): string {
-  if (typeof __dirname !== "undefined") {
-    return __dirname;
-  }
-  return dirname(fileURLToPath(import.meta.url));
-}
-
-// Resolve a directory at run time: prefer the override env var when set,
-// otherwise fall back to the default path derived from this script's own
-// location, so the shim keeps working when the config dir moves or is shared
-// across environments with different home directories.
-function resolveDir(envName: string, defaultPath: string): string {
-  const value = process.env[envName];
-  if (value) {
-    return value;
-  }
-  return resolve(defaultPath);
-}
 
 async function main(): Promise<void> {
   const rawData = parseArgv();
   const toolData = parseRawData(rawData);
 
-  const binDir = selfDir();
+  const rootDir = "{root_dir}";
-  const rootDir = resolveDir("{root_dir_env}", join(binDir, "{root_dir_rel}"));
-  const functionsDir = resolveDir(
-    "{functions_dir_env}",
-    join(binDir, "{functions_dir_rel}"),
-  );
   setupEnv(rootDir, rawData);
 
-  const toolPath = join(functionsDir, "tools", "{function_name}.ts");
+  const toolPath = "{tool_path}.ts";
   await run(toolPath, "run", toolData);
 }
 

assets/functions/tools/execute_command.sh

@@ -20,12 +20,5 @@ main() {
     trap "rm -f '$script'" EXIT
     # shellcheck disable=SC2154
     printf '%s\n' "$argc_command" > "$script"
-    # No -e: the command gets standard interactive-shell semantics — the last
+    bash -e -o pipefail "$script" >> "$LLM_OUTPUT"
-    # statement decides the exit code, so trailing guards like `; exit 0` work
-    # and an intermediate non-zero status (grep with no matches, a failing
-    # test run being inspected) cannot abort the script mid-way. pipefail is
-    # kept so a failing pipeline stage still surfaces in the exit code. 2>&1:
-    # the harness only returns $LLM_OUTPUT on success, so without it stderr
-    # (git push, cargo progress, curl -v) vanishes from successful calls.
-    bash -o pipefail "$script" >> "$LLM_OUTPUT" 2>&1
 }

assets/functions/tools/fs_grep.sh

@@ -25,11 +25,7 @@ main() {
         exit 1
     fi
 
-    # --binary-files=text: GNU grep's binary heuristic false-positives on valid
+    local grep_args=(-nH --color=never)
-    # UTF-8 source files >=128KiB when a multibyte character straddles an
-    # internal read-buffer boundary, silently returning zero matches. This tool
-    # only searches text, so always force text mode.
-    local grep_args=(-nH --color=never --binary-files=text)
 
     if [[ -d "$search_path" ]]; then
         # Use -r (not -R) so symlinks to directories are NOT followed - this avoids
@@ -59,11 +55,7 @@ main() {
     # (they only matter when recursing into a directory tree).
 
     local results
-    # tr strips NUL bytes from matches in real binary files (text mode searches
+    results=$(grep "${grep_args[@]}" -E "$search_pattern" "$search_path" 2>/dev/null | head -n "$MAX_RESULTS") || true
-    # them), which would otherwise trigger bash's "ignored null byte in input"
-    # warning in the command substitution. -I can't be used instead: it overrides
-    # --binary-files=text and re-skips the misdetected UTF-8 files noted above.
-    results=$(grep "${grep_args[@]}" -E "$search_pattern" "$search_path" 2>/dev/null | tr -d '\0' | head -n "$MAX_RESULTS") || true
 
     if [[ -z "$results" ]]; then
         echo "No matches found for: $search_pattern" >> "$LLM_OUTPUT"