@kody-ade/kody-engine 0.2.63 → 0.3.1

package/dist/executables/bug/profile.json

@@ -33,7 +33,7 @@
         "with": {
           "label": "kody-flow:bug",
           "color": "d73a4a",
-          "description": "kody2 flow: bug / enhancement"
+          "description": "kody flow: bug / enhancement"
         }
       },
       {
@@ -41,7 +41,7 @@
         "with": {
           "label": "kody:orchestrating",
           "color": "1d76db",
-          "description": "kody2: orchestrating a multi-stage flow"
+          "description": "kody: orchestrating a multi-stage flow"
         }
       },
       { "script": "loadIssueContext" },
@@ -58,22 +58,22 @@
         "runWhen": { "data.taskState.core.lastOutcome.type": "RUN_COMPLETED" } },
 
       { "script": "finishFlow",
-        "with": { "reason": "review-passed", "label": "kody:done", "color": "0e8a16", "description": "kody2: PR ready for human review/merge" },
+        "with": { "reason": "review-passed", "label": "kody:done", "color": "0e8a16", "description": "kody: PR ready for human review/merge" },
         "runWhen": { "data.taskState.core.lastOutcome.type": "REVIEW_PASS" } },
 
       { "script": "dispatch", "with": { "next": "fix", "target": "pr" },
         "runWhen": { "data.taskState.core.lastOutcome.type": ["REVIEW_CONCERNS", "REVIEW_FAIL"] } },
 
       { "script": "finishFlow",
-        "with": { "reason": "review-failed", "label": "kody:failed", "color": "e11d21", "description": "kody2: flow failed" },
+        "with": { "reason": "review-failed", "label": "kody:failed", "color": "e11d21", "description": "kody: flow failed" },
         "runWhen": { "data.taskState.core.lastOutcome.type": "REVIEW_FAILED" } },
 
       { "script": "finishFlow",
-        "with": { "reason": "fix-applied", "label": "kody:done", "color": "0e8a16", "description": "kody2: PR ready for human review/merge" },
+        "with": { "reason": "fix-applied", "label": "kody:done", "color": "0e8a16", "description": "kody: PR ready for human review/merge" },
         "runWhen": { "data.taskState.core.lastOutcome.type": "FIX_COMPLETED" } },
 
       { "script": "finishFlow",
-        "with": { "reason": "aborted", "label": "kody:failed", "color": "e11d21", "description": "kody2: flow failed" },
+        "with": { "reason": "aborted", "label": "kody:failed", "color": "e11d21", "description": "kody: flow failed" },
         "runWhen": { "data.taskState.core.lastOutcome.type": ["PLAN_FAILED", "RUN_FAILED", "FIX_FAILED", "AGENT_NOT_RUN"] } },
 
       { "script": "persistFlowState" }

package/dist/executables/chore/profile.json

@@ -33,7 +33,7 @@
         "with": {
           "label": "kody-flow:chore",
           "color": "c5def5",
-          "description": "kody2 flow: chore / docs / dep-bump"
+          "description": "kody flow: chore / docs / dep-bump"
         }
       },
       {
@@ -41,7 +41,7 @@
         "with": {
           "label": "kody:orchestrating",
           "color": "1d76db",
-          "description": "kody2: orchestrating a multi-stage flow"
+          "description": "kody: orchestrating a multi-stage flow"
         }
       },
       { "script": "loadIssueContext" },
