@kody-ade/kody-engine 0.3.2 → 0.3.4

package/dist/bin/kody.js

@@ -3,7 +3,7 @@
 // package.json
 var package_default = {
   name: "@kody-ade/kody-engine",
-  version: "0.3.2",
+  version: "0.3.4",
   description: "kody \u2014 autonomous development engine. Single-session Claude Code agent behind a generic executor + declarative executable profiles.",
   license: "MIT",
   type: "module",
@@ -4182,11 +4182,14 @@ function updateVersionInFile(file, newVersion, cwd) {
   fs18.writeFileSync(abs, updated);
   return true;
 }
+var FIRST_RELEASE_COMMIT_CAP = 100;
 function generateChangelog(cwd, newVersion, lastTag) {
-  const range = lastTag ? `${lastTag}..HEAD` : "HEAD";
+  const logArgs = ["log", "--pretty=format:%s||%h", "--no-merges"];
+  if (lastTag) logArgs.splice(1, 0, `${lastTag}..HEAD`);
+  else logArgs.splice(1, 0, `-n${FIRST_RELEASE_COMMIT_CAP}`, "HEAD");
   let log = "";
   try {
-    log = execFileSync15("git", ["log", range, "--pretty=format:%s||%h", "--no-merges"], {
+    log = execFileSync15("git", logArgs, {
       cwd,
       encoding: "utf-8",
       stdio: ["ignore", "pipe", "pipe"]
@@ -4343,9 +4346,13 @@ async function runPrepare(args) {
   }
   const base = ctx.config.git.defaultBranch;
   const title = `chore: release ${tag}`;
+  const bodyMax = 6e4;
+  const rawEntry = entry.length > bodyMax ? `${entry.slice(0, bodyMax)}
+
+_\u2026 truncated; see CHANGELOG.md_` : entry;
   const body = `Automated release PR opened by kody.
 
-${entry}
+${rawEntry}
 
 Merge this and then run \`kody release --mode finalize\`.`;
   let prUrl = "";

package/dist/executables/fix/profile.json

@@ -30,7 +30,8 @@
       "Edit",
       "Bash",
       "Grep",
-      "Glob"
+      "Glob",
+      "mcp__playwright"
     ],
     "hooks": [],
     "skills": [],

package/dist/executables/fix/prompt.md

@@ -19,7 +19,7 @@ You are Kody, an autonomous engineer. Apply the feedback below to the existing P
 # Required steps
 1. **Extract** every actionable item from the feedback. A structured review uses headings like `### Concerns`, `### Suggestions`, and `### Bugs`; each bullet under those headings is a distinct item. `### Strengths`, `### Summary`, and `### Bottom line` are NOT items — skip them. If the feedback has no headings (plain inline feedback), treat the whole feedback as one item.
 2. **Number each item** internally (Item 1, Item 2, …). You will account for every one of them in your final message below.
-3. **Research** — read only what's needed to act on the items. Make the minimum edits required to implement each one.
+3. **Research** — read only what's needed to act on the items. Make the minimum edits required to implement each one. If the feedback or PR body links to external URLs (reproduction sites, bug recordings, spec pages), use the **Playwright MCP** tools (`mcp__playwright__browser_navigate`, `mcp__playwright__browser_snapshot`) to load them — do not rely on your interpretation of the URL alone.
 4. **Verify** — run each quality command with Bash. Fix the root cause of any failure you introduced by this round of edits.
 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/plan/profile.json

@@ -20,7 +20,8 @@
       "Read",
       "Grep",
       "Glob",
-      "Bash"
+      "Bash",
+      "mcp__playwright"
     ],
     "hooks": [],
     "skills": [],
@@ -40,10 +41,10 @@
       "name": "playwright",
       "install": {
         "required": false,
-        "checkCommand": "npx --no-install playwright --version",
+        "checkCommand": "ls \"$HOME/.cache/ms-playwright\" 2>/dev/null | grep -q '^chromium'",
         "installCommand": "npx --yes playwright install --with-deps chromium"
       },
-      "verify": "npx --no-install playwright --version",
+      "verify": "ls \"$HOME/.cache/ms-playwright\" 2>/dev/null | grep -q '^chromium'",
       "usage": ""
     }
   ],

package/dist/executables/plan/prompt.md

@@ -43,6 +43,10 @@ plan under the Required output structure below.
 
 ---
 
+# External references (MUST be fetched before planning)
+
+If the issue body or recent comments contain URLs (http/https), you MUST use the **Playwright MCP** tools (`mcp__playwright__browser_navigate`, `mcp__playwright__browser_snapshot`, optionally `mcp__playwright__browser_take_screenshot`) to load each one and read its content **before** you start planning. Referenced pages — especially demos, specs, and design mocks — are part of the specification. Features visible in a linked demo are in scope unless the issue explicitly excludes them. If a URL cannot be loaded, record that as an Ambiguity rather than silently dropping it.
+
 # Research floor (MUST be done before writing the plan)
 
 Before producing the final plan, you MUST have read:

package/dist/executables/research/profile.json

@@ -20,7 +20,8 @@
       "Read",
       "Grep",
       "Glob",
-      "Bash"
+      "Bash",
+      "mcp__playwright"
     ],
     "hooks": [],
     "skills": [],
@@ -40,10 +41,10 @@
       "name": "playwright",
       "install": {
         "required": false,
-        "checkCommand": "npx --no-install playwright --version",
+        "checkCommand": "ls \"$HOME/.cache/ms-playwright\" 2>/dev/null | grep -q '^chromium'",
         "installCommand": "npx --yes playwright install --with-deps chromium"
       },
-      "verify": "npx --no-install playwright --version",
+      "verify": "ls \"$HOME/.cache/ms-playwright\" 2>/dev/null | grep -q '^chromium'",
       "usage": ""
     }
   ],

