@webpresso/plugin-codex 0.0.15 → 0.0.17

package/skills/ultragoal/SKILL.md

@@ -21,13 +21,13 @@ argument-hint: "<new|status|handoff|run|cancel> [brief]"
 - "spawn many in parallel", multi-blueprint ready-set execution
 - Reject unbound "complete everything while I sleep" without stop condition / budgets
 
-Use `wp ultragoal` / MCP `wp_ultragoal_*` as the durable controller for work spanning
+Use `wp ultragoal` / MCP `ultragoal_*` as the durable controller for work spanning
 one or more blueprints. Prefer this spine over host-local mega-sessions or ad-hoc
 multi-agent swarms.
 
 ## Creating an ultragoal does NOT set a host stop-condition
 
-`wp_ultragoal_new` records a durable brief, budgets, and phase. It does **not**
+`ultragoal_new` records a durable brief, budgets, and phase. It does **not**
 install the session Stop hook that keeps a host working until a condition holds
 — that hook belongs to the host's own goal surface (Claude Code's `/goal`), which
 this skill cannot reach. The two are independent: an ultragoal can sit in `plan`
@@ -151,23 +151,23 @@ OS sandbox. Run Ultragoal only with providers, configuration, and task content y
 
 ## Tooling map (use these; do not reimplement with Bash)
 
-| Phase                  | Prefer MCP / CLI                                                                       | Purpose                                             |
-| ---------------------- | -------------------------------------------------------------------------------------- | --------------------------------------------------- |
-| Create / resume        | `wp_ultragoal_new`, `wp_ultragoal_status`                                              | Durable controller state                            |
-| Isolation              | `wp_worktree`                                                                          | Owner / lane worktrees; never primary as controller |
-| Blueprint read         | `wp_blueprint_list`, `wp_blueprint_get`, `wp_blueprint_context`                        | Ready-set and deps                                  |
-| Blueprint write        | `wp_blueprint_put`, `wp_blueprint_transition`                                          | Spec edits (MCP-only for blueprints)                |
-| Task done              | `wp_blueprint_task_verify` only                                                        | Evidence-gated completion                           |
-| Parallel execute       | `/goal` (autopilot) or ready-queue + host subagents                                    | Max parallel when deps allow                        |
-| Context-light delegate | `wp_session_context`                                                                   | Manifest for subagents (no history paste)           |
-| Continuity             | `wp_session_capture`, `wp_session_search`, `wp_session_restore`, `wp_session_snapshot` | Decisions / resume                                  |
-| Large command / file   | `wp_session_execute`, `wp_session_batch_execute`, `wp_session_execute_file`            | Bounded output + index                              |
-| QA                     | `wp_qa` (or `wp_lint` + `wp_typecheck` + `wp_test`)                                    | Affected quality gates                              |
-| PR / land              | `wp_pr_upsert`, `wp_pr_status`, `wp_pr_wait`, `wp_pr_merge`                            | Open early; exact-head merge only                   |
-| Delivery programs      | `wp_delivery_status`                                                                   | Derive one dispatch/integration action              |
-| Fleet / workers        | `wp_fleet_status`, `wp_worker_tail`                                                    | Multi-session visibility                            |
-| Token gain             | `wp_gain`                                                                              | Optional efficiency check after heavy execute       |
-| Advance loop           | `wp_ultragoal_run`, `wp_ultragoal_handoff`, `wp_ultragoal_cancel`                      | Controller steps only                               |
+| Phase                  | Prefer MCP / CLI                                                           | Purpose                                             |
+| ---------------------- | -------------------------------------------------------------------------- | --------------------------------------------------- |
+| Create / resume        | `ultragoal_new`, `ultragoal_status`                                        | Durable controller state                            |
+| Isolation              | `worktree`                                                                 | Owner / lane worktrees; never primary as controller |
+| Blueprint read         | `blueprint_list`, `blueprint_get`, `blueprint_context`                     | Ready-set and deps                                  |
+| Blueprint write        | `blueprint_put`, `blueprint_transition`                                    | Spec edits (MCP-only for blueprints)                |
+| Task done              | `blueprint_task_verify` only                                               | Evidence-gated completion                           |
+| Parallel execute       | `/goal` (autopilot) or ready-queue + host subagents                        | Max parallel when deps allow                        |
+| Context-light delegate | `session_context`                                                          | Manifest for subagents (no history paste)           |
+| Continuity             | `session_capture`, `session_search`, `session_restore`, `session_snapshot` | Decisions / resume                                  |
+| Large command / file   | `session_execute`, `session_batch_execute`, `session_execute_file`         | Bounded output + index                              |
+| QA                     | `qa` (or `lint` + `typecheck` + `test`)                                    | Affected quality gates                              |
+| PR / land              | `pr_upsert`, `pr_status`, `pr_wait`, `pr_merge`                            | Open early; exact-head merge only                   |
+| Delivery programs      | `delivery_status`                                                          | Derive one dispatch/integration action              |
+| Fleet / workers        | `fleet_status`, `worker_tail`                                              | Multi-session visibility                            |
+| Token gain             | `gain`                                                                     | Optional efficiency check after heavy execute       |
+| Advance loop           | `ultragoal_run`, `ultragoal_handoff`, `ultragoal_cancel`                   | Controller steps only                               |
 
 Fallback to `wp …` CLI only when the matching MCP tool is unavailable. Prefer `wp` >
 `vp` > raw package managers. Never raise timeouts to hide hangs.