@@ -55,22 +55,22 @@
         "runWhen": { "data.taskState.core.lastOutcome.type": "RUN_COMPLETED" } },
 
       { "script": "finishFlow",
-        "with": { "reason": "review-passed", "label": "kody:done", "color": "0e8a16", "description": "kody2: PR ready for human review/merge" },
+        "with": { "reason": "review-passed", "label": "kody:done", "color": "0e8a16", "description": "kody: PR ready for human review/merge" },
         "runWhen": { "data.taskState.core.lastOutcome.type": "REVIEW_PASS" } },
 
       { "script": "dispatch", "with": { "next": "fix", "target": "pr" },
         "runWhen": { "data.taskState.core.lastOutcome.type": ["REVIEW_CONCERNS", "REVIEW_FAIL"] } },
 
       { "script": "finishFlow",
-        "with": { "reason": "review-failed", "label": "kody:failed", "color": "e11d21", "description": "kody2: flow failed" },
+        "with": { "reason": "review-failed", "label": "kody:failed", "color": "e11d21", "description": "kody: flow failed" },
         "runWhen": { "data.taskState.core.lastOutcome.type": "REVIEW_FAILED" } },
 
       { "script": "finishFlow",
-        "with": { "reason": "fix-applied", "label": "kody:done", "color": "0e8a16", "description": "kody2: PR ready for human review/merge" },
+        "with": { "reason": "fix-applied", "label": "kody:done", "color": "0e8a16", "description": "kody: PR ready for human review/merge" },
         "runWhen": { "data.taskState.core.lastOutcome.type": "FIX_COMPLETED" } },
 
       { "script": "finishFlow",
-        "with": { "reason": "aborted", "label": "kody:failed", "color": "e11d21", "description": "kody2: flow failed" },
+        "with": { "reason": "aborted", "label": "kody:failed", "color": "e11d21", "description": "kody: flow failed" },
         "runWhen": { "data.taskState.core.lastOutcome.type": ["RUN_FAILED", "FIX_FAILED", "AGENT_NOT_RUN"] } },
 
       { "script": "persistFlowState" }

package/dist/executables/classify/profile.json

@@ -36,7 +36,7 @@
         "with": {
           "label": "kody:classifying",
           "color": "0e8a16",
-          "description": "kody2: classifying the issue"
+          "description": "kody: classifying the issue"
         }
       },
       { "script": "loadIssueContext" },

package/dist/executables/feature/profile.json

@@ -33,7 +33,7 @@
         "with": {
           "label": "kody-flow:feature",
           "color": "a2eeef",
-          "description": "kody2 flow: feature / refactor"
+          "description": "kody flow: feature / refactor"
         }
       },
       {
@@ -41,7 +41,7 @@
         "with": {
           "label": "kody:orchestrating",
           "color": "1d76db",
-          "description": "kody2: orchestrating a multi-stage flow"
+          "description": "kody: orchestrating a multi-stage flow"
         }
       },
       { "script": "loadIssueContext" },
@@ -61,22 +61,22 @@
         "runWhen": { "data.taskState.core.lastOutcome.type": "RUN_COMPLETED" } },
 
       { "script": "finishFlow",
-        "with": { "reason": "review-passed", "label": "kody:done", "color": "0e8a16", "description": "kody2: PR ready for human review/merge" },
+        "with": { "reason": "review-passed", "label": "kody:done", "color": "0e8a16", "description": "kody: PR ready for human review/merge" },
         "runWhen": { "data.taskState.core.lastOutcome.type": "REVIEW_PASS" } },
 
       { "script": "dispatch", "with": { "next": "fix", "target": "pr" },
         "runWhen": { "data.taskState.core.lastOutcome.type": ["REVIEW_CONCERNS", "REVIEW_FAIL"] } },
 
       { "script": "finishFlow",
-        "with": { "reason": "review-failed", "label": "kody:failed", "color": "e11d21", "description": "kody2: flow failed" },
+        "with": { "reason": "review-failed", "label": "kody:failed", "color": "e11d21", "description": "kody: flow failed" },
         "runWhen": { "data.taskState.core.lastOutcome.type": "REVIEW_FAILED" } },
 
       { "script": "finishFlow",
-        "with": { "reason": "fix-applied", "label": "kody:done", "color": "0e8a16", "description": "kody2: PR ready for human review/merge" },
+        "with": { "reason": "fix-applied", "label": "kody:done", "color": "0e8a16", "description": "kody: PR ready for human review/merge" },
         "runWhen": { "data.taskState.core.lastOutcome.type": "FIX_COMPLETED" } },
 
       { "script": "finishFlow",
-        "with": { "reason": "aborted", "label": "kody:failed", "color": "e11d21", "description": "kody2: flow failed" },
+        "with": { "reason": "aborted", "label": "kody:failed", "color": "e11d21", "description": "kody: flow failed" },
         "runWhen": { "data.taskState.core.lastOutcome.type": ["RESEARCH_FAILED", "PLAN_FAILED", "RUN_FAILED", "FIX_FAILED", "AGENT_NOT_RUN"] } },
 
       { "script": "persistFlowState" }

package/dist/executables/fix/profile.json

@@ -36,9 +36,26 @@
     "commands": [],
     "subagents": [],
     "plugins": [],