package/dist/executables/research/prompt.md

@@ -2,6 +2,16 @@ You are a senior engineer **researching** a GitHub issue. Your job is to fill in
 
 Use Read / Grep / Glob / Bash (read-only) to study the codebase as much as needed. Then emit a final message with the research doc wrapped in the required markers (see "Required output").
 
+## External references — MANDATORY first step
+
+Before you study the repo, scan the issue body and recent comments for **every URL** (http/https). For each one:
+
+- Use the **Playwright MCP** tools available to you (`mcp__playwright__browser_navigate`, `mcp__playwright__browser_snapshot`, optionally `mcp__playwright__browser_take_screenshot`) to actually load the page and read its content. This is not optional — links in the issue are part of the specification.
+- If a URL cannot be loaded (auth-gated, 404, timeout, browser crash), say so explicitly in the "External references" section — do NOT paraphrase or invent content you did not fetch.
+- Never treat a URL as decorative context. Every link must appear in your "External references" section with a real 2–4 sentence summary of what you saw, or an explicit note that you couldn't fetch it.
+
+If the issue contains zero URLs, write "## External references\n\nNone." and move on — do not fabricate links.
+
 ---
 
 # Repo
@@ -32,6 +42,9 @@ PR_SUMMARY:
 ## Understood request
 One paragraph restating what the issue is asking for, in your own words.
 
+## External references
+Per the MANDATORY step above — one bullet per URL found in the issue body/comments. Each bullet: the URL, and a 2–4 sentence summary of what the page actually contains (fetched via Playwright MCP), or an explicit note that it could not be loaded (with the reason). If the issue has no URLs, write `None.` here.
+
 ## Repo context
 **Issue-specific only.** Surface whatever you actually discover during your
 read-only exploration — files, modules, or existing patterns the implementer

package/dist/executables/review/profile.json

@@ -21,7 +21,8 @@
       "Read",
       "Grep",
       "Glob",
-      "Bash"
+      "Bash",
+      "mcp__playwright"
     ],
     "hooks": [],
     "skills": [],
