@kody-ade/kody-engine 0.4.58 → 0.4.60

package/dist/executables/fix/profile.json

@@ -26,6 +26,8 @@
     "maxTurnTimeoutSec": 1200,
     "systemPromptAppend": null,
     "cacheable": true,
+    "enableVerifyTool": true,
+    "verifyAttempts": 4,
     "tools": [
       "Read",
       "Write",
@@ -33,7 +35,8 @@
       "Bash",
       "Grep",
       "Glob",
-      "mcp__playwright"
+      "mcp__playwright",
+      "mcp__kody-verify"
     ],
     "hooks": ["block-git"],
     "skills": [],

package/dist/executables/fix/prompt.md

@@ -32,7 +32,7 @@ If a prior-art block is present above, scan it before editing — those are earl
    - Read the **full** contents of every file you intend to change.
    - Read the test file for each of those files, if one exists.
    - Skipping the floor on the assumption "feedback says exactly what to change" is a hard failure when the change touches code with non-obvious invariants.
-4. **Verify** — run each quality command with Bash. Fix the root cause of any failure you introduced by this round of edits.
+4. **Verify** — before declaring DONE, call the `verify` tool (mcp__kody-verify__verify). It runs the project's typecheck/lint/test gates and returns `{ ok, failures, attemptsRemaining }`. If `ok: true`, proceed to DONE. If `ok: false`, read the truncated `failures` list, fix what you introduced this round (not pre-existing breakages unrelated to the feedback), and call `verify` again. Bounded by 4 attempts; after that the tool returns `locked: true` and you must wrap up. The postflight verifier still runs after this session as the final ratifier.
 5. Your FINAL message MUST use this exact format (or a single `FAILED: <reason>` line on failure). The `FEEDBACK_ACTIONS:` block is REQUIRED — omitting it or leaving it empty makes your DONE invalid.
 
    ```

package/dist/executables/fix-ci/profile.json

@@ -25,13 +25,16 @@
     "maxTurnTimeoutSec": 1200,
     "systemPromptAppend": null,
     "cacheable": true,
+    "enableVerifyTool": true,
+    "verifyAttempts": 4,
     "tools": [
       "Read",
       "Write",
       "Edit",
       "Bash",
       "Grep",
-      "Glob"
+      "Glob",
+      "mcp__kody-verify"
     ],
     "hooks": ["block-git"],
     "skills": [],

package/dist/executables/fix-ci/prompt.md

@@ -36,7 +36,7 @@ You are Kody, an autonomous engineer. A CI workflow on PR #{{pr.number}} (`{{bra
 
 2. **Make the minimum edits to fix the root cause.** Do not bundle unrelated cleanups into a CI fix.
 
-3. **Re-run the relevant quality command locally with Bash and confirm exit 0.**
+3. **Confirm green via the `verify` tool** — call `mcp__kody-verify__verify` to run the project's typecheck/lint/test gates. If `ok: false`, read the truncated `failures`, fix the root cause, and call `verify` again. Bounded by 4 attempts; after that the tool returns `locked: true` and you must wrap up with FAILED. The postflight verifier still runs after this session as the final ratifier.
 
 4. **Final message format** (or `FAILED: <reason>` on failure):
 

package/dist/executables/run/profile.json

@@ -25,13 +25,16 @@
     "maxTurnTimeoutSec": 1200,
     "systemPromptAppend": null,
     "cacheable": true,
+    "enableVerifyTool": true,
+    "verifyAttempts": 4,
     "tools": [
       "Read",
       "Write",
       "Edit",
       "Bash",
       "Grep",
-      "Glob"
+      "Glob",
+      "mcp__kody-verify"
     ],
     "hooks": ["block-git"],
     "skills": [],

package/dist/executables/run/prompt.md

@@ -40,7 +40,7 @@ If a prior-art block is present above, READ THE DIFFS — those are failed or su
 2. **Plan** — before any Edit/Write, output a short plan (5–10 lines): what files you'll change, the approach, what could go wrong. No fluff.
 3. **Build** — Edit/Write to implement the change. Stay within the plan; if you discover the plan was wrong, briefly say so and adjust.
 4. **Test** — for every new module you added and every behavior you changed, write or update tests. If the plan above contains a "Test plan" section, treat it as authoritative: every item there must produce a corresponding test. Before writing a test, open the newest existing file in the same test directory (`tests/int/`, `tests/unit/`, `tests/e2e/`, or sibling `*.test.ts`) and copy its imports, setup hooks, and auth pattern **verbatim**. Do NOT introduce a new test infrastructure (own testcontainers, `fetch` against relative URLs, alternate auth headers) when a working pattern already exists in that directory — divergence from the established pattern is a hard failure even if the test passes locally. Cover at least one happy path and one failure path per change. Skipping tests is a hard failure. A change may only be declared untestable if you can name the specific blocker (e.g., "no fake exists for the X SDK and stubbing it would mock the entire call surface"); vague "this is just config" claims are rejected. Untestable changes go in `PLAN_DEVIATIONS:` with the named blocker.
-5. **Verify** — run each quality command with Bash. On failure, fix the root cause and re-run. When reporting that a command passed, you MUST have just run it and seen exit code 0 in this session — do not paraphrase prior output.
+5. **Verify** — before declaring DONE, call the `verify` tool (mcp__kody-verify__verify). It runs typecheck/lint/tests with the project's configured commands and returns `{ ok, failures, attemptsRemaining }`. If `ok: true`, you may proceed to DONE. If `ok: false`, read the truncated `failures` list, fix the root cause, commit-equivalent edits, and call `verify` again. You have up to 4 total attempts; the tool will return `locked: true` after that and you must wrap up with FAILED. The postflight verifier runs again after this session ends and is the final ratifier — but it's also the gate that downgrades a self-reported DONE to FAILED if you skipped this step, so calling the tool is strictly cheaper than not.
 6. Your FINAL message must use this exact format (or a single `FAILED: <reason>` line on failure). The `PLAN_DEVIATIONS:` block is REQUIRED whenever a plan was provided.
 
    ```

package/dist/executables/types.ts

@@ -74,6 +74,16 @@ export interface Profile {
    * Defines the in-process step sequence and routing map. See ContainerChild.
    */
   children?: ContainerChild[]
+  /**
+   * Whether the container should `git reset --hard HEAD` between
+   * children to discard tracked-file modifications a prior child left
+   * behind. Default `true` (preserves the legacy bug-safe behaviour
+   * — see executor.ts:runContainerLoop notes). Set `false` for
+   * containers whose children are expected to share intermediate
+   * state (e.g. bug's `reproduce` writing a failing test that `run`
+   * then makes pass). Only honoured when `role === "container"`.
+   */
+  resetBetweenChildren?: boolean
   /** Absolute directory the profile was loaded from. Used to resolve prompt.md. */
   dir: string
 }
@@ -177,6 +187,21 @@ export interface ClaudeCodeSpec {
    * not support `excludeDynamicSections` (forward-compatible).
    */
   cacheable?: boolean
+  /**
+   * Phase 3 opt-in: expose an in-process `verify` MCP tool to the agent
+   * so it can iterate on typecheck/lint/test failures inside one SDK
+   * session instead of needing a `fix-ci` round trip. The tool is
+   * bounded by `verifyAttempts` (default 4). The postflight `verify`
+   * script still runs after the agent finishes as the final ratifier.
+   * Default false.
+   */
+  enableVerifyTool?: boolean
+  /**
+   * Hard cap on verify-tool invocations per agent session when
+   * `enableVerifyTool` is true. Default 4 (≈3 fix iterations after the
+   * first attempt). Set to 0 or omit to use the default.
+   */
+  verifyAttempts?: number | null
   /** SDK built-in tools this executable is allowed to use (capability pack). */
   tools: string[]
   /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kody-ade/kody-engine",
-  "version": "0.4.58",
+  "version": "0.4.60",
   "description": "kody — autonomous development engine. Single-session Claude Code agent behind a generic executor + declarative executable profiles.",
   "license": "MIT",
   "type": "module",
@@ -12,9 +12,22 @@
     "templates",
     "kody.config.schema.json"
   ],
+  "scripts": {
+    "kody": "tsx bin/kody.ts",
+    "build": "tsup && node scripts/copy-assets.cjs",
+    "test": "vitest run tests/unit tests/int --no-coverage",
+    "test:e2e": "vitest run tests/e2e --no-coverage",
+    "test:all": "vitest run tests --no-coverage",
+    "typecheck": "tsc --noEmit",
+    "lint": "biome check",
+    "lint:fix": "biome check --write",
+    "format": "biome format --write",
+    "prepublishOnly": "pnpm build"
+  },
   "dependencies": {
     "@actions/cache": "^6.0.0",
-    "@anthropic-ai/claude-agent-sdk": "0.2.119"
+    "@anthropic-ai/claude-agent-sdk": "0.2.119",
+    "zod": "^4.0.0"
   },
   "devDependencies": {
     "@biomejs/biome": "^2.4.12",
@@ -32,16 +45,5 @@
     "url": "git+https://github.com/aharonyaircohen/kody-engine.git"
   },
   "homepage": "https://github.com/aharonyaircohen/kody-engine",
-  "bugs": "https://github.com/aharonyaircohen/kody-engine/issues",
-  "scripts": {
-    "kody": "tsx bin/kody.ts",
-    "build": "tsup && node scripts/copy-assets.cjs",
-    "test": "vitest run tests/unit tests/int --no-coverage",
-    "test:e2e": "vitest run tests/e2e --no-coverage",
-    "test:all": "vitest run tests --no-coverage",
-    "typecheck": "tsc --noEmit",
-    "lint": "biome check",
-    "lint:fix": "biome check --write",
-    "format": "biome format --write"
-  }
-}
+  "bugs": "https://github.com/aharonyaircohen/kody-engine/issues"
+}