gm-cc 2.0.441 → 2.0.442

package/.claude-plugin/marketplace.json

@@ -4,7 +4,7 @@
     "name": "AnEntrypoint"
   },
   "description": "State machine agent with hooks, skills, and automated git enforcement",
-  "version": "2.0.441",
+  "version": "2.0.442",
   "metadata": {
     "description": "State machine agent with hooks, skills, and automated git enforcement"
   },

package/package.json

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

package/plugin.json

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

package/skills/gm-complete/SKILL.md

@@ -139,8 +139,9 @@ Before declaring complete, sweep the entire codebase for violations:
 8. **Fallback/demo modes** → remove, fail loud instead
 9. **TODO.md** → must be empty/deleted before completion
 10. **CHANGELOG.md** → must have entries for this session's changes
-11. **memorize** → launch memorize sub-agent in background with session learnings before invoking update-docs: `Agent(subagent_type='memorize', model='haiku', run_in_background=true, prompt='## CONTEXT TO MEMORIZE\n<session learnings>')`
-12. **Deploy/publish** → if deployable, deploy. If npm package, publish.
+11. **Observability gaps** → every server subsystem added this session exposes a `/debug/<subsystem>` endpoint; every client module added this session registers into `window.__debug` by key. Ad-hoc console.log is not observability — permanent queryable structures are. Any gap found → fix before advancing.
+12. **memorize** → launch memorize sub-agent in background with session learnings before invoking update-docs: `Agent(subagent_type='memorize', model='haiku', run_in_background=true, prompt='## CONTEXT TO MEMORIZE\n<session learnings>')`
+13. **Deploy/publish** → if deployable, deploy. If npm package, publish.
 
 Any violation found = fix immediately before advancing.
 

package/skills/gm-emit/SKILL.md

@@ -85,7 +85,7 @@ The post-emit verification is a differential diagnosis against the pre-emit base
 - No hardcoded values — dynamic/modular code using ground truth only
 - No adjectives/descriptive language in variable/function names
 - No unnecessary files — clean anything not required for the program to function
-- Client-side code exposes debug globals (window.__debug or similar)
+- Observability: every new server subsystem exposes a named inspection endpoint; every new client module registers into `window.__debug` by key and deregisters on unmount. Ad-hoc `console.log` is not observability — permanent queryable structure is. Any new code path not reachable via `window.__debug` or a `/debug/<subsystem>` endpoint → do NOT advance, add observability before writing feature code.
 - Structural quality: if/else chains where a dispatch table or pipeline suffices → regress to `gm-execute` for restructuring. One-liners that compress logic at the cost of readability → expand. Any logic that reinvents a native API or library → replace with the native/library call. Structure must make wrong states unrepresentable — if it doesn't, it's not done.
 - memorize sub-agent launched in background before advancing: `Agent(subagent_type='memorize', model='haiku', run_in_background=true, prompt='## CONTEXT TO MEMORIZE\n<what was learned>')`
 - CHANGELOG.md updated with changes

package/skills/planning/SKILL.md

@@ -47,11 +47,13 @@ Planning = exhaustive fault-surface enumeration. For every aspect of the task:
 
 ## OBSERVABILITY ENUMERATION — MANDATORY EVERY PASS
 
-During every planning pass, enumerate every possible aspect of the app's runtime observability that can be improved:
+During every planning pass, enumerate every possible aspect of the app's runtime observability that can be improved. The goal is permanent structures — not ad-hoc logs — that make any future debugging session start from a complete, live picture of system state.
 
-**Server-side**: Does every internal — state machine, queue, cache, connection pool, active task map, process registry, RPC handler, hook dispatcher — expose a real-time inspection API? Can any internal state be read, queried, or modified without restarting? Are profiling hooks present on every hot path? Are logs structured and filterable by subsystem at any time?
+**Server-side permanent structures**: Every internal subsystem — state machine, queue, cache, connection pool, active task map, process registry, RPC handler, hook dispatcher — must expose a named, queryable inspection endpoint (e.g. `/debug/<subsystem>`). State must be readable, filterable, and ideally modifiable without restart. Profiling hooks on every hot path. Structured logs with subsystem tag, severity, and timestamp — filterable at runtime by subsystem, not just log level. Any internal state that requires a restart to inspect is an observability gap.
 
-**Client-side**: Does `window.__debug` expose every possible piece of state — all component state, all active requests, all log entries, all event queues, all WebSocket connections, all rendered props? Is every execution path traceable via globals?
+**Client-side permanent structures**: `window.__debug` must be a live, structured registry — not a dump. Every component's state, every active request, every event queue, every WebSocket connection, every rendered prop, every error boundary — all addressable by key, all queryable without refreshing. New modules register themselves into `window.__debug` on mount and deregister on unmount. Any execution path not traceable via `window.__debug` is an observability gap.
+
+**Permanent vs ad-hoc**: `console.log` = ad-hoc = not observability. A structured logger with subsystem routing = permanent. `window.__debug.myModule.state` = permanent. `window.__debug = { ...window.__debug, tmp: x }` = ad-hoc = not acceptable. Permanent structures survive deploys and accumulate diagnostic value across sessions.
 
 **Mandate**: on discovery of any observability gap → immediately add a .prd item. Observability improvements are highest-priority — never deferred. The agent must be able to see specifically anything it wants and nothing else — no guessing, no blind spots.