-    "mcpServers": []
+    "mcpServers": [
+      {
+        "name": "playwright",
+        "command": "npx",
+        "args": ["-y", "@playwright/mcp@latest"]
+      }
+    ]
   },
-  "cliTools": [],
+  "cliTools": [
+    {
+      "name": "playwright",
+      "install": {
+        "required": false,
+        "checkCommand": "npx --no-install playwright --version",
+        "installCommand": "npx --yes playwright install --with-deps chromium"
+      },
+      "verify": "npx --no-install playwright --version",
+      "usage": ""
+    }
+  ],
   "scripts": {
     "preflight": [
       {
@@ -46,7 +63,7 @@
         "with": {
           "label": "kody:fixing",
           "color": "e99695",
-          "description": "kody2: applying review feedback"
+          "description": "kody: applying review feedback"
         }
       },
       { "script": "fixFlow" },

package/dist/executables/fix/prompt.md

@@ -42,6 +42,6 @@ You are Kody, an autonomous engineer. Apply the feedback below to the existing P
 - **"Already satisfied" (i.e. skipping the edit because the code already does what's asked) is only allowed when you can cite the exact file:line that already implements it.** If in doubt, make the edit — under `fixed`.
 - Do NOT run git/gh commands. The wrapper handles it.
 - Stay on `{{branch}}`.
-- Do not modify files under `.kody/`, `.kody-engine/`, `.kody2/`, `node_modules/`, `dist/`, `build/`, `.env`, `*.log`.
+- Do not modify files under `.kody/`, `.kody-engine/`, `.kody/`, `node_modules/`, `dist/`, `build/`, `.env`, `*.log`.
 - If the feedback is ambiguous or conflicts with the issue, err toward what the feedback says.
 {{systemPromptAppend}}

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

@@ -46,7 +46,7 @@
         "with": {
           "label": "kody:fixing",
           "color": "e99695",
-          "description": "kody2: applying review feedback"
+          "description": "kody: applying review feedback"
         }
       },
       {

package/dist/executables/init/profile.json

@@ -1,7 +1,7 @@
 {
   "name": "init",
   "role": "utility",
-  "describe": "Scaffold a consumer repo with kody.config.json and the @kody2 workflow. No agent.",
+  "describe": "Scaffold a consumer repo with kody.config.json and the @kody workflow. No agent.",
   "inputs": [
     {
       "name": "force",

package/dist/executables/plan/profile.json

@@ -27,9 +27,26 @@
     "commands": [],
     "subagents": [],
     "plugins": [],
-    "mcpServers": []
+    "mcpServers": [
+      {
+        "name": "playwright",
+        "command": "npx",
+        "args": ["-y", "@playwright/mcp@latest"]
+      }
+    ]
   },
-  "cliTools": [],
+  "cliTools": [
+    {
+      "name": "playwright",
+      "install": {
+        "required": false,
+        "checkCommand": "npx --no-install playwright --version",
+        "installCommand": "npx --yes playwright install --with-deps chromium"
+      },
+      "verify": "npx --no-install playwright --version",
+      "usage": ""
+    }
+  ],
   "scripts": {
     "preflight": [
       {
@@ -37,7 +54,7 @@
         "with": {
           "label": "kody:planning",
           "color": "5319e7",
-          "description": "kody2: producing an implementation plan"
+          "description": "kody: producing an implementation plan"
         }
       },
       {
@@ -49,6 +66,9 @@
       {
         "script": "loadConventions"
       },
+      {
+        "script": "loadPriorArt"
+      },
       {
         "script": "composePrompt"
       }

package/dist/executables/plan/prompt.md

@@ -1,6 +1,6 @@
-You are a senior engineer producing an **implementation plan** for the GitHub issue below. You will NOT write code. You will NOT run git or gh commands. You will NOT modify files. Your only outputs are:
+You are a senior engineer producing a **deep, detailed implementation plan** for the GitHub issue below. The plan must be thorough enough that another engineer can implement the feature without re-doing research — file locations, function signatures, algorithms, edge cases, and tests are all specified. You will NOT write code. You will NOT run git or gh commands. You will NOT modify files.
 
-1. Use Read / Grep / Glob / Bash (read-only) to study the codebase as much as needed.
+1. Use Read / Grep / Glob / Bash (read-only) to study the codebase as much as needed. Depth matters more than speed — invest turns in understanding before writing.
 2. Emit a final message with the plan wrapped in the required markers (see "Required output").
 
 ---
@@ -17,6 +17,43 @@ Recent comments (most recent first, truncated):
 
 {{conventionsBlock}}
 
+{{priorArt}}
+
+---
+
+# Delta mode — if a prior plan comment exists
+
+Before writing the plan, scan the "Recent comments" block above for a previous
+comment whose body starts with `## Plan for issue`. If one exists, you are in
+**delta mode**:
+
+1. Treat the prior plan as the baseline. Do NOT regenerate unchanged sections
+   from scratch.
+2. Integrate the signal from comments posted AFTER the prior plan: user
+   answers, correction directives, new clarifying info, closed/merged PRs that
+   appeared since.
+3. In each section, mark changed bullets with `(updated)`, new bullets with
+   `(new)`, and removed items with `(removed — <reason>)`. Preserve unchanged
+   bullets verbatim so reviewers can diff.
+4. If nothing material has changed since the prior plan, output
+   `FAILED: no new information since last plan` instead of a duplicate.
+
+If no prior `## Plan for issue` comment exists, produce a full first-pass
+plan under the Required output structure below.
+
+---
+
+# Research floor (MUST be done before writing the plan)
+
+Before producing the final plan, you MUST have read:
+
+- Every file you intend to change (the full file, not just a grep hit).
+- The tests for each file you intend to change, if tests exist for that module.
+- At least one sibling module that already implements the same pattern you're about to follow (reference implementations).
+- The full prior-art diffs above (if any) — not just titles. Those represent failed solutions; understanding why they failed is part of the plan.
+
+If a file you need to read does not exist, say so explicitly in the plan under "Ambiguities" — do NOT guess at its contents.
+
 ---
 
 # Required output
@@ -27,16 +64,87 @@ Your FINAL message must be exactly this shape (no extra text before or after):
 DONE
 COMMIT_MSG: plan: <very short title>
 PR_SUMMARY:
-<A concrete implementation plan in markdown. Include:
- - Files to change (with paths), and the change in each.
- - New files to create, with their purpose and rough shape.
- - Any ambiguities that need the human to resolve first.
- - Verification checklist (typecheck / tests / lint expectations).
- Keep to ~60 lines or less. No filler. No marketing language.>
+<A deep, detailed implementation plan in markdown with the following sections, in order. Omit a section only if its trigger condition is not met — do not leave placeholders. Depth is expected; brevity for its own sake is not a goal.
+
+## Existing patterns found
+For each major part of the change, name the sibling module in this repo that
+already solves a similar problem and state how this plan reuses it.
+ - Pattern: <what kind of pattern — e.g. "admin field with custom React component", "fetch-then-group client hook", "JSON strings module">
+ - Reference: <exact path in this repo, e.g. `src/ui/admin/LessonBlocksField/index.tsx`>
+ - Reuse: <how this plan follows it — which hooks/APIs/idioms are mirrored, what deviates and why>
+If you searched and found nothing applicable, say so explicitly: "Searched
+for X / Y / Z — no existing pattern; proposing new convention because …".
+Proposing a new pattern when an existing one covers the use case is a
+planning failure — fall back to reuse unless you name a concrete reason.
+
+## Changes (per file)
+For EACH file you will change or create, include:
+ - Path (exact).
+ - Why this file — one sentence tying the change to the issue.
+ - Current state — what's there today (function/class/export names, relevant line ranges). Skip for new files.
+ - Target state — what will be there after the change, at the same level of specificity.
+ - Exact locations of edits (function name, line range if stable, or anchor like "after the `meta` group field, before the closing `fields: []`").
+ - For new files: rough shape including exports, key functions with signatures, and top-level module comment.
+ - Dependencies touched (imports added/removed, new packages) — call out if anything needs installing.
+
+## Algorithms & pseudocode
+REQUIRED for any non-trivial logic (sorting, diffing, state transitions, concurrency, batching, caching, conflict resolution).
+ - Write pseudocode (not production code) showing the actual algorithm — inputs, steps, outputs.
+ - Call out invariants the algorithm preserves.
+ - Call out complexity (N swaps vs N-squared recalc vs single-batch write).
+ - If there's a choice between two algorithms, explain why you picked this one.
+
+## How clarifying answers shape the plan
+REQUIRED if research asked clarifying questions and the issue comments contain user answers.
+ - For each answered question: name the concrete design choice the answer forces — not a restatement of the answer.
+ - "Answer: yes → init orders 10/20/30 on first interaction" → spell out: which function performs the init, when it runs (mount vs first-swap), how it detects the "first use" state, what happens on re-entry.
+
+## Why this will work
+REQUIRED if research cites a prior failed attempt (closed PR, reverted commit, previous run that didn't land), or if prior-art above contains a diff.
+ - Root-cause hypothesis — what specifically went wrong in the prior attempt (cite lines from the prior diff above).
+ - The specific change in THIS plan that addresses the root cause — name the file/line/hook/config that differs from the prior attempt.
+ - How you will verify the fix works — a concrete behavioral check (URL + action + expected UI, or API call + expected response, or a test case). Not "typecheck passes."
+
+## API surface verification
+REQUIRED for every hook, import, SDK method, framework primitive, or config key the plan names.
+ - Build a table or list. For each named symbol: the file path where it's defined, or the exact package + export (with a `node_modules/...` path you actually read), or the mark `UNVERIFIED`.
+ - Do not guess. If you could not find it with Read / Grep / Glob, it is UNVERIFIED. Do not rely on UNVERIFIED symbols in the plan — flag them as blockers.
+ - Include negative evidence too: "Searched for `useXxx` in `@payloadcms/ui` exports — not found; planner assumed `useDocumentInfo` instead."
+
+## Initial data state → transition → steady state
+REQUIRED if the feature mutates existing data (reorder, migrate, backfill, rename, enable).
+ - Initial state: describe the data as it is in production today, including edge cases (rows with NULL, rows with default zero, orphan rows, etc).
+ - Transition: the exact step(s) that move data from initial → steady, including who triggers them (user action, migration script, on-mount hook), idempotency, and rollback behavior.
+ - Steady state: what invariants hold after transition.
+ - Failure modes during transition: partial-apply, race conditions, concurrent writers.
+
+## Error paths & failure handling
+For each external call or mutation in the plan (API request, DB write, file op, SDK call), enumerate:
+ - What can fail (network, validation, auth, not-found, conflict, rate limit).
+ - What the UI/caller does on each failure — retry, surface error, rollback, log-and-continue.
+ - What state the system is left in if the op fails mid-way.
+
+## Test plan
+ - Specific test cases by name, with inputs and expected outputs. Not "add unit tests."
+ - Unit tests: one line per test naming what it asserts.
+ - Integration / behavioral tests: one line each, naming the flow covered and the assertion.
+ - Regression tests for the prior-art failure mode (if applicable) — a test that would have caught the prior bug.
+ - Manual verification steps: URL + click sequence + expected UI, or API call + expected response.
+
+## Ambiguities & assumptions
+ - List anything still unresolved that needs human input before implementation.
+ - List every assumption the plan makes that was NOT confirmed by the issue, comments, or code (e.g. "assumed `usePayload` hook exists — UNVERIFIED").
+
+## Verification checklist
+ - Build / typecheck / test / lint commands expected to pass after implementation.
+ - Each concrete behavioral check from "Test plan" restated as a pass/fail gate.
+
+No filler. No marketing language. Depth over brevity.>
 ```
 
 # Rules
 - Read-only. Do NOT modify any file.
 - Do NOT run git or gh commands.
-- No speculative scope — plan only what the issue asks for.
+- No speculative scope — plan only what the issue asks for, but plan it THOROUGHLY.
 - If the issue is ambiguous and you cannot make progress without input, output `FAILED: <what's unclear>` instead of a plan.
+- If the Research floor cannot be met because required files are missing or unreadable, output `FAILED: <what could not be read>` instead of a half-blind plan.

package/dist/executables/plan-verify/profile.json

@@ -1,7 +1,7 @@
 {
   "name": "plan-verify",
   "role": "utility",
-  "describe": "Live-test executable. Loads kody-live-marker skill, /kody-live-probe command, kody-live-trace hook, and the bundled test-plugin. Asks the agent to emit confirmation tokens for each feature so Kody2 can validate plugin wiring end-to-end.",
+  "describe": "Live-test executable. Loads kody-live-marker skill, /kody-live-probe command, kody-live-trace hook, and the bundled test-plugin. Asks the agent to emit confirmation tokens for each feature so Kody can validate plugin wiring end-to-end.",
   "inputs": [
     { "name": "issue", "flag": "--issue", "type": "int", "required": true, "describe": "GitHub issue number to verify against." }
   ],
@@ -9,7 +9,7 @@
     "model": "inherit",
     "permissionMode": "default",
     "maxTurns": 15,
-    "systemPromptAppend": "You are running Kody2's plugin-wiring live verification. Emit confirmation tokens exactly as the prompt instructs.",
+    "systemPromptAppend": "You are running Kody's plugin-wiring live verification. Emit confirmation tokens exactly as the prompt instructs.",
     "tools": ["Read", "Grep", "Glob", "Bash"],
     "hooks": ["kody-live-trace"],
     "skills": ["kody-live-marker"],

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

@@ -1,4 +1,4 @@
-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.
+You are Kody'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}}
 

package/dist/executables/research/profile.json

@@ -27,9 +27,26 @@
     "commands": [],
     "subagents": [],
     "plugins": [],
-    "mcpServers": []
+    "mcpServers": [
+      {
+        "name": "playwright",
+        "command": "npx",
+        "args": ["-y", "@playwright/mcp@latest"]
+      }
+    ]
   },
-  "cliTools": [],
+  "cliTools": [
+    {
+      "name": "playwright",
+      "install": {
+        "required": false,
+        "checkCommand": "npx --no-install playwright --version",
+        "installCommand": "npx --yes playwright install --with-deps chromium"
+      },
+      "verify": "npx --no-install playwright --version",
+      "usage": ""
+    }
+  ],
   "scripts": {
     "preflight": [
       {
@@ -37,7 +54,7 @@
         "with": {
           "label": "kody:researching",
           "color": "1d76db",
-          "description": "kody2: researching the issue"
+          "description": "kody: researching the issue"
         }
       },
       {
@@ -84,6 +101,11 @@
         "name": "research",
         "format": "markdown",
         "from": "prSummary"
+      },
+      {
+        "name": "priorArt",
+        "format": "json",
+        "from": "priorArt"
       }
     ]
   }

package/dist/executables/research/prompt.md

@@ -25,6 +25,7 @@ Your FINAL message must be exactly this shape (no extra text before or after):
 ```
 DONE
 COMMIT_MSG: research: <very short title>
+PRIOR_ART: <JSON array of closed or merged PR numbers from this repo that are prior attempts at THIS issue, or [] if none. Include only PRs that actually touched the same feature/area — not every PR your research happens to mention. Example: [1086] or []. Must be valid JSON parseable as number[].>
 PR_SUMMARY:
 <A research doc in markdown with EXACTLY these sections, in order:
 
@@ -82,6 +83,9 @@ Gaps & assumptions — they live in the prior comment. Keep the whole delta
 under 25 lines. If nothing has changed since the prior research, output
 `FAILED: no new information since last research` instead.
 
+`PRIOR_ART:` is still required in delta mode (carry forward the prior list,
+or update it if new PRs became relevant since).
+
 If no prior `## Research for issue` comment exists in the thread, produce
 the full first-pass structure below.
 

package/dist/executables/resolve/profile.json

@@ -39,7 +39,7 @@
         "with": {
           "label": "kody:resolving",
           "color": "b60205",
-          "description": "kody2: resolving merge conflicts"
+          "description": "kody: resolving merge conflicts"
         }
       },
       {

package/dist/executables/review/profile.json

@@ -28,9 +28,26 @@
     "commands": [],
     "subagents": [],
     "plugins": [],
-    "mcpServers": []
+    "mcpServers": [
+      {
+        "name": "playwright",
+        "command": "npx",
+        "args": ["-y", "@playwright/mcp@latest"]
+      }
+    ]
   },
-  "cliTools": [],
+  "cliTools": [
+    {
+      "name": "playwright",
+      "install": {
+        "required": false,
+        "checkCommand": "npx --no-install playwright --version",
+        "installCommand": "npx --yes playwright install --with-deps chromium"
+      },
+      "verify": "npx --no-install playwright --version",
+      "usage": ""
+    }
+  ],
   "scripts": {
     "preflight": [
       {
@@ -38,7 +55,7 @@
         "with": {
           "label": "kody:reviewing",
           "color": "d93f0b",
-          "description": "kody2: reviewing a PR"
+          "description": "kody: reviewing a PR"
         }
       },
       {

package/dist/executables/run/profile.json

@@ -39,7 +39,7 @@
         "with": {
           "label": "kody:running",
           "color": "fbca04",
-          "description": "kody2: implementing the change"
+          "description": "kody: implementing the change"
         }
       },
       { "script": "runFlow" },

package/dist/executables/run/prompt.md

@@ -7,7 +7,7 @@ You are Kody, an autonomous engineer. Take a GitHub issue from spec to a tested
 {{conventionsBlock}}{{coverageBlock}}{{toolsUsage}}# Issue #{{issue.number}}: {{issue.title}}
 {{issue.body}}
 
-# Existing plan (produced by `@kody2 plan`, if present)
+# Existing plan (produced by `@kody plan`, if present)
 {{artifacts.plan}}
 
 If the plan above is non-empty, TREAT IT AS AUTHORITATIVE — follow its file list and approach rather than inventing your own. Deviate only if the plan is wrong; if you do, you MUST declare each deviation in the `PLAN_DEVIATIONS:` block of your final message (format below). Silent deviations are a hard failure, even if the code works. If the plan is empty, proceed from first principles and emit `PLAN_DEVIATIONS: none` in the final message.
@@ -32,7 +32,7 @@ If the plan above is non-empty, TREAT IT AS AUTHORITATIVE — follow its file li
 # Rules
 - Do NOT run **any** `git` or `gh` commands. The wrapper handles all git/gh operations. If a quality gate fails, that's the failure — do not investigate it via git.
 - Stay on the current branch (`{{branch}}`). It is already checked out for you.
-- Do NOT modify files under: `.kody/`, `.kody-engine/`, `.kody-lean/`, `.kody2/`, `node_modules/`, `dist/`, `build/`, `.env`, or any `*.log`.
+- Do NOT modify files under: `.kody/`, `.kody-engine/`, `.kody-lean/`, `.kody/`, `node_modules/`, `dist/`, `build/`, `.env`, or any `*.log`.
 - Do NOT post issue comments — the wrapper handles that.
 - Pre-existing quality-gate failures: assume they are NOT your responsibility unless your edits touched related code.
 - Keep the plan and reasoning concise. Long monologues waste turns.

package/dist/executables/spec/profile.json

@@ -33,7 +33,7 @@
         "with": {
           "label": "kody-flow:spec",
           "color": "7057ff",
-          "description": "kody2 flow: spec / RFC / design-doc"
+          "description": "kody flow: spec / RFC / design-doc"
         }
       },
       {
@@ -41,7 +41,7 @@
         "with": {
           "label": "kody:orchestrating",
           "color": "1d76db",
-          "description": "kody2: orchestrating a multi-stage flow"
+          "description": "kody: orchestrating a multi-stage flow"
         }
       },
       { "script": "loadIssueContext" },
@@ -55,11 +55,11 @@
         "runWhen": { "data.taskState.core.lastOutcome.type": "RESEARCH_COMPLETED" } },
 
       { "script": "finishFlow",
-        "with": { "reason": "spec-ready", "label": "kody:done", "color": "0e8a16", "description": "kody2: spec/plan artifact ready" },
+        "with": { "reason": "spec-ready", "label": "kody:done", "color": "0e8a16", "description": "kody: spec/plan artifact ready" },
         "runWhen": { "data.taskState.core.lastOutcome.type": "PLAN_COMPLETED" } },
 
       { "script": "finishFlow",
-        "with": { "reason": "aborted", "label": "kody:failed", "color": "e11d21", "description": "kody2: flow failed" },
+        "with": { "reason": "aborted", "label": "kody:failed", "color": "e11d21", "description": "kody: flow failed" },
         "runWhen": { "data.taskState.core.lastOutcome.type": ["RESEARCH_FAILED", "PLAN_FAILED", "AGENT_NOT_RUN"] } },
 
       { "script": "persistFlowState" }

package/dist/executables/sync/profile.json

@@ -32,7 +32,7 @@
         "with": {
           "label": "kody:syncing",
           "color": "c5def5",
-          "description": "kody2: syncing PR with base"
+          "description": "kody: syncing PR with base"
         }
       },
       {