@kody-ade/kody-engine 0.4.563 → 0.4.565

package/dist/implementations/run/prompt.md

@@ -52,6 +52,7 @@ If a prior-art block is present above, READ THE DIFFS — those are failed or su
    - If your change requires writing or modifying a test, also check for repo-level testing guidance: `tests/README.md`, `TESTING.md`, or a "Testing"/"Tests" section in `AGENTS.md`/`CLAUDE.md`. If one exists, treat its patterns (auth setup, fixture creation, what NOT to do) as authoritative — they override anything you might infer from grepping individual files.
    - **Removal/rename refactors** (deleting a call like `console.error`, renaming a function, dropping a method, replacing one API with another): before editing, grep the test directories for assertions tied to the OLD symbol — spies (`vi.spyOn(console`, `jest.spyOn(console`, `consoleErrorSpy`, `mockFn.mock.calls`), the literal function name, and any string the call produced. Enumerate every hit in your plan (step 2) and update those tests in step 4 in the same session. Skipping this grep is a hard failure even if your local test runs pass — the wrapper runs the full suite and you cannot fix breakages after DONE.
    - If a file you need to read does not exist, say so explicitly in your plan (step 2). Do not guess at its contents.
+   - A failing path may be generated, aliased, or stale. If it does not exist, locate the real tracked source with Glob/Grep or `git ls-files` before editing. Never recreate an existing module under a guessed directory. New files are allowed only when the task actually requires a new module, and their parent directory must already exist or be created explicitly.
 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.

package/package.json

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