gm-skill 2.0.2309 → 2.0.2311

package/README.md

@@ -143,7 +143,7 @@ Any project using gm can override its instruction prose, gate-denial text, resid
 { "repo": "https://github.com/your-org/your-gm-config", "branch": "main", "path": "" }
 ```
 
-The daemon clones and re-syncs that repo on a poll interval (default 600s, `.gm/daemon-config-reference.md`'s `plugin_update_poll_interval_secs`), so a push to your config repo reaches every project pointing at it within that window -- not instant, eventually consistent. Resolution order per key is always: your project's own `.gm/instructions/<key>.md` file wins outright, then your config repo's synced copy, then gm's compiled default. A malformed `source.json` or unreachable repo degrades to the compiled default and logs why -- it never crashes a dispatch. No project sets up `source.json` for itself before checking: gm ships pointed at `AnEntrypoint/gm-config` by default, so every fresh install already pulls from a shared config repo unless a project's own `source.json` says otherwise.
+The daemon clones and re-checks that repo on a debounce, default 15 minutes (`config_sync.rs`'s `DEFAULT_DEBOUNCE_MS`). A push to your config repo reaches every project pointing at it within that window -- not instant, eventually consistent. Resolution order per key is always the same three steps. Your project's own `.gm/instructions/<key>.md` file wins outright. Your config repo's synced copy is next. A compiled Rust default is last, served only as an emergency fallback. A malformed `source.json` or unreachable repo degrades to that fallback and logs why. It never crashes a dispatch. A prior good checkout keeps serving through a transient outage rather than being discarded. No project needs to set up `source.json` before this works: gm ships pointed at `AnEntrypoint/gm-config` by default. Every fresh install already pulls from a shared config repo unless a project's own `source.json` says otherwise.
 
 **WARNING: a config repo has the same authority as your own local git history, including code execution.** Gate hooks (arbitrary JS run at gate evaluation) execute from a synced config repo exactly as they would from a file in your own project. Anyone who can push to that repo, or compromise it, gets code execution on every machine syncing it -- there is no sandboxing, no local review step, no confirmation prompt. Only point `source.json` at a repo you trust with that level of access; the same trust model applies whether the repo is `AnEntrypoint/gm-config` or one your own org runs.
 
@@ -176,7 +176,7 @@ Eight git submodules, source only, none compiled artifacts:
 - **`agentplug/`** -- the native host that loads that wasm and drives `browser`/`task` natively via CDP, plus the shared-plugin loader
 - **`agentplug-bert`**, **`agentplug-libsql`**, **`agentplug-treesitter`** -- the shared native plugins agentplug loads alongside the gm wasm (embeddings, vector storage, syntax parsing)
 - **`rs-codeinsight`**, **`rs-search`** -- codebase-indexing and search backends the `codesearch` verb consumes
-- **`gm-config/`** -- the default remote-config repo (prose, FSM graph, gate hooks, policy), a regenerated snapshot of the compiled defaults; gm points at it out of the box unless a project or user configures its own
+- **`gm-config/`** -- the default remote-config repo: prose, FSM graph, gate hooks, policy. Edited directly and pulled from at runtime. gm points at it out of the box unless a project or user configures its own.
 
 A plain `git clone` leaves all eight empty -- clone with submodules, or init them after the fact:
 

package/bin/plugkit-slim.wasm.sha256

@@ -1 +1 @@
-c751f13beeea2ea6bdafc394d63139a6146e06bb214b771084111713e92b021d  plugkit-slim.wasm
+8d39561fb13f9e1df66bca3e6d7fff012518b310a71ce438e5e08343e584a4cf  plugkit-slim.wasm

package/bin/plugkit.version

@@ -1 +1 @@
-0.1.1080
+0.1.1081

package/bin/plugkit.wasm.sha256

@@ -1 +1 @@
-fb23be5857a40c4aab205bd399cf207b473ab5ca76cafd9689eff3c2f77380ce  plugkit.wasm
+4a74680391a6757e9f5586759bc823d4386be3d4e65b821a32d64e190536ae3d  plugkit.wasm

package/gm-plugkit/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gm-plugkit",
-  "version": "2.0.2309",
+  "version": "2.0.2311",
   "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-plugkit/plugkit-slim.wasm.sha256

@@ -1 +1 @@
-c751f13beeea2ea6bdafc394d63139a6146e06bb214b771084111713e92b021d  plugkit-slim.wasm
+8d39561fb13f9e1df66bca3e6d7fff012518b310a71ce438e5e08343e584a4cf  plugkit-slim.wasm

package/gm-plugkit/plugkit.version

@@ -1 +1 @@
-0.1.1080
+0.1.1081

package/gm.json

@@ -1,6 +1,6 @@
 {
   "name": "gm",
-  "version": "2.0.2309",
+  "version": "2.0.2311",
   "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.1080"
+  "plugkitVersion": "0.1.1081"
 }

package/package.json

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