@@ -175,25 +175,25 @@ Fallback to `wp …` CLI only when the matching MCP tool is unavailable. Prefer
 ## Protocol
 
 1. Create or resume the ultragoal in a **managed blueprint owner worktree**
-   (`wp_worktree` / `wp_blueprint_put`). Never use `main` or the primary checkout
+   (`worktree` / `blueprint_put`). Never use `main` or the primary checkout
    as controller.
 2. Print the **ready-set**: tasks whose dependencies are satisfied (from blueprint tools).
 3. Launch up to `concurrency` independent ready tasks in parallel (worktree-isolated).
    Serialize only when file ownership overlaps or deps require it.
-4. Execute only the current phase handoff; call `wp_ultragoal_run` again after evidence.
-5. Mark tasks done **only** via `wp_blueprint_task_verify` with passing evidence.
+4. Execute only the current phase handoff; call `ultragoal_run` again after evidence.
+5. Mark tasks done **only** via `blueprint_task_verify` with passing evidence.
 6. **Opportunistic `/fix`:** at most `fix_budget` pre-existing issues per phase, each with
    named invariant + failing proof. Excess → handoff backlog (do not expand epic).
-7. **Validate / land:** local proof with `wp_qa` / targeted tools; outside review only when
+7. **Validate / land:** local proof with `qa` / targeted tools; outside review only when
    merge-ready and within `review_budget` — **exactly one sequential** outside voice unless
    the user sets N (the default value lives in `workflow-skills-routing.md`).
    Controller validation evidence is **machine-qa (prior QA phase) + N outside voices**
    (default N=1), not two outside model reviewers at budget 1.
-   `wp_review_gate` has one mode: purpose plan for exact-version draft plan
-   approval/auto-promotion, purpose delivery for implementation/phase outside
+   `review_gate` has one mode: purpose plan for exact-version draft plan
+   approval (then `blueprint_promote`), purpose delivery for implementation/phase outside
    voice. Each new provider verdict is a formal round of the slug's budget and
    an approval is authority immediately. A CLI delivery gate is explicit MCP-unavailable
-   compatibility only, not this MCP contract. Use `wp_pr_*` for PR babysit — no
+   compatibility only, not this MCP contract. Use `pr_*` for PR babysit — no
    multi-sleep poll loops; no parallel multi-reviewer stampede.
 8. Stop on `complete`, `cancelled`, blocked guard exhaustion, or `WP_ULTRAGOAL_DISABLE=1`.
 
