gm-qwen 2.0.749 → 2.0.750

package/gm.json

@@ -1,6 +1,6 @@
 {
   "name": "gm",
-  "version": "2.0.749",
+  "version": "2.0.750",
   "description": "State machine agent with hooks, skills, and automated git enforcement",
   "author": "AnEntrypoint",
   "license": "MIT",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gm-qwen",
-  "version": "2.0.749",
+  "version": "2.0.750",
   "description": "State machine agent with hooks, skills, and automated git enforcement",
   "author": "AnEntrypoint",
   "license": "MIT",

package/skills/gm/SKILL.md

@@ -72,6 +72,16 @@ Refusal is forced closure. Refusing the task because part of it is hard is the i
 
 **Required move when scope exceeds reach**: identify the bounded subset that IS witnessable from this session, write a PRD covering only that subset, execute it, and at end-of-turn name the residual scope as a follow-up item — never as a refusal. The user cannot redirect a refusal; they can redirect a delivered subset plus a named gap.
 
+## FIX ON SIGHT — HARD RULE
+
+Any issue surfaced during work — failing test, exec stderr, CI red, lint warning, type error, broken import, runtime exception, deprecation warning, unexpected output, dead code, bad data — gets fixed THIS turn, in-band. Never defer, never suppress, never note-and-move-on.
+
+Forbidden: `// TODO fix later` | catching to ignore | `2>/dev/null` to hide | "out of scope" when scope is the same file | "we can address that next session" | leaving a red CI to ship docs | merging around a failing assertion | adding `.skip` / `xit` / `it.todo`.
+
+Required: surface → diagnose → fix at root cause → re-witness → continue. If the fix uncovers a new unknown, regress to `planning`. If the fix is genuinely out-of-scope-irreversible, write a `.gm/prd.yml` item for it BEFORE moving on — never just narrate it away.
+
+A skill chain that shipped while ignoring a known-bad signal is a forced-closure failure (see LAWFUL DOWNGRADE).
+
 ## EXECUTION ORDER
 
 1. Recall — `plugkit recall` for any familiar-feeling unknown (cheapest, 200 tokens)

package/skills/gm-complete/SKILL.md

@@ -89,6 +89,10 @@ Stop hook watches all GitHub Actions runs for the pushed HEAD. Do not call `gh r
 - Failure → Stop blocks with run names+IDs → investigate with `gh run view <id> --log-failed`, fix, push, hook re-watches
 - Deadline 180s (override `GM_CI_WATCH_SECS`) → slow jobs get "still in progress" approve
 
+## FIX ON SIGHT — HARD RULE
+
+Any issue surfaced during verify (test.js failure, browser-validation mismatch, CI red, git-status dirt, hygiene-sweep finding, stress-suite flunk, observability gap) is fixed in-band before declaring complete. Never paper over, never `.skip`, never ship-and-followup, never silence stderr/CI signals. Failure routes to the owning phase: broken output → `gm-emit` | wrong logic → `gm-execute` | new unknown → `planning`. Never declare COMPLETE while a known-bad signal is live.
+
 ## HYGIENE SWEEP
 
 Before declaring complete:

package/skills/gm-emit/SKILL.md

@@ -67,6 +67,10 @@ console.log(await fn(realInput));
 - All facts resolved this phase memorized via background Agent(memorize)
 - CHANGELOG.md updated; TODO.md cleared/deleted
 
+## FIX ON SIGHT — HARD RULE
+
+Pre-emit run, post-emit run, or legitimacy gate surfaces ANY issue (failing assertion, stderr, type/lint error, unexpected variance, broken import, runtime throw) → fix at root cause this turn, re-run pre-emit AND post-emit, advance only when all gates pass simultaneously. Never write-and-promise-fix-later, never `try/catch`-to-hide, never `.skip`, never silence with redirection. Known variance → fix and re-verify (self-loop). Unknown variance → regress to `planning`.
+
 ## CODE EXECUTION
 
 `exec:<lang>` only. File writes via exec:nodejs + require('fs'). Never Bash(node/npm/npx/bun).

package/skills/gm-execute/SKILL.md

@@ -118,6 +118,10 @@ Triggers: exec output answers prior unknown | CI log reveals root cause | code r
 
 N facts → N parallel Agent calls in ONE message. End-of-turn self-check mandatory.
 
+## FIX ON SIGHT — HARD RULE
+
+Issue surfaced mid-execution (failing test, exec stderr, broken import, runtime exception, lint/type error, deprecation warning, unexpected output) is fixed THIS turn, at root cause, in-band. Never `// TODO`, never `try/catch`-to-swallow, never `2>/dev/null`, never `.skip`, never "out of scope" inside the same file. Re-witness after fix. New unknown surfaced by the fix → regress to `planning`. Genuine out-of-scope → write a `.gm/prd.yml` item before continuing.
+
 ## CONSTRAINTS
 
 **Never**: Bash(node/npm/npx/bun) | fake data | mocks | scattered tests | fallbacks | Grep/Glob/Find/Explore | sequential independent items | respond mid-phase | edit before witnessing | duplicate code | if/else where dispatch suffices | one-liners that obscure | reinvent native/library

package/skills/planning/SKILL.md

@@ -57,6 +57,12 @@ Forbidden: "honest stop", "stopping for a hard call", "I cannot do this from ins
 
 Required: identify the witnessable bounded subset, PRD-write it, execute it. Residual scope = follow-up item, never refusal.
 
+## FIX ON SIGHT — HARD RULE
+
+Every issue surfaced during planning, execution, or verification — failing test, exec stderr, CI red, lint/type warning, broken import, runtime exception, deprecation, unexpected output — is fixed in-band the same session. Never defer with `// TODO`, never silence with `try/catch`-to-ignore or `2>/dev/null`, never `.skip` a test, never ship while CI is red, never narrate "we'll address that next time."
+
+Surface → diagnose root cause → fix → re-witness → continue. New unknown discovered while fixing → regress here (planning). Genuinely out-of-scope → add a `.gm/prd.yml` item BEFORE moving on, never just mention it. Ignoring a known-bad signal = forced-closure failure.
+
 ## SKIP PLANNING (DEFAULT for small work)
 
 Skip if ANY: single-file single-concern edit | trivially bounded <5min | surgical user instructions | bug fix with identified root cause | zero unknowns. Heavy ceremony only for multi-file architectural work.

package/skills/update-docs/SKILL.md

@@ -52,6 +52,10 @@ git commit -m "docs: update documentation to reflect session changes"
 git push -u origin HEAD
 ```
 
+## FIX ON SIGHT — HARD RULE
+
+Doc-write surfaces a stale claim, broken link, missing file referenced, or contradiction with disk → fix at root cause this turn (update doc to match disk, or fix code if disc is wrong). Never leave a known-false claim in docs. Push surfaces a CI failure → fix and re-push, do not declare complete.
+
 ## Fidelity Rules
 
 Every claim verifiable against disk: phase names match frontmatter, platform names match `platforms/`, file paths exist, constraint counts accurate. Unverifiable section → remove, don't speculate.