gm-skill 2.0.1196 → 2.0.1198

package/README.md

@@ -35,7 +35,7 @@ An earlier generation fanned out fifteen per-platform downstream repos (gm-cc, g
 
 ## Version
 
-`2.0.1196` — auto-bumped from the canonical `gm` repo. Every push to `AnEntrypoint/gm` (or any cascading sibling crate) republishes this package.
+`2.0.1198` — auto-bumped from the canonical `gm` repo. Every push to `AnEntrypoint/gm` (or any cascading sibling crate) republishes this package.
 
 ## Source of truth
 

package/bin/plugkit.version

@@ -1 +1 @@
-0.1.436
+0.1.438

package/bin/plugkit.wasm.sha256

@@ -1 +1 @@
-ca58e233ebbc1650a7973b0e5e1bef8f0cd178d819ba2755eaa7cbb308c56be7  plugkit.wasm
+993680a7b6d2c7625c0cfc7627e3135cc6673bb9e3ac55fb241270929ba5b60b  plugkit.wasm

package/gm.json

@@ -1,6 +1,6 @@
 {
   "name": "gm",
-  "version": "2.0.1196",
+  "version": "2.0.1198",
   "description": "Spool-dispatch orchestration engine with unified state machine, skills, and automated git enforcement",
   "author": "AnEntrypoint",
   "license": "MIT",
@@ -17,5 +17,5 @@
   "publishConfig": {
     "access": "public"
   },
-  "plugkitVersion": "0.1.436"
+  "plugkitVersion": "0.1.438"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gm-skill",
-  "version": "2.0.1196",
+  "version": "2.0.1198",
   "description": "Canonical universal harness — AI-native software engineering via skill-driven orchestration; bootstraps plugkit for task execution and session isolation. Install in any AI coding agent host.",
   "author": "AnEntrypoint",
   "license": "MIT",
@@ -39,7 +39,7 @@
     "gm.json"
   ],
   "dependencies": {
-    "gm-plugkit": "^2.0.1196"
+    "gm-plugkit": "^2.0.1198"
   },
   "engines": {
     "node": ">=16.0.0"

package/skills/gm-skill/SKILL.md

@@ -1,25 +1,27 @@
 ---
 name: gm-skill
-description: AI-native software engineering harness. Every action routes through plugkit via the spool. The agent dispatches verbs; plugkit owns phase, mutables, PRD, recall, instructions, the four-gate filter, and every other concern.
+description: AI-native engineering harness. Plugkit-served instruction stream; three-layer admission filter (cost, bounds, direction) gates every mutation; PRD-DAG covers the destructive transform's closure; emit the mature artifact, not the scaffold.
 allowed-tools: Skill, Read, Write, Bash(node *), Bash(bun *)
 ---
 
 # gm — only plugkit
 
-Plugkit owns the discipline. Every turn, dispatch the `instruction` verb and follow the prose it returns. Every candidate mutation runs through the four-gate filter plugkit serves: G1 cost → G2 bound → G3 distance → G4 trajectory. Any reject defers or discards. Read/Edit/Bash/Grep/Glob before the first `instruction` dispatch is the failure mode this skill prevents — every one of those is a step taken outside the loop, and the loop is the work.
+Plugkit owns the discipline. Every turn: dispatch `instruction`, follow the prose. Every candidate operation traverses the three-layer admission filter — L1 cost (empirical baseline; recall+codesearch fan-out probes it) → L2 bounds (`|F|=1` single-writer per surface; PRD/mutables/KV are the central stores) → L3 direction (Lyapunov criterion; mutations must monotonically decrease distance-to-goal; audit tuple `(id, hash, ts)` per accepted write). Reject → defer or discard.
 
-If `.gm/exec-spool/.status.json` is absent or its `ts` is older than 15s, boot the watcher first — the one thing this skill does directly, because nothing else can be served until the spool is alive:
+Read/Edit/Bash/Grep/Glob before the first `instruction` dispatch IS the failure this skill prevents — each is a step outside the loop, and the loop is the work.
+
+If `.gm/exec-spool/.status.json` is absent or stale (>15s), boot the watcher — the one direct action this skill permits:
 
 ```
 bun x gm-plugkit@latest spool > /dev/null 2>&1 &
 ```
 
-(`npx -y gm-plugkit@latest spool > /dev/null 2>&1 &` if `bun` is missing.) Wait 2s, confirm `.status.json` heartbeat is fresh, then proceed.
+(`npx -y gm-plugkit@latest spool > /dev/null 2>&1 &` if `bun` missing.) Wait 2s, confirm fresh heartbeat, proceed.
 
-Now dispatch `instruction` by writing an empty body to `.gm/exec-spool/in/instruction/<N>.txt` and reading the response from `.gm/exec-spool/out/instruction-<N>.json`. The response carries the active phase prose, the PRD, the open mutables, prior recall, the four-gate framing for the phase, and every signal that should shape the next action. Follow that prose imperatively. When its exit condition is met, dispatch `transition`. The chain runs PLAN → EXECUTE → EMIT → VERIFY → COMPLETE under plugkit's direction; this skill does not duplicate the prose, does not enumerate verbs, does not describe the dispatch format — plugkit serves all of it on demand.
+Now dispatch `instruction` (empty body → `in/instruction/<N>.txt`). Response carries the active phase prose, PRD, open mutables, prior recall, the three-layer framing for this phase, and every signal the next action needs. Follow imperatively. Exit condition met → `transition`. Chain runs PLAN → EXECUTE → EMIT → VERIFY → COMPLETE under plugkit's direction; this skill does not duplicate prose, enumerate verbs, or describe the dispatch ABI — plugkit serves all of it on demand.
 
-Nothing else lives here. Every concern that feels like it belongs in this file — how to batch, what verbs exist, when to scan for residuals, how the browser surface works, where the watcher logs go, how updates land, when to stop, which closure shapes are forbidden — is served by `instruction` when the moment calls for it. Trying to remember it from this skill instead of asking plugkit is forced closure: the agent acts on a stale snapshot of policy instead of the live one plugkit holds.
+Maturity-first invariant: emit the closure of the destructive transform the request admits, not a scaffold + "Phase 2 next session" IOU. Partial emits are non-monotonic, L3-rejected. If closure exceeds session reach, that's a Maximal Cover decomposition (PRD-DAG enumeration), never a TODO-launder.
 
-Memory writes route through `memorize-fire` only. Questions to the user fire last — after the four gates, scope-expansion, and a `WebSearch`/`WebFetch` pack have all closed empty. `AskUserQuestion` mid-iteration to pick between viable approaches IS the forced-closure deviation the filter rejects.
+Memory writes route through `memorize-fire` only — native memory surfaces are invisible to recall and forbidden. Questions to user fire last, after the three layers, scope-expansion, and a `WebSearch`/`WebFetch` pack all close empty. `AskUserQuestion` mid-iteration to pick between viable approaches IS the L3 violation the filter rejects (low-cost narrative substituting for an audited mutation).
 
 Only plugkit.