@@ -206,83 +206,78 @@ primary checkout.
 - Hard fail on a task → mark blocked with reason; **cascade-skip** dependents that cannot
   proceed; continue independent ready work.
 - Lifecycle mutation failure → stop (do not continue on stale plan state).
-- On block: call `wp_ultragoal_handoff` and emit a **≤40-line handoff**: goal, done, blockers,
-  evidence refs (`wp_session_*` ids if any), next 3 commands. Do not paste full transcripts.
+- On block: call `ultragoal_handoff` and emit a **≤40-line handoff**: goal, done, blockers,
+  evidence refs (`session_*` ids if any), next 3 commands. Do not paste full transcripts.
 
 ## Outside-voice review (required for autopilot)
 
-Autopilot and agent-driven ultragoal loops **must** request an **OpenCode Go** outside-voice review after each **goal/phase milestone**, and must pick the model by purpose. Use **`wp_review_gate`** purpose plan for exact-version draft plan approval/auto-promotion and one single-shot **`wp_review_gate`** purpose delivery call for implementation/phase outside voice. The gate has one mode: each newly executed provider review that reaches a verdict is a formal round of the slug's budget, an approval is authority immediately, and an identical-subject call replays the recorded verdict without a new round. CLI delivery gates are explicit MCP-unavailable compatibility only, not this MCP contract.
+Autopilot and agent-driven ultragoal loops **must** request an outside-voice review after each **goal/phase milestone**. Use **`review_gate`** purpose plan for exact-version draft plan approval (then promote with `blueprint_promote`) and one single-shot **`review_gate`** purpose delivery call for implementation/phase outside voice. The gate has one mode: each newly executed provider review that reaches a verdict is a formal round of the slug's budget, an approval is authority immediately, and an identical-subject call replays the recorded verdict without a new round. CLI delivery gates are explicit MCP-unavailable compatibility only, not this MCP contract.
 
-Count each milestone review against `review_budget` for merge-ready claims: **exactly one sequential** reviewer path unless the user sets N; the default value is owned by `workflow-skills-routing.md`. Prefer purpose-matched OpenCode Go first; do not fan out multi-host review swarms.
+Count each milestone review against `review_budget` for merge-ready claims: **exactly one sequential** reviewer path unless the user sets N; the default value is owned by `workflow-skills-routing.md`. Do not fan out multi-host review swarms.
 
 ### Milestones that require a review
 
-Run `wp_review_gate` purpose plan for the plan approval milestone below and one
-single-shot `wp_review_gate` purpose delivery call for implementation/phase
+Run `review_gate` purpose plan for the plan approval milestone below and one
+single-shot `review_gate` purpose delivery call for implementation/phase
 milestones. Each new provider verdict is one formal round of the slug's budget.
 
 | Milestone          | When                                                                                                                             |
 | ------------------ | -------------------------------------------------------------------------------------------------------------------------------- |
-| Plan gate          | Before `draft` → `planned`, using the exact version returned by `wp_blueprint_put`; approval may auto-promote the same version   |
+| Plan gate          | Before `draft` → `planned`, using the exact version returned by `blueprint_put`; then `blueprint_promote` the approved version   |
 | Phase advance      | After ultragoal advances `plan` → `execute`, `execute` → `qa`, `qa` → `validate`, `validate` → `land`, or lands `complete`       |
 | Task batch handoff | After a meaningful execute batch when the phase remains `execute` (at least once per blueprint before claiming execute-complete) |
 
-Do **not** invent ledger approvals. If OpenCode Go is unavailable or hits a provider-wide usage limit, capture the failure evidence and end OpenCode Go review for the window; do not hop OpenCode families, substitute another host, or substitute a forged approval.
+Do **not** invent ledger approvals. If the review provider is unavailable or hits a provider-wide usage limit, capture the failure evidence and end outside review for the window; do not hop reviewer families, substitute another host, or substitute a forged approval.
 
