gm-cc 2.0.188 → 2.0.190

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.188",
+  "version": "2.0.190",
   "metadata": {
     "description": "State machine agent with hooks, skills, and automated git enforcement"
   },

package/agents/gm.md

@@ -9,6 +9,8 @@ enforce: critical
 
 **Invoke the `gm` skill immediately.** Use the Skill tool with `skill: "gm"`.
 
+**CRITICAL: Skills are invoked via the Skill tool ONLY. Do NOT use the Agent tool to load skills. Skills are not agents. Use: `Skill tool` with `skill: "gm"` (or `"planning"`, `"gm-execute"`, `"gm-emit"`, `"gm-complete"`). Using the Agent tool for skills is a violation.**
+
 All work coordination, planning, execution, and verification happens through the skill tree:
 - `gm` skill → `planning` skill → `gm-execute` skill → `gm-emit` skill → `gm-complete` skill
 

package/hooks/prompt-submit-hook.js

@@ -74,7 +74,7 @@ try {
   ensureGitignore();
 
   const parts = [];
-  parts.push('Invoke the `gm` skill to begin. DO NOT use EnterPlanMode. DO NOT use gm subagent directly — use the `gm` skill via the Skill tool.');
+  parts.push('Use the Skill tool with skill: "gm" to begin — do NOT use the Agent tool to load skills. Skills are invoked via the Skill tool only, never as agents. DO NOT use EnterPlanMode.');
 
   const search = runCodeSearch(prompt);
   if (search) parts.push(search);

package/hooks/session-start-hook.js

@@ -29,7 +29,7 @@ ensureGitignore();
 try {
   let outputs = [];
 
-  outputs.push('Invoke the `gm` skill to begin. All code execution uses exec:<lang> via the Bash tool — never direct Bash(node ...) or Bash(npm ...) or Bash(npx ...).');
+  outputs.push('Use the Skill tool with skill: "gm" to begin — do NOT use the Agent tool to load skills. Skills are invoked via the Skill tool only, never as agents. All code execution uses exec:<lang> via the Bash tool — never direct Bash(node ...) or Bash(npm ...) or Bash(npx ...).');
 
   if (projectDir && fs.existsSync(projectDir)) {
     try {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gm-cc",
-  "version": "2.0.188",
+  "version": "2.0.190",
   "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.188",
+  "version": "2.0.190",
   "description": "State machine agent with hooks, skills, and automated git enforcement",
   "author": {
     "name": "AnEntrypoint",

package/skills/gm/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: gm
-description: Immutable programming state machine. Root orchestrator. Invoke for all work coordination.
-agent: true
+description: Immutable programming state machine. Root orchestrator. Invoke for all work coordination via the Skill tool.
 enforce: critical
 ---
 
@@ -68,13 +67,13 @@ exec:close
 <task_id>
 ```
 
-**Runner management** (PM2-backed, visible in `pm2 list` and `pm2 monit`):
+**Runner management** (the runner itself is a PM2 process named `gm-exec-runner`):
 ```
 exec:runner
 start|stop|status
 ```
 
-All gm-exec activity runs under PM2. Use `exec:bash\npm2 list` to see all running processes. Users can run `pm2 monit` directly in their terminal to watch live activity.
+`exec:runner start` launches a single PM2 process (`gm-exec-runner`) that hosts all execution as worker threads inside it. Individual `exec:<lang>` calls are worker threads — they do NOT appear as separate entries in `pm2 list`. Only the runner process is visible. Use `exec:runner status` to check it.
 
 ## CODEBASE EXPLORATION