gm-skill 2.0.2172 → 2.0.2173

package/AGENTS.md

@@ -30,11 +30,11 @@ Plugkit-core = the wasm cdylib guest (the gm brain), published as `plugkit.wasm`
 
 **`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`).
+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 the `agentplug-runner` executable staged at `~/.gm-tools/agentplug-runner` (gm-plugkit's own launcher-edge install location) and exits. **The executable's own runtime state lives elsewhere**: `agentplug-host::install_dir()` resolves to `~/.agentplug`, not `~/.gm-tools` -- every plugin wasm/version marker (`~/.agentplug/plugins/<name>.wasm`, `<name>.version`), `daemon-status.json`, `daemon-registry.txt`, and `daemon-config.json` live under `~/.agentplug`, fully independent of gm-plugkit's own launcher-edge files under `~/.gm-tools` (which still holds gm-plugkit's own `plugkit.wasm`/`plugkit-slim.wasm`/`plugkit.version` for the pre-agentplug JS-wrapper code path, now dormant once delegation succeeds). Inspecting the wrong directory for the live-served gm.wasm version is the single most likely false-alarm source when diagnosing update-path issues -- always check `~/.agentplug/plugins/gm.version`, never `~/.gm-tools/plugins/gm.version` or `~/.gm-tools/plugkit.version`, to see what agentplug-runner is actually serving. `bootstrap.js` still seeds per-project wiring and downloads `plugkit.wasm`/`plugkit-slim.wasm` (sha256-pinned) from `plugkit-bin` into `~/.gm-tools`, but this path is bypassed entirely once `tryDelegateToRunner` succeeds (the common case whenever `~/.gm-tools/agentplug-runner.exe` exists) -- `plugkit-slim.wasm` at the `~/.gm-tools` top level is therefore normally ABSENT by design on a machine where agentplug-runner is doing the serving; that is not a bootstrap failure. `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`).
 
 **`bin/install.js` hard-requires agentplug-runner.** It downloads the sha256-verified native runner from `AnEntrypoint/agentplug-bin` for the host platform, and if none is published (or the download/verify fails) it fails the install loudly with a clear message rather than leaving the user with no loader. There is no JS-host fallback to silently fall through to anymore.
 
-**agentplug-runner auto-updates the wasm it serves, not itself.** Polls `plugkit-bin` every 600s; executable self-update is `bin/install.js` re-run or the daemon's own takeover-handoff protocol. Full mechanics: the recall store (`recall: agentplug daemon.rs self-update handoff protocol`).
+**agentplug-runner auto-updates the wasm it serves, not itself.** Polls `plugkit-bin` every 600s; executable self-update is `bin/install.js` re-run or the daemon's own takeover-handoff protocol. Full mechanics: the recall store (`recall: agentplug daemon.rs self-update handoff protocol`). The poll's own liveness is observable directly: `~/.agentplug/daemon-status.json` carries `last_plugin_update_poll_ts`/`last_runner_update_poll_ts`, refreshed every `plugin_update_poll_interval_secs`/`runner_update_poll_interval_secs` tick (600s default each) -- a null or stale value there, not a `.update-check-cache.json`/`.wasm-update-respawn-guard.json` file, is the live signal (those two filenames belong solely to the retired `plugkit-wasm-wrapper.js` JS host and are never written by agentplug-runner; their staleness once agentplug-runner is the active loader is expected, not a defect). A plugin whose installed `.version` marker is not real release semver (e.g. a hand-built `0.0.0-local-dev` sideload) is never silently auto-overwritten -- the daemon warns loudly to stderr at both boot and every stale-poll tick, and records `~/.agentplug/plugins/<name>.local-dev-sideload.json` so the state is queryable rather than indistinguishable from a released build.
 
 Wasm host-import link-module rule (`#[link(wasm_import_module="env")]` on every host-import extern block, every dep crate): the recall store (`recall: wasm host-import link-module trap`).
 

package/gm-plugkit/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gm-plugkit",
-  "version": "2.0.2172",
+  "version": "2.0.2173",
   "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.2172",
+  "version": "2.0.2173",
   "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.2172",
+  "version": "2.0.2173",
   "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",