-### Purpose → model routing (no hardcoding IDs)
+### Reviewer selection (the gate chooses, not the caller)
 
-Resolve models from the live catalog every time:
+Pass `caller_model` with your own model id and omit `provider`, `model`, and
+`effort`. The gate selects the reviewer route itself — a cross-family reviewer
+chosen for capability, current provider limits, and measured daily cost — and
+reports the choice in `policy_selection`. Never resolve models from a live
+catalog at invocation time, never probe a provider CLI for its model list, and
+never read a credential store to discover models; provider catalog discovery
+belongs to the snapshot drift workflow. A human operator may still name an
+explicit `provider`/`model` as an override; agents must not.
 
-```bash
-opencode models opencode-go
-```
-
-**Selection order and the purpose→family mapping live in one place: the committed
-reviewer policy (`packages/workflow-skills/src/opencode-reviewer-policy.ts`),
-rendered into the `opencode-go` skill and drift-gated against it.** Follow that
-skill; do not restate the ordering here. A second copy of a preference list is a
-second thing to update, and the copy that goes stale is the one an agent reads.
-
-Treat a provider-wide usage limit as terminal for every OpenCode Go model in the current review window; do not hop OpenCode families to evade a usage block. There is no substitute host: the window ends with the captured failure evidence.
+Treat a provider-wide usage limit as terminal for the current review window; do not hop reviewer families to evade a usage block. There is no substitute host: the window ends with the captured failure evidence.
 
 ### Plan gate invocation shape
 
 ```text
-wp_review_gate({
+review_gate({
   "project_id": "<project-id>",
   "slug": "<blueprint-slug>",
   "expected_version": "bpv1:0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef",
   "repository_access": "read-only",
   "auto_promote": true,
-  "provider": "opencode",
-  "model": "<selected-model>",
-  "effort": "medium"
+  "caller_model": "<your own model id>"
 })
 ```
 
 The plan gate has no `purpose` or `target` field. Pass the exact `bpv1:` token
-returned by `wp_blueprint_put`, never a commit hash or `HEAD`. An explicitly
+returned by `blueprint_put`, never a commit hash or `HEAD`. An explicitly
 requested CLI delivery gate is an MCP-unavailable compatibility fallback only.
 If the MCP host returns before a terminal result, poll the same invocation with
-`wp_review_gate_wait`; treat in-progress, not-found, contention, waiter timeout,
+`review_gate_wait`; treat in-progress, not-found, contention, waiter timeout,
 waiter abort, and cancellation as non-verdict observation states. `not_found`
 means no active or terminal gate exists for that subject; refresh state and
 start the gate again instead of spinning a wait loop.
 
 ### Honesty rules (non-negotiable)
 
-- Never self-approve or hand-edit `reviews.md` / `review-events.jsonl` / frontmatter approvals to fake OpenCode Go authority.
-- Never mark blueprint tasks done except through `wp_blueprint_task_verify` with real evidence.
+- Never self-approve or hand-edit `reviews.md` / `review-events.jsonl` / frontmatter approvals to fake outside-review authority.
+- Never mark blueprint tasks done except through `blueprint_task_verify` with real evidence.
 - Never run ultragoal mutations on `main` or a primary checkout; use the managed blueprint owner worktree.
 - Keep every loop bounded and never increase timeouts.
 - When the controller returns `waiting` (`blueprint-promotion`, `approval-gate`, `blueprint-tasks`, …), fix the named gap; do not spin `wp ultragoal run` without progress.
 
 ## Tooling-aligned evidence (QA / land)
 
-- **QA phase** prefers **GitHub required checks** for the worktree PR (`wp_pr_status` /
-  `wp_pr_wait` or `gh pr checks --required`) when PR is `OPEN`/`MERGED`, checks green, and
+- **QA phase** prefers **GitHub required checks** for the worktree PR (`pr_status` /
+  `pr_wait` or `gh pr checks --required`) when PR is `OPEN`/`MERGED`, checks green, and
   PR head matches clean worktree HEAD.
