gm-skill 2.0.2550 → 2.0.2552

package/AGENTS.md

@@ -28,7 +28,7 @@ Repo root = package root = published `gm-skill` npm package; no factory, no sepa
 
 ## 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 and the redundant `gm-runner` native host are both retired and removed from the tree -- there is no fallback loader; agentplug-runner is required.
+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`).
 
@@ -181,8 +181,6 @@ Push to any rs-* sibling -> `cascade.yml` -> rs-plugkit `release.yml` -> single
 
 **Submodule pointers auto-sync via `.github/workflows/submodule-sync.yml`**, 30min schedule. Mechanics + manual-recovery fallback: the recall store (`recall: gm submodule pointer auto-sync mechanics`).
 
-The `gm-runner` crate and its separate `gm-runner.yml` CI workflow are retired along with the binary itself (see the WASM-guest section above) -- confirmed absent from rs-plugkit's `crates/` and `.github/workflows/`, no longer a stage in the cascade.
-
 **The three agentplug-* wasm-plugin repos (agentplug-bert, agentplug-libsql, agentplug-treesitter) share one reusable release workflow** hosted in rs-plugkit (`wasm-plugin-release.yml`, `workflow_call`). Parameterization + the build_env/pre_build_steps quoting caveat: the recall store (`recall: gm cascade pin-toil design`).
 
 **Repos involved (push to any triggers cascade):** `AnEntrypoint/{rs-codeinsight, rs-search, rs-plugkit, gm}`. rs-learn and rs-exec are retired (crates removed from / never depended on by rs-plugkit; their spool-dispatch and memory surfaces reimplemented natively in rs-plugkit wasm_dispatch; repos archived as tombstones, README points at rs-plugkit). Roles, npm package names, legacy-retirement detail: the recall store (`recall: cascade repos involved roles`, `recall: legacy gm-skill variants retired`).

package/bin/plugkit-slim.wasm.sha256

@@ -1 +1 @@
-01fc6c2d0b45f7d77b2f2fd47b2f111709e2c4c94e096f07546a092ec6397959  plugkit-slim.wasm
+1639ed3b402eaf95b51e5b70cfec4d3c5bff02b2f0fc72a9a5f6b384fd466a76  plugkit-slim.wasm

package/bin/plugkit.version

@@ -1 +1 @@
-0.1.1205
+0.1.1206

package/bin/plugkit.wasm.sha256

@@ -1 +1 @@
-6013a4d890cd15b8b6f555e3801eef7dd57062c56f683145ec6e200b90ec850a  plugkit.wasm
+a33a046f994b625201664aed7f404c19c9e2ae8aac785466bc8db1ab34c33936  plugkit.wasm

package/gm-plugkit/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gm-plugkit",
-  "version": "2.0.2550",
+  "version": "2.0.2552",
   "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 @@
-01fc6c2d0b45f7d77b2f2fd47b2f111709e2c4c94e096f07546a092ec6397959  plugkit-slim.wasm
+1639ed3b402eaf95b51e5b70cfec4d3c5bff02b2f0fc72a9a5f6b384fd466a76  plugkit-slim.wasm

package/gm-plugkit/plugkit.version

@@ -1 +1 @@
-0.1.1205
+0.1.1206

package/gm.json

@@ -1,6 +1,6 @@
 {
   "name": "gm",
-  "version": "2.0.2550",
+  "version": "2.0.2552",
   "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.1205"
+  "plugkitVersion": "0.1.1206"
 }

package/package.json

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

@@ -48,10 +48,22 @@ means unavailable: fall back, never retry blindly. Where served: `codesearch`
 `transition`, `phase-status`, `filter`. `git_finalize {message}` bundles
 add->commit->porcelain-gate->push->CI-watch; where absent, compose it.
 
-`browser` body is plain-text prefixed, never CLI flags: `session
+`browser` runs a headless engine (oxibrowser, pure Rust) by default -- fast,
+no Chrome process, but a narrower surface: navigate/evaluate/dom-query/
+extract-markdown only, one implicit session per instance (`session
+new/close/reset` are accepted no-ops), and no screenshot/capture/profile/
+trace/viewport. `cdp` is the same plain-text-body contract driving real
+Chrome over CDP (playwright-style) for anything `browser` cannot do yet --
+full CSS/layout fidelity, real screenshots, devtools-dependent sites, or
+genuine multi-tab sessions. A `browser` dispatch that fails or names an
+unsupported mode returns a `note` pointing at `cdp`; try that next rather
+than reworking the `browser` call.
+
+Both verbs share one plain-text body grammar, never CLI flags: `session
 new|list|close <id>|reset <id>`, `timeout=<ms>`, `url=<target>`,
-`screenshot[=name]`, `dom=<selector>`, or bare JS. Prefixes stack. Sessions
-persist Chrome across dispatches. Every response carries `result.debug`.
+`screenshot[=name]`, `dom=<selector>`, or bare JS. Prefixes stack. `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.