@@ -41,10 +42,10 @@
       "name": "playwright",
       "install": {
         "required": false,
-        "checkCommand": "npx --no-install playwright --version",
+        "checkCommand": "ls \"$HOME/.cache/ms-playwright\" 2>/dev/null | grep -q '^chromium'",
         "installCommand": "npx --yes playwright install --with-deps chromium"
       },
-      "verify": "npx --no-install playwright --version",
+      "verify": "ls \"$HOME/.cache/ms-playwright\" 2>/dev/null | grep -q '^chromium'",
       "usage": ""
     }
   ],

package/dist/executables/review/prompt.md

@@ -1,5 +1,7 @@
 You are Kody, a senior code reviewer. Review PR #{{pr.number}} carefully and post ONE structured review comment. Do NOT edit any files. Do NOT run any `git` or `gh` commands. Use Read / Grep / Glob / Bash only to inspect the diff and surrounding code.
 
+If the PR body or linked issue references external URLs (reference implementations, demos, design mocks, spec pages), load each one with the **Playwright MCP** tools (`mcp__playwright__browser_navigate`, `mcp__playwright__browser_snapshot`) before forming your verdict. Concerns about "does the implementation match the reference?" must cite the actual fetched content, not an assumption about what the URL contains.
+
 # PR #{{pr.number}}: {{pr.title}}
 
 Base: {{pr.baseRefName}} ← Head: {{pr.headRefName}}

package/dist/executables/ui-review/profile.json

@@ -31,7 +31,8 @@
       "Glob",
       "Bash",
       "Write",
-      "Edit"
+      "Edit",
+      "mcp__playwright"
     ],
     "hooks": [],
     "skills": [],
@@ -51,10 +52,10 @@
       "name": "playwright",
       "install": {
         "required": false,
-        "checkCommand": "npx --no-install playwright --version",
+        "checkCommand": "ls \"$HOME/.cache/ms-playwright\" 2>/dev/null | grep -q '^chromium'",
         "installCommand": "npx --yes playwright install --with-deps chromium"
       },
-      "verify": "npx --no-install playwright --version",
+      "verify": "ls \"$HOME/.cache/ms-playwright\" 2>/dev/null | grep -q '^chromium'",
       "usage": "Use `npx playwright test <file>` to run a Playwright spec. Write ad-hoc specs under `.kody/ui-review/*.spec.ts`. If `npx playwright test` errors with `Cannot find package '@playwright/test'`, install it once with `npm install -D @playwright/test` (or the repo's package-manager equivalent) before retrying — the `playwright` browser binaries are already set up by preflight, but the per-repo test framework may not be. Prefer `page.goto(process.env.UI_REVIEW_BASE_URL)` — the base URL is injected as `UI_REVIEW_BASE_URL` at run time. Capture screenshots with `await page.screenshot({ path: '.kody/ui-review/<name>.png' })` and reference those paths in your final review.",
       "allowedUses": [
         "test",

package/dist/executables/ui-review/prompt.md

@@ -2,6 +2,8 @@ You are Kody, a senior UI/UX reviewer. Review PR #{{pr.number}} by reading the d
 
 You MAY write throwaway Playwright specs and screenshots under `.kody/ui-review/` — that directory is ignored by the repo.
 
+You have two browsing options: the `playwright-cli` skill (Bash-based, good for running written specs) AND the **Playwright MCP** tools (`mcp__playwright__browser_navigate`, `mcp__playwright__browser_snapshot`, `mcp__playwright__browser_take_screenshot`) for ad-hoc exploration. For visiting reference URLs cited in the PR body or linked issue (design mocks, demos, spec pages), prefer the MCP tools — they return structured accessibility snapshots without requiring a written spec file.
+
 # PR #{{pr.number}}: {{pr.title}}
 
 Base: {{pr.baseRefName}} ← Head: {{pr.headRefName}}

package/package.json

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