-- If no PR-bound green CI is available, fall back to local **`wp_qa`**.
+- If no PR-bound green CI is available, fall back to local **`qa`**.
 - Open a PR early so CI can satisfy QA. Do **not** raise timeouts.
 - **Land** still requires a **MERGED** PR with green required checks bound to the projected
   source snapshot. Use `/verify --merge-ready` (merge-ready `review_budget`, per

package/skills/verify/SKILL.md

@@ -37,22 +37,24 @@ integrated, and free of stale garbage?**
 
 Default `/verify` must **not** spawn outside reviewers. That stampede is a known
 token/time failure mode. Merge-ready runs **one** sequential outside voice via
-the preferred skill (`claude` / `codex` / one OpenCode Go), then stops.
+one `review_gate` delivery gate (or a host review skill), then stops. Pass
+`caller_model` with your own model id and omit `provider`/`model`/`effort`: the
+gate selects the cross-family reviewer and reports it in `policy_selection`.
 
 ## Tooling map
 
-| Gate                      | Prefer                                                                                   |
-| ------------------------- | ---------------------------------------------------------------------------------------- |
-| Lint / types / tests / QA | `wp_lint`, `wp_typecheck`, `wp_test`, `wp_qa`                                            |
-| Format                    | `wp_format`                                                                              |
-| Audits                    | `wp_audit`, `wp_audits`                                                                  |
-| Blueprint                 | blueprint MCP tools + `wp_audit`                                                         |
-| PR / CI wait              | `wp_pr_status`, `wp_pr_wait` (not multi-sleep loops)                                     |
-| Release                   | `wp_release_progress` for live Release phases; `wp_release_readiness` for package gates  |
-| Large output              | `wp_session_execute` / `batch_execute` / `execute_file`                                  |
-| Continuity                | `wp_session_capture` for verify summary; avoid paste-back walls                          |
-| E2E / act                 | `wp_e2e`, `wp_ci_act` when the change requires them                                      |
-| Outside authority         | `wp_review_gate` (purpose plan or delivery); each new provider verdict is a formal round |
+| Gate                      | Prefer                                                                                |
+| ------------------------- | ------------------------------------------------------------------------------------- |
+| Lint / types / tests / QA | `lint`, `typecheck`, `test`, `qa`                                                     |
+| Format                    | `format`                                                                              |
+| Audits                    | `audit`, `audits`                                                                     |
+| Blueprint                 | blueprint MCP tools + `audit`                                                         |
+| PR / CI wait              | `pr_status`, `pr_wait` (not multi-sleep loops)                                        |
+| Release                   | `release_progress` for live Release phases; `release_readiness` for package gates     |
+| Large output              | `session_execute` / `batch_execute` / `execute_file`                                  |
+| Continuity                | `session_capture` for verify summary; avoid paste-back walls                          |
+| E2E / act                 | `e2e`, `ci_act` when the change requires them                                         |
+| Outside authority         | `review_gate` (purpose plan or delivery); each new provider verdict is a formal round |
 
 ## Iron law — evidence before claims
 
@@ -81,7 +83,7 @@ Not sufficient: "should pass", "looks correct", lint-only evidence for runtime c
 
 Follow the repo's current routing and command surface:
 
-- use MCP `wp_*` / repo-owned quality wrappers first
+- use wp MCP tools / repo-owned quality wrappers first
 - use bounded session-memory tooling for large output
 - reuse fresh logs instead of re-running broad commands just to inspect output
 
@@ -102,7 +104,7 @@ workflow:
 2. Run the repo audit when available:
 
    ```text
-   wp_audit({"kind":"test-smells"})
+   audit({"kind":"test-smells"})
    ```
 
    Use the global `wp audit test-smells` command only when MCP is unavailable.
@@ -137,16 +139,16 @@ Hard stop on any failure.
 
 Run the narrowest checks that prove the touched behavior:
 
-- `wp_lint` / targeted lint
-- `wp_typecheck` / targeted typecheck
-- `wp_test` / targeted tests
-- `wp_qa`, `wp_e2e`, build / package checks only when the change requires them
+- `lint` / targeted lint
+- `typecheck` / targeted typecheck
+- `test` / targeted tests
+- `qa`, `e2e`, build / package checks only when the change requires them
 
 **Before push or PR open/update**, run the pre-push owner end-to-end:
 
 ```text
-start = wp_ci_preflight({})
-wp_ci_preflight_wait({ runId: start.details.operation.runId })
+start = ci_preflight({})
+ci_preflight_wait({ runId: start.details.operation.runId })
 ```
 
 The start result is not a gate verdict. Poll again when wait returns
@@ -167,12 +169,12 @@ push-ready if preflight failed. Do **not** bypass hooks to ship red work.
 
 Rules:
 
-- Prefer MCP `wp_*` over raw underlying tools.
+- Prefer wp MCP tools over raw underlying tools.
 - Reuse fresh logs / session-memory indexed output if the runner auto-saves them.
 - Never claim broader correctness than the commands actually proved.
-- If the repo documents a "full QA" bookend, reserve `wp_qa` / `--full` for the final broad pass rather than every iteration.
+- If the repo documents a "full QA" bookend, reserve `qa` / `--full` for the final broad pass rather than every iteration.
 - If CI is already red: read the failed job log, reproduce with the matching
-  local `wp_ci_preflight` + `wp_ci_preflight_wait` flow (or the `wp ci-preflight` CLI fallback), fix, then push **one**
+  local `ci_preflight` + `ci_preflight_wait` flow (or the `wp ci-preflight` CLI fallback), fix, then push **one**
   corrective commit — do not burn another full matrix “to check.”
 
 ## Phase 3 — Cross-surface impact scan
@@ -209,7 +211,7 @@ Check that:
 - UX or operator-facing flows include graceful-degradation coverage when applicable
 
 Run the folded TPH gate for every verification target. At minimum, execute
-`wp_audit` with the `test-smells` kind when available (use global `wp audit
+`audit` with the `test-smells` kind when available (use global `wp audit
 test-smells` only as the CLI fallback) and inspect changed tests against the
 `testing-philosophy` checklist. Add E2E or integration evidence when the change
 touches user/operator-facing workflows, batch/list behavior, graceful
@@ -253,7 +255,7 @@ Before claiming **merge-ready** / land:
 
 ### 1. Classify with immutable refs
 
-Run `wp_audit` with `kind: "risk-review-coverage"` using:
+Run `audit` with `kind: "risk-review-coverage"` using:
 
 - immutable PR **base** SHA
 - immutable **authority** (head) SHA
@@ -267,13 +269,13 @@ CI job in `.github/workflows/pr-policy.yml`.
 
 When classification is **sensitive**:
 
-- Require delivery review via `risk-review-coverage` / `wp_review_gate`
+- Require delivery review via `risk-review-coverage` / `review_gate`
   (purpose delivery) / qualifying lane approvals for the current
   review subject until `policySatisfied` (**approval**). A formal **reject** is a terminal automated-review
   outcome but does **not** satisfy land policy: Product status stays
   `incomplete`, Process status stays `sensitive-blocked` until approval.
   Tech-debt is **not** a substitute for delivery approval.
-- Launch **exactly one at a time** `wp_review_gate` delivery attempt with
+- Launch **exactly one at a time** `review_gate` delivery attempt with
   `--base-ref <base-sha>` and `--authority-ref <head-sha>`. Do not substitute
   `HEAD` for the authority SHA, and do not relaunch while the same subject has
   an in-progress gate.
@@ -312,8 +314,8 @@ When classification is **standard**:
   Must be start-of-line. Process label: `standard-skip`.
 
 - Otherwise obtain **exactly one sequential** outside voice: one
-  `wp_review_gate` delivery gate (or host skill). Process label: `outside-approved`.
-- At most **one OpenCode Go reviewer** counts unless the user asks for more.
+  `review_gate` delivery gate (or host skill). Process label: `outside-approved`.
+- At most **one outside reviewer** counts unless the user asks for more.
 - Invoke the selected reviewer **once**. Do not probe, retry, or rotate
   providers automatically, and **never** fan out parallel multi-host review
   swarms.
@@ -322,12 +324,13 @@ When classification is **standard**:
 - These approvals are model outside-voice approvals, not a substitute for human
   GitHub reviews or branch-protection approvals.
 
-Reviewer preference (pick **one** path):
-
-- From Codex → Claude (else one OpenCode Go).
-- From Claude → Codex (else one OpenCode Go).
-- Prefer skills: `claude`, `codex`, or one of `opencode-go` / `qwen` /
-  `deepseek` / `glm` / `kimi` / `minimax` / `mimo`.
+Reviewer preference: the gate owns it. State `caller_model` (your own model
+id) and omit `provider`/`model`/`effort`; `review_gate` selects a
+cross-family reviewer by capability, current provider limits, and measured
+daily cost, and discloses the choice in `policy_selection`. Do not name a
+reviewer host or model, do not probe provider catalogs, and do not rotate
+providers yourself. A human operator may still name an explicit
+`provider`/`model` override; agents must not.
 
 ### 4. Dual product/process labels on every land claim
 
@@ -340,14 +343,14 @@ Never invent a land-now skip. See `land-policy` for the full table.
 
 ### Approval evidence requirements
 
-- Blueprint plan approval: use `wp_review_gate` with the current `bpv1` version.
+- Blueprint plan approval: use `review_gate` with the current `bpv1` version.
   It records the review and promotes an approved draft atomically by default.
   If the gate is still running or the host wait expires, poll the same exact
-  invocation with `wp_review_gate_wait` until a terminal review outcome is
+  invocation with `review_gate_wait` until a terminal review outcome is
   observed; wait timeout/abort/in-progress/not-found are not reviewer verdicts.
   `not_found` means there is no active or terminal gate for that subject; refresh
   state and start the gate again instead of continuing to wait.
-- Implementation / delivery approval: use `wp_review_gate` purpose delivery
+- Implementation / delivery approval: use `review_gate` purpose delivery
   on the immutable subject, exactly once with the selected provider, for
   sensitive and standard PRs alike. The gate has one mode: each newly executed
   provider review that reaches a verdict is one formal round of the slug's
@@ -358,7 +361,7 @@ Never invent a land-now skip. See `land-policy` for the full table.
   spends none). Do not run a separate
   provider probe.
 - Two gates on the same subject cannot run concurrently — every
-  `wp_review_gate` call claims the subject's active marker. If a call reports
+  `review_gate` call claims the subject's active marker. If a call reports
   marker contention, serialize the two calls rather than treating contention
   as an error.
 - Each gate reviewer must return exactly one schema-valid JSON review object;
@@ -377,7 +380,7 @@ Never invent a land-now skip. See `land-policy` for the full table.
 Report:
 
 - mode used (`local` / `full` / `merge-ready`)
-- what was verified and which `wp_*` commands/logs prove it
+- what was verified and which wp MCP tools commands/logs prove it
 - which docs/help/instruction surfaces were refreshed when guidance changed
 - outside models only if merge-ready (with PR comment links when applicable)
 - what remains intentionally out of scope
@@ -388,7 +391,7 @@ If any required check is missing, the correct result is **not done yet**, not a
 
 **Tooling friction (optional):** if this session burned medium+ tokens on MCP/CLI/hooks/CI
 gates (not product code), run `/tooling-friction` once and resolve its capture
-destination with `wp_tooling_friction_path({"file":"<file>"})` — copy the absolute
+destination with `tooling_friction_path({"file":"<file>"})` — copy the absolute
 path from the tool summary (human CLI: `wp tooling-friction path --file <file>`).
 Do not invent fleet folder slugs or worktree-keyed desktop-state paths. Skip when
 the path was smooth. If the surface cannot be resolved or written, report the skip