gm-skill 2.0.2099 → 2.0.2101

package/AGENTS.md

@@ -22,13 +22,13 @@ 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 8 phase-prose files (entry/plan/execute/emit/verify/consolidate/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 only override mechanism, a per-key three-tier chain: `.gm/instructions/<key>.md` (per-project vendored file, always wins) -> a configured source-repo's synced cache (`.gm/instructions/source.json` + `.gm/instructions-source-cache/<key>.md`) -> the compiled default. The same chain covers gate-denial and residual copy (deviation text, gate reasons) -- `gates.rs`/`residual.rs` call `prose::resolve("gates/<key>", default)`/`prose::resolve("residual/<key>", default)` at each call site (e.g. `residual.rs`'s `residual/prd-open`, `residual/browser-open`, `residual/tasks-running`, `residual/imperative`), so these ARE file-override-able exactly like phase prose, via `.gm/instructions/gates/<key>.md` / `.gm/instructions/residual/<key>.md`. `gm-plugkit/instructions/gates/` and `gm-plugkit/instructions/residual/` are the real, git-tracked source directories for this repo's own provisioned defaults, vendored into `.gm/instructions/gates/` and `.gm/instructions/residual/` at bootstrap -- both directories and their files genuinely exist in this repo, edit the `gm-plugkit/instructions/` source copy to change gm's own provisioned defaults. Detail in 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`. The 8 phase-prose files (entry/plan/execute/emit/verify/consolidate/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`).
 
 ## WASM guest, one native host (agentplug-runner is the sole loader)
 
 Plugkit-core = the wasm cdylib guest (the gm brain), published as `plugkit.wasm`/`plugkit-slim.wasm` from `AnEntrypoint/plugkit-bin` by the cascade. It is host-agnostic, and `agentplug-runner` is the SOLE host that loads it. The JS wasm-host (`plugkit-wasm-wrapper.js` + `gm-plugkit/wrapper/`) and the redundant `gm-runner` native host are both retired -- there is no fallback loader; agentplug-runner is required.
 
-**`agentplug-runner`** (repo `AnEntrypoint/agentplug`, published to `AnEntrypoint/agentplug-bin`) is a real native wasmtime binary that loads gm.wasm as one plugin among siblings (`bert`/`libsql`/`treesitter`), routing gm.wasm's `host_plugin_call`/`host_vec_embed` to those shared plugins. This is why gm fetches `plugkit-slim.wasm` (no baked-in embedding weights -- bert supplies them out-of-wasm). `.status.json` `runtime` reads `agentplug`. Browser is driven via direct CDP and task via a native process registry, both native in agentplug-host (agentplug's `crates/agentplug-host/src/browser.rs` has its own embedded `cdp_eval.js`, so the browser verb needs nothing from the retired JS wrapper).
+**`agentplug-runner`** (repo `AnEntrypoint/agentplug`, published to `AnEntrypoint/agentplug-bin`) is a real native wasmtime binary that loads gm.wasm as one plugin among siblings (`bert`/`libsql`/`treesitter`), routing gm.wasm's `host_plugin_call`/`host_vec_embed` to those shared plugins -- browser and task are both native in agentplug-host, needing nothing from the retired JS wrapper. Full mechanics: the recall store (`recall: agentplug-runner wasmtime plugin loading mechanics`).
 
 The `gm-plugkit` npm identity stays load-bearing as the thin launcher edge only: `bun x gm-plugkit@latest spool` (`cli.js::tryDelegateToRunner`) re-execs into `~/.gm-tools/agentplug-runner` and exits; `bootstrap.js` still seeds per-project wiring and downloads `plugkit.wasm`/`plugkit-slim.wasm` (sha256-pinned) from `plugkit-bin`. `startSpoolDaemon()` launches agentplug-runner or, when it is absent, fails loudly with an actionable install message -- there is no silent no-loader state. Size + embedded-model mechanics: the recall store (`recall: WASM-only plugkit size mechanics`).
 

package/gm-plugkit/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gm-plugkit",
-  "version": "2.0.2099",
+  "version": "2.0.2101",
   "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.2099",
+  "version": "2.0.2101",
   "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.2099",
+  "version": "2.0.2101",
   "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",