@webpresso/plugin-opencode 0.0.12 → 0.0.14

package/skills/verify/SKILL.md

@@ -37,22 +37,22 @@ 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` / `grok` / one OpenCode Go), then stops.
+the preferred skill (`claude` / `codex` / one OpenCode Go), then stops.
 
 ## 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` (authoritative) for plans; `wp_review_gate` with `mode: "advisory"` for implementation |
+| 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 |
 
 ## Iron law — evidence before claims
 
@@ -245,7 +245,7 @@ in outside-voice usage — stop and fix the gate, do not multiply reviewers.
 **Skip this entire phase** for default `/verify` and `/verify --full`. Local
 `done` claims do not require outside voice.
 
-This phase implements **land-policy M7** (delivery vs advisory). Full land
+This phase implements **land-policy M7** (delivery vs outside voice). Full land
 language and dual-label contract:
 [`catalog/agent/rules/land-policy.md`](../../rules/land-policy.md).
 
@@ -269,34 +269,37 @@ When classification is **sensitive**:
 
 - Require delivery review via `risk-review-coverage` / `wp_review_gate`
   (purpose delivery) / qualifying lane approvals for the current
-  review subject until `policySatisfied` (**approval** or valid same-subject
-  **maintainer-override**). A formal **reject** is a terminal automated-review
+  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 or
-  override. Tech-debt is **not** a substitute for delivery approval.
+  `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
   `--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.
-- On formal **reject**: surface the gate `next_action` (`report_delivery_reject`)
-  / reject projection to the user; free-triage against blueprint non-goals;
-  address the findings, then re-review only a changed exact subject. The shared
-  gate permits five distinct rejected delivery subjects by default. Once that
-  budget is exhausted, **do not** set `scope_continue=true` without explicit
-  user authorization; agents must not invent the grant. For plan or delivery,
-  only an operator may request an absolute finite same-slug ceiling through MCP
-  `scope_continue_limit` (10..32); the field still requires
-  `scope_continue=true`. MCP wins over `WP_REVIEW_SCOPE_CONTINUE_LIMIT`; when
-  neither is present, the plan/delivery defaults are 16/10. Machine enforcement
-  does not link successor slugs; creating one to launder or bypass the budget
-  remains procedurally forbidden, as do resets and retry schemes.
+- On formal **reject**: record the gate `next_action` (`report_delivery_reject`)
+  / reject projection, triage against blueprint non-goals, address the findings,
+  then re-review only a changed exact subject. The gate counts formal verdicts
+  per slug and purpose, starting with eight rounds.
+  After all allowance is spent, a corrected subject may open one
+  extra lane on an explicitly selected provider and model, including one that
+  already reviewed the lineage. The gate records that grant, adds five formal
+  rounds, and permits at most five distinct provider attempts in the new lane
+  that reach a verdict or an unproven outcome; provider infrastructure failures
+  spend no attempt but are bounded separately at five per lane. The provider and model remain pinned.
+  Once that lane is spent, this blueprint's review lineage is terminal: no
+  gate call on its slug can reopen it, whatever the subject. Re-plan the
+  narrowed scope as a new blueprint with its own plan review.
+  Machine enforcement does not link successor slugs; creating one to launder
+  or bypass the budget remains procedurally forbidden, as do resets and retry
+  schemes.
 - `Review-skip` is **FORBIDDEN** (`sensitive-review-skip-forbidden`).
 - Completed owner blueprint must be present in the PR
   (`sensitive-no-completed-owner` otherwise).
 - Process label when blocked: `sensitive-blocked`. When delivery lane
   approves: `delivery-approved`.
 
-### 3. Standard → skip or one advisory outside voice
+### 3. Standard → skip or one outside voice
 
 When classification is **standard**:
 
@@ -308,8 +311,8 @@ When classification is **standard**:
 
   Must be start-of-line. Process label: `standard-skip`.
 
