@webpresso/opencode-plugin 3.1.28 → 3.1.30

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@webpresso/opencode-plugin",
-  "version": "3.1.28",
+  "version": "3.1.30",
   "private": false,
   "description": "OpenCode plugin adapter package for Webpresso agent-kit.",
   "homepage": "https://github.com/webpresso/agent-kit#readme",

package/plugin-skill-ownership.json

@@ -2,7 +2,7 @@
   "schemaVersion": 1,
   "host": "opencode",
   "packageName": "@webpresso/opencode-plugin",
-  "packageVersion": "3.1.28",
+  "packageVersion": "3.1.30",
   "runtimeDirs": [],
   "skills": {
     "ai-deslop": {
@@ -39,7 +39,7 @@
       "digest": "sha256:306355888da0827e3523022077f731845726bbaaf595ca12515cc91d8605b5e6"
     },
     "fix": {
-      "digest": "sha256:6761e335ca1327d0dd12822886d5ea7f1b683f27caba62046cd0529c7cda7e44"
+      "digest": "sha256:2508fbad15af4ef828b668084cac950c98b8a232ce25c8152135788738e5f243"
     },
     "grok": {
       "digest": "sha256:07f2cdc58889f13f0869ddc153d465423cf2f4aae7b9deb4c4e427d2dba78a34"
@@ -90,7 +90,7 @@
       "digest": "sha256:953ab2625287866e5f27e602a89f1752e054d47522d04e1fdc11880867dc2fde"
     },
     "verify": {
-      "digest": "sha256:4c9d534c358456c1d34f9b4b919e70dd013164c7c89ca8229181b77e31bdc914"
+      "digest": "sha256:60de27bef39fd24041e1b78a276fc7ed2f38bc6d7ac5af88beba7eb6770a0119"
     }
   }
 }

package/skills/fix/SKILL.md

@@ -122,12 +122,15 @@ Run the narrowest checks that prove the repaired behavior on the real repo surfa
 - `wp_test` / targeted tests for the repaired path
 - `wp_lint` / `wp_typecheck` for changed surfaces
 - `wp_qa` only when the blast radius needs the bookend
+- Before push: `wp ci-preflight` (local pre-push owner). Do not use remote CI
+  re-runs as the primary fix loop (`ci-cost-local-first`).
 
 Rules:
 
 - Prefer MCP `wp_*` over raw host Bash.
 - Reuse fresh logs / session-memory indexed output; do not re-run long commands just to re-read.
 - Read the exit code and summary before making a claim.
+- Never `git push --no-verify` to land an unproven fix.
 
 Escalate to `/verify <target>` (local) or `/verify <target> --merge-ready` when any of these are true:
 

package/skills/verify/SKILL.md

@@ -109,6 +109,9 @@ workflow:
 1. Identify target type (file / package / blueprint slug / all).
 2. Map each claim you plan to make to the exact command or log that proves it.
 3. If the target is a blueprint slug, run the repo's blueprint show/audit surface and record the acceptance boxes that still need proof.
+4. **CI cost / local-first:** treat remote CI as confirmation, not the first
+   debugger. Load `ci-cost-local-first` expectations: no hook skips, no
+   blind `gh run rerun`, Ubicloud for private non-release jobs.
 
 ## Phase 1 — Governance gates
 
@@ -130,12 +133,27 @@ Run the narrowest checks that prove the touched behavior:
 - `wp_test` / targeted tests
 - `wp_qa`, `wp_e2e`, build / package checks only when the change requires them
 
+**Before push or PR open/update**, run the pre-push owner end-to-end:
+
+```bash
+wp ci-preflight
+```
+
+That is fail-fast branch-scoped format → guardrails → typecheck → lint →
+test. Agent-kit itself enforces it from `.husky/pre-push`; consumer repos may
+keep pre-push checks user-owned, so run the command explicitly before pushing.
+Do **not** claim push-ready if preflight failed. Do **not** bypass hooks to ship
+red work.
+
 Rules:
 
 - Prefer MCP `wp_*` 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 CI is already red: read the failed job log, reproduce with the matching
+  local `wp` command, fix, re-run `wp ci-preflight`, then push **one**
+  corrective commit — do not burn another full matrix “to check.”
 
 ## Phase 3 — Cross-surface impact scan