@kody-ade/kody-engine 0.2.13 → 0.2.15

package/dist/bin/kody2.js

@@ -3,7 +3,7 @@
 // package.json
 var package_default = {
   name: "@kody-ade/kody-engine",
-  version: "0.2.13",
+  version: "0.2.15",
   description: "kody2 \u2014 autonomous development engine. Single-session Claude Code agent behind a generic executor + declarative executable profiles.",
   license: "MIT",
   type: "module",

package/dist/executables/plan-verify/prompt.md

@@ -1,17 +1,40 @@
-You are Kody2's plugin-wiring live verification agent. Your ONLY job is to prove that each of the four extension mechanisms (plugins, skills, commands, hooks) is successfully loaded into your session.
+You are Kody2's plugin-wiring live verification agent. Your ONLY job is to prove that each of the four extension mechanisms (plugins, skills, commands, hooks) is successfully loaded into your session. Do NOT address the issue's actual work.
+
+Issue #{{issue.number}}: {{issue.title}}
 
 ---
 
-# Task
-Issue #{{issue.number}}: {{issue.title}}
+# What to do, in order
+
+Perform these four checks, then emit the final report.
+
+## Check 1 — Plugin
+
+Look at your available skills. If a skill named `kody-plugin-marker` is loaded, record the literal string `PLUGIN_LOADED_OK`. Otherwise record `MISSING`.
+
+## Check 2 — Skill
+
+Look at your available skills. If a skill named `kody-live-marker` is loaded, record the literal string `SKILL_LOADED_OK`. Otherwise record `MISSING`.
+
+## Check 3 — Command
+
+Look at your available slash commands. If `/kody-live-probe` is listed, record the literal string `COMMAND_LOADED_OK`. Otherwise record `MISSING`.
+
+## Check 4 — Hook
+
+Run these Bash steps, in order:
 
-Do not perform the issue's actual work. Instead, emit the confirmation tokens below.
+1. `rm -f /tmp/kody-hook-signal.txt`
+2. Use the Read tool to read `README.md` (or any file). This should trigger a PreToolUse hook that appends `HOOK_FIRED_OK` to `/tmp/kody-hook-signal.txt`.
+3. `cat /tmp/kody-hook-signal.txt`
+
+If step 3 prints a line containing `HOOK_FIRED_OK`, record `HOOK_FIRED_OK`. Otherwise record `MISSING`.
 
 ---
 
-# Required tokens
+# Output
 
-Your final message MUST use this exact shape:
+Your FINAL message must use this exact structure. Replace each `<...>` placeholder with your recorded value from the check above (either the `_OK` token or `MISSING`) — do NOT include the "<" or ">" characters, and do NOT include the "if-else" explanation text.
 
 ```
 DONE
@@ -19,35 +42,31 @@ COMMIT_MSG: verify: plugin-wiring live check for #{{issue.number}}
 PR_SUMMARY:
 # Plugin-Wiring Verification Report
 
-- **Plugin**: PLUGIN_LOADED_OK if the kody-plugin-marker skill is loaded, else MISSING
-- **Skill**: SKILL_LOADED_OK if the kody-live-marker skill is loaded, else MISSING
-- **Command**: COMMAND_LOADED_OK if the /kody-live-probe command is listed, else MISSING
-- **Hook**: HOOK_FIRED_OK if reading /tmp/kody-hook-signal.txt returns the line HOOK_FIRED_OK, else MISSING
+- Plugin: <check-1-value>
+- Skill: <check-2-value>
+- Command: <check-3-value>
+- Hook: <check-4-value>
 ```
 
-Fill in each line with the **actual** token (PLUGIN_LOADED_OK / SKILL_LOADED_OK / COMMAND_LOADED_OK / HOOK_FIRED_OK) if that feature is working, or the literal word `MISSING` if it isn't.
-
----
-
-# How to check each feature
-
-**Plugin** — A plugin named `kody2-test-plugin` should be loaded. It ships a skill called `kody-plugin-marker`. If the skill is available, consult it (its SKILL.md instructs you to emit `PLUGIN_LOADED_OK`).
-
-**Skill** — A skill called `kody-live-marker` should be available. Its SKILL.md instructs you to emit `SKILL_LOADED_OK`. If you can see that skill in your available skills, emit the token.
+Example of a valid filled-in output (if all four worked):
 
-**Command** — A slash command `/kody-live-probe` should be available. Verify by listing available slash commands (if you cannot see them, say MISSING). If available, emit `COMMAND_LOADED_OK`.
+```
+DONE
+COMMIT_MSG: verify: plugin-wiring live check for #{{issue.number}}
+PR_SUMMARY:
+# Plugin-Wiring Verification Report
 
-**Hook** — There is a `PreToolUse` hook configured for the Read tool. Its side effect: every time you invoke Read, the hook runs a shell command that writes `HOOK_FIRED_OK` to `/tmp/kody-hook-signal.txt`. Steps:
-1. Use `Bash` to run `rm -f /tmp/kody-hook-signal.txt` to clear prior runs.
-2. Use `Read` to read any file in the repository (e.g. `README.md`). This SHOULD trigger the hook.
-3. Use `Bash` to `cat /tmp/kody-hook-signal.txt`. If it prints `HOOK_FIRED_OK`, emit that token. Otherwise emit MISSING.
+- Plugin: PLUGIN_LOADED_OK
+- Skill: SKILL_LOADED_OK
+- Command: COMMAND_LOADED_OK
+- Hook: HOOK_FIRED_OK
+```
 
 ---
 
 # Rules
 
 - Read-only. Do NOT modify any file.
-- Do NOT run git or gh commands.
-- Do NOT perform the issue's actual requested work.
-- If any feature reports MISSING, continue with the others — the whole point is to learn which mechanisms work.
-- Output must match the DONE/COMMIT_MSG/PR_SUMMARY shape exactly so Kody2's state-reducer can parse it.
+- Do NOT run git or gh.
+- Do NOT perform the issue's actual work.
+- Emit the final report even if some checks report `MISSING` — the whole point is to learn which mechanisms work.

package/dist/plugins/hooks/kody-live-trace.json

@@ -3,14 +3,13 @@
   "hooks": {
     "PreToolUse": [
       {
-        "matcher": "tool == \"Read\"",
+        "matcher": "Read",
         "hooks": [
           {
             "type": "command",
             "command": "printf 'HOOK_FIRED_OK\\n' >> /tmp/kody-hook-signal.txt"
           }
-        ],
-        "description": "Kody2 live-test hook — appends HOOK_FIRED_OK to /tmp/kody-hook-signal.txt on every Read tool use, so the agent can verify the hook fired."
+        ]
       }
     ]
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kody-ade/kody-engine",
-  "version": "0.2.13",
+  "version": "0.2.15",
   "description": "kody2 — autonomous development engine. Single-session Claude Code agent behind a generic executor + declarative executable profiles.",
   "license": "MIT",
   "type": "module",