-- Otherwise obtain **exactly one sequential** advisory outside voice
-  (`wp_review_gate` with `mode: "advisory"`, or host skill). Process label: `outside-approved`.
+- 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.
 - Invoke the selected reviewer **once**. Do not probe, retry, or rotate
   providers automatically, and **never** fan out parallel multi-host review
@@ -321,10 +324,9 @@ When classification is **standard**:
 
 Reviewer preference (pick **one** path):
 
-- From Codex → Claude or Grok (else one OpenCode Go).
-- From Claude → Codex or Grok (else one OpenCode Go).
-- From Grok → Claude or Codex (else one OpenCode Go).
-- Prefer skills: `claude`, `codex`, `grok`, or one of `opencode-go` / `qwen` /
+- 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`.
 
 ### 4. Dual product/process labels on every land claim
@@ -345,26 +347,20 @@ Never invent a land-now skip. See `land-policy` for the full table.
   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: for sensitive PRs use `wp_review_gate`
-  purpose delivery, default authoritative mode, on the immutable subject; for
-  standard advisory use the same `wp_review_gate` call with `mode: "advisory"`
-  exactly once with the selected provider. Do not run a separate provider
-  probe. A later authoritative call on the same subject may promote a
-  matching complete advisory approval to authority with zero provider
-  invocation, unless a completed reject already exists for that content at
-  either stage.
-- `advisory-exhausted` is a terminal outcome with no ledger event and no
-  verdict — treat it as terminal-without-authority. It means this exact
-  digest already used its advisory attempt budget; do not retry the same
-  content or report it as a failure. Change the reviewed content (which mints
-  a new digest) or spend real authoritative budget instead. It is always
-  returned synchronously; no `wp_review_gate_wait` poll is ever needed or
-  issued for it.
-- An advisory gate and an authoritative gate on the same subject cannot run
-  concurrently — unlike the removed `wp_review_run`, an advisory
-  `wp_review_gate` call claims the same active marker an authoritative call
-  does. If a call reports marker contention, serialize the two calls rather
-  than treating contention as an error.
+- Implementation / delivery approval: use `wp_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
+  budget, an approval is authority immediately, and an identical-subject call
+  replays the recorded verdict without a new round (an approval withheld for
+  incomplete adjudication of prior findings — not all briefed, or a briefed
+  claim still open without a matching finding — grants no authority and
+  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
+  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;
   never infer a verdict from Markdown. The gate derives approval from typed
   findings: blockers reject, nits approve with nits, and no findings approve.

package/skills/grok/SKILL.md

@@ -1,44 +0,0 @@
----
-name: grok
-description: "Grok outside-voice reviewer through Webpresso MCP."
-license: MIT
----
-
-# Grok outside-voice review
-
-Use only for a requested content-bound plan or delivery review. Treat output as external advice
-until independently verified.
-
-## MCP-only contract
-
-- Call `wp_review_gate` exactly once for the real plan version or delivery diff.
-- Observe the same durable operation with `wp_review_gate_wait` when needed.
-- Never invoke a provider command, the legacy review CLI, or a removed review-run surface.
-- If the review MCP is unavailable, stop and report it unavailable. There is no CLI fallback.
-
-## Advisory call
-
-```jsonc
-{
-  "project_id": "<project>",
-  "slug": "<blueprint-slug>",
-  "purpose": "delivery",
-  "base_ref": "<full-base-sha>",
-  "authority_ref": "<full-head-sha>",
-  "provider": "grok",
-  "repository_access": "none",
-  "mode": "advisory",
-}
-```
-
-Use authoritative mode only when formal plan or delivery approval is requested.
-
-## Model policy
-
-When the user names an exact model, pass it in the MCP `model` field. Otherwise omit
-that field and let the MCP owner select the configured provider default.
-
-## Review quality
-
-Follow `catalog/agent/rules/review-methodology-sota.md`; report typed verdict, model,
-artifact, grounded findings, and independently verified conclusions.