gm-skill 2.0.1856 → 2.0.1857

package/gm-plugkit/instructions/plan.md

@@ -34,6 +34,10 @@ Cut the cover hardest-node-first: the row exercising the most failure modes at o
 
 Any observation not yet a row -- outstanding work, unfinished surface, improvable shape, preference misalignment, adjacent concern -- is `prd-add` this turn; response-body-only observations evaporate at turn end. Structural noticing (coverage gap, missing doc, rule-violating prior commit) and preference-aware noticing (drift from density-at-PLAN/residual-triage/push-on-clean/every-possible-expansion/browser-witness) are the same event: each its own row, witnessed by what surfaced it.
 
+**A genuinely unrelated issue discovered mid-task is `prd-add`, never a same-turn detour and never dropped.** "Unrelated" means outside this cover's own closure -- a bug/gap/hygiene issue the current transform did not touch and does not depend on. It still gets a row (never silently ignored, never fixed inline burning the current cover's focus, never mentioned in prose and left unrecorded) so a later cover picks it up deliberately.
+
+`prd-resolve` accepts an optional `commit_comment` (aliases `commit_message`, `resolution_note`) alongside `id`/`witness_evidence` -- a one-line resolution note. When present, the next `git_commit`/`git_finalize` in that repo bundles it into the commit message body under a "Resolved PRD rows" section and clears the row from `.gm/prd.yml` (deleted, not archived -- the commit message is the durable record). Pass it whenever the resolved row's story is worth a line in git history; omit it for rows too granular to warrant one.
+
 ## Mutables
 
 Unknowns -> `.gm/mutables.yml` via `mutable-add`, `status: unknown`, witness = `file:line`/codesearch hit/exec output. Narrative resolution rejected; unwitnessed rows block every `transition`. Uncertain mid-plan (orient-to-PRD gap, unweighted recall hit) -> re-dispatch `instruction`, never invent the next step from memory.

package/gm-plugkit/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gm-plugkit",
-  "version": "2.0.1856",
+  "version": "2.0.1857",
   "description": "Bootstrap and daemon-spawn tool for gm plugkit binary. Downloads the correct platform binary, verifies SHA256, and starts the spool watcher daemon. Includes plugkit-wasm-wrapper for WASM-based spool watching.",
   "main": "index.js",
   "bin": {

package/gm.json

@@ -1,6 +1,6 @@
 {
   "name": "gm",
-  "version": "2.0.1856",
+  "version": "2.0.1857",
   "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.1856",
+  "version": "2.0.1857",
   "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

@@ -38,6 +38,8 @@ Code/file/symbol lookup uses `codesearch` (`{"query":"..."}`) or `recall` (prior
 
 Spool verbs are the primary interface: `codesearch`, `recall`, `fetch`, `exec_js`, `browser`, `memorize-fire`, git verbs (`git_status`, `git_log`, `git_diff`, `git_show`, `git_branch`, `git_add`, `git_commit`, `git_finalize`, `git_push`, `git_checkout`, `git_fetch`, `git_rm`, `git_revert`, `git_reset`). Git operations via Bash/PowerShell are recorded as `deviation.bash-git-bypass`. `git_finalize {message}` bundles add->commit->porcelain-gate->push in one dispatch.
 
+`prd-resolve` accepts an optional `commit_comment` (a one-line resolution note) alongside `id`/`witness_evidence`. When present, the row's note rides until the repo's next `git_commit`/`git_finalize`, which bundles every pending note for that repo into the commit message under a "Resolved PRD rows" section and clears those rows from `.gm/prd.yml`. Unrelated issues discovered mid-task are `prd-add`, never a same-turn detour and never dropped -- a later cover picks them up deliberately.
+
 Missing `.gm/exec-spool` on first use is normal. Boot the watcher before dispatching work.
 
 Boot probe at session start, one Bash call: