gm-skill 2.0.2308 → 2.0.2310

package/AGENTS.md

@@ -22,7 +22,9 @@ Skills encode environment-specific constraints that override general knowledge.
 
 # Architecture & Philosophy
 
-Repo root = package root = published `gm-skill` npm package; no factory, no separate build-output dir. Entry: `skills/gm/SKILL.md`. Orchestration lives in rs-plugkit, served on-demand via `instruction`. The 11 phase-prose files (entry/specify/prove/emit/state/conc/sec/res/decide/update_docs/browser) live single-sourced inside rs-plugkit itself (`crates/plugkit-core/src/orchestrator/instructions/prose/*.md`, `include_str!`'d at build) -- a prose edit there requires a Rust rebuild via the normal cascade, no cross-repo sync step. `prose.rs::resolve()` is the per-key three-tier override chain (project file -> source-repo cache -> compiled default) covering phase prose, gate-denial text, and residual copy alike; edit `gm-plugkit/instructions/` to change this repo's own provisioned defaults. Chain detail: the recall store (`recall: string-externalization project`).
+Repo root = package root = published `gm-skill` npm package; no factory, no separate build-output dir. Entry: `skills/gm/SKILL.md`. Orchestration lives in rs-plugkit, served on-demand via `instruction`.
+
+**`AnEntrypoint/gm-config` is the authored source.** It holds phase prose, gates, residual copy, and the FSM graph. rs-plugkit pulls from it at runtime; it never pushes into it. `prose.rs::resolve()` is the per-key three-tier chain: project-vendored `.gm/instructions/<key>.md`, then `gm-config`'s cached checkout, then a compiled Rust default. `fsm::graph()` runs the same chain for `fsm/graph.json`. `config::resolve()`'s `ImplicitDefaultRepo` tier clones `gm-config` with zero configuration and re-checks it on a debounce (`config_sync.rs`, default 15 min). A hand edit to `gm-config` reaches every project on its next debounce window, with no rs-plugkit rebuild and no release. The 11 phase-prose `.md` files under `crates/plugkit-core/src/orchestrator/instructions/prose/` (entry/specify/prove/emit/state/conc/sec/res/decide/update_docs/browser), `include_str!`'d at build, are that compiled default. They serve only as an emergency fallback. They fire when `gm-config` is genuinely unreachable: offline, a cold start with no cache yet, a network outage. They are never the source of truth. `Outcome::ConfigRepoUnreachable` marks that emergency-fallback case apart from the healthy no-override case, surfaced to the agent as `config_repo_unreachable` on every `instruction`/`transition` response. To run a different default set, fork `gm-config` and point `.gm/config.source.json` at the fork. Editing the compiled `.md` files in rs-plugkit itself never changes what a project resolves. Chain detail: the recall store (`recall: string-externalization project`).
 
 ## WASM guest, one native host (agentplug-runner is the sole loader)
 

package/gm-plugkit/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gm-plugkit",
-  "version": "2.0.2308",
+  "version": "2.0.2310",
   "description": "Bootstrap and daemon-spawn tool for gm plugkit binary. Downloads the correct platform wasm, verifies SHA256, and launches agentplug-runner (the native wasm host) as the spool watcher daemon.",
   "main": "index.js",
   "bin": {

package/gm.json

@@ -1,6 +1,6 @@
 {
   "name": "gm",
-  "version": "2.0.2308",
+  "version": "2.0.2310",
   "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.2308",
+  "version": "2.0.2310",
   "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

@@ -128,4 +128,4 @@ Memory via `memorize-fire` dispatch stores in `.gm/rs-learn.db` and is retrieved
 
 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 (SPECIFY/PROVE/EMIT/STATE/CONC/SEC/RES/DECIDE, gate reasons, deviation text) is served live by rs-plugkit's `instruction` verb from compiled Rust consts -- not authored in this file. Resolution is three-tier, per key, each tier overriding the one before: (1) `.gm/instructions/<key>.md` local vendored override, always wins; (2) a configured source repo synced by the daemon into `.gm/instructions-source-cache/` when `.gm/instructions/source.json` ({repo, branch, path}) is present -- lets an org or project pull shared prose from any git repo without forking rs-plugkit; (3) the compiled-in default, the final fallback. A skill-improvement pass (e.g. workflow-forge) editing only this file's numbered steps misses that entire layer: changing the compiled default means editing `rs-plugkit/crates/plugkit-core/src/orchestrator/instructions/prose/*.md` directly (single-sourced there, `include_str!`'d at build) -> 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.
+**This file is not gm's whole procedure.** The phase-specific behavioral prose lives elsewhere: SPECIFY/PROVE/EMIT/STATE/CONC/SEC/RES/DECIDE, gate reasons, and deviation text. rs-plugkit's `instruction` verb serves it live from `AnEntrypoint/gm-config`, not from this file. Resolution is three-tier, per key, each tier overriding the one before. Tier one: `.gm/instructions/<key>.md`, a local vendored override, always wins. Tier two: `gm-config`'s cached checkout, consulted with zero configuration by default. Point `.gm/config.source.json` at a fork or a private repo to use a different one. Tier three: a compiled-in Rust default. It serves only as an emergency fallback when `gm-config` is genuinely unreachable. A skill-improvement pass (for example workflow-forge) that edits only this file's numbered steps misses that entire layer. The actual served prose lives in `gm-config`'s `prose/*.md`. Edit it and push it directly to `gm-config` main -- no rs-plugkit rebuild, no cascade, no release. Editing `rs-plugkit/crates/plugkit-core/src/orchestrator/instructions/prose/*.md` changes only the emergency fallback text. It never changes what a healthy project resolves. This file holds only invocation syntax, transition markers, gate-condition summaries, spool-dispatch mechanics, and constraints. It is the boot-edge ABI a skill-runner uses before the served prose takes over.