gm-skill 2.0.2308 → 2.0.2309

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.2309",
   "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.2309",
   "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.2309",
   "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",