gm-skill 2.0.1897 → 2.0.1899

package/README.md

@@ -119,7 +119,19 @@ A push to `main` triggers `.github/workflows/publish.yml`:
 
 `.github/workflows/gh-pages.yml` builds the `site/` flatspace source to `dist/` and deploys to GitHub Pages.
 
-The plugkit wasm itself is built and released by [rs-plugkit](https://github.com/AnEntrypoint/rs-plugkit) on every push, published to npm as `plugkit-wasm` and to GitHub Releases as `plugkit-bin`. Bootstrapping the agent downloads the wasm at install time, it does not ship in this repo.
+The plugkit wasm itself is built and released by [rs-plugkit](https://github.com/AnEntrypoint/rs-plugkit) (submoduled at `rs-plugkit/`, source only -- see below) on every push, published to npm as `plugkit-wasm` and to GitHub Releases as `plugkit-bin`. Bootstrapping the agent downloads the compiled wasm at install time; the compiled binary itself does not ship in this repo, only the Rust source that builds it.
+
+## developing gm itself
+
+`rs-plugkit/` is a git submodule (rs-plugkit's Rust source, not a compiled artifact). A plain `git clone` leaves it empty -- clone with submodules, or init it after the fact:
+
+```
+git clone --recurse-submodules https://github.com/AnEntrypoint/gm.git
+# or, in an existing checkout:
+git submodule update --init --recursive
+```
+
+An empty `rs-plugkit/` directory after a normal `git clone` is expected, not a bug -- it only matters if you're changing rs-plugkit's own Rust source (orchestrator, gates, spool dispatch) rather than the skill/installer JS in this repo's own tree.
 
 ## license
 

package/gm-plugkit/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gm-plugkit",
-  "version": "2.0.1897",
+  "version": "2.0.1899",
   "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.1897",
+  "version": "2.0.1899",
   "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.1897",
+  "version": "2.0.1899",
   "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

@@ -99,3 +99,5 @@ Memory via `memorize-fire` dispatch stores in `.gm/rs-learn.db` and is retrieved
 `auto_recall` attaches to `instruction` responses on turn entry. `memorize-prune {key}` or `memorize-prune {query}` deletes or reviews memory entries.
 
 Subagent prompts should reference the gm skill and task specifics only, without restating verb names, spool paths, or protocol mechanics already supplied by invocation.
+
+**This file is not gm's whole procedure.** The phase-specific behavioral prose (PLAN/EXECUTE/EMIT/VERIFY/CONSOLIDATE, gate reasons, deviation text) is served live by rs-plugkit's `instruction` verb from compiled Rust consts, per-project-overridable via `.gm/instructions/<key>.md` -- not authored in this file. A skill-improvement pass (e.g. workflow-forge) editing only this file's numbered steps misses that entire layer: changing PLAN/EXECUTE prose routes through `gm-plugkit/instructions/*.md` -> `scripts/sync-instruction-consts.mjs` -> `rs-plugkit/src/orchestrator/instructions/*.rs` -> a push+CI+cascade rebuild, never a direct edit here. This file holds only: invocation syntax, transition markers, gate-condition summaries, spool-dispatch mechanics, and constraints -- the boot-edge ABI a skill-runner interacts with before the served prose takes over.