gm-skill 2.0.2559 → 2.0.2560

package/AGENTS.md

@@ -30,7 +30,7 @@ Repo root = package root = published `gm-skill` npm package; no factory, no sepa
 
 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 and the redundant `gm-runner` native host (crate and `gm-runner.yml` CI workflow) are both retired and removed from the tree -- absent from rs-plugkit's `crates/` and `.github/workflows/`, no longer a stage in the cascade; 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 -- 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`).
+**`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. The `browser` verb defaults to oxibrowser (pure-Rust, headless, `agentplug/crates/agentplug-host/src/oxibrowser_driver.rs`); the `cdp` verb (`rs-plugkit/crates/plugkit-core/src/wasm_dispatch/verbs.rs`) drives real Chrome over CDP for screenshots, full layout fidelity, and multi-tab sessions oxibrowser cannot do. Both share one plain-text body grammar. Full mechanics: the recall store (`recall: agentplug-runner wasmtime plugin loading mechanics`, `recall: browser cdp oxibrowser split`).
 
 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` and exits -- there is no silent no-loader state. The launcher-edge install path (`~/.gm-tools`) and the runner's own runtime state (`~/.agentplug`) are two different directories; always check `~/.agentplug/plugins/gm.version` for what is actually being served, never `~/.gm-tools`. Full path-split mechanics: the recall store (`recall: agentplug-runner runtime-state path split`). 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.2559",
+  "version": "2.0.2560",
   "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.2559",
+  "version": "2.0.2560",
   "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.2559",
+  "version": "2.0.2560",
   "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

@@ -63,8 +63,9 @@ Both verbs share one plain-text body grammar, never CLI flags: `session
 new|list|close <id>|reset <id>`, `timeout=<ms>`, `url=<target>`, `dom=<selector>`,
 or bare JS. Prefixes stack. `cdp` additionally accepts `screenshot[=name]`,
 `capture`, `profile`, `trace`, and `viewport=`, which `browser` rejects outright
-(see line 54-55). `cdp` sessions persist a real Chrome process across
-dispatches. Every response carries `result.debug`.
+(see line 54-55). Unlike `browser`'s no-op session commands, `cdp` sessions
+persist a real Chrome process across dispatches. Every response carries
+`result.debug`.
 
 Ground truth only: no mocks, fakes, or test files on disk. Verification is live
 witnessed execution, same turn as the work. Reasoning is execution, not monologue.