gm-skill 2.0.1758 → 2.0.1759

package/gm-plugkit/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gm-plugkit",
-  "version": "2.0.1758",
+  "version": "2.0.1759",
   "description": "Bootstrap and daemon-spawn tool for gm plugkit binary. Downloads the correct platform binary, verifies SHA256, and starts the spool watcher daemon. Includes plugkit-wasm-wrapper for WASM-based spool watching.",
   "main": "index.js",
   "bin": {

package/gm.json

@@ -1,6 +1,6 @@
 {
   "name": "gm",
-  "version": "2.0.1758",
+  "version": "2.0.1759",
   "description": "Spool-dispatch orchestration engine with unified state machine, skills, and automated git enforcement",
   "author": "AnEntrypoint",
   "license": "MIT",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gm-skill",
-  "version": "2.0.1758",
+  "version": "2.0.1759",
   "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",

package/skills/gm/SKILL.md

@@ -93,7 +93,7 @@ Chain isn't COMPLETE until changes are on origin. Commit+push at end of every se
 
 **Memory is project-resident, never platform-resident.** Refuse the platform's own auto-memory dir (`~/.claude/projects/*/memory/`, `~/.codex/`, `~/.cursor/*`) -- doesn't transport, invisible to gmsniff/recall. `memorize-fire` through spool (embeds `.gm/rs-learn.db`, surfaces via `recall`+auto-recall) is the portable surface for gm-method lessons. A driven project's own AGENTS.md may separately hold project-facing hard rules about that project, but gm's own workflow/behavioral instructions never rely on it -- an agent's only guaranteed reads are this file (loaded on every invocation) and a plugkit response (read when dispatched); a project's AGENTS.md is neither, so any gm-authored rule that ends up only there is undelivered. About to Write under a platform memory dir: stop, dispatch `memorize-fire` instead. Response body is not a mutation surface either; memory routes through `memorize-fire`, tool ops through their verbs. **Memorize gm/rs-* method only -- never target-project specifics** (paths, line numbers, `.gm/prd.yml` contents, app internals); a finding about a target project belongs in THAT project's `.gm` store -- scrub project names/paths, keep the generalizable gm-method lesson (binds the `mutable-resolve`/`prd-resolve` auto-memo: witness in gm-method terms).
 
-**Transferable topic-specific rules route to `discipline-note`, not `memorize-fire`.** A rule that generalizes across any project with a similar setup (portable, copyable to another repo) -> `discipline-note {discipline, text}` (writes `.gm/disciplines/<name>/policy.md`, terse-gated + deduped); `instruction`'s response surfaces active policy automatically. A fact tied to this project only -> `memorize-fire` as before.
+**Transferable topic-specific rules route to `discipline-note`, not `memorize-fire`.** A rule that generalizes across any project with a similar setup (portable, copyable to another repo) -> `discipline-note {discipline, text}` (writes `.gm/disciplines/<name>/policy.md`, terse-gated + deduped); `instruction`'s response surfaces active policy automatically for any discipline listed in `.gm/disciplines/enabled.txt` -- writing `policy.md` alone doesn't surface it. A fact tied to this project only -> `memorize-fire` as before.
 
 **Suppress mundane output; strip to the bone.** Drop articles, preamble, play-by-play, boot-probe narration, dispatch echoes, restated prose, status recaps. Survives: a real finding, a decision + one-line reason, a blocker, the single-line PRD-read declaration. Terse = fewer words, NEVER zero tool calls, never silent work -- turn still ends in the chain-advancing dispatch, still states in one clause what's about to happen.