@kody-ade/kody-engine 0.2.40 → 0.2.41

package/dist/bin/kody2.js

@@ -3,7 +3,7 @@
 // package.json
 var package_default = {
   name: "@kody-ade/kody-engine",
-  version: "0.2.40",
+  version: "0.2.41",
   description: "kody2 \u2014 autonomous development engine. Single-session Claude Code agent behind a generic executor + declarative executable profiles.",
   license: "MIT",
   type: "module",
@@ -2855,6 +2855,24 @@ ${plan}
 Comment \`@kody2 run\` to execute this plan.`;
 }
 
+// src/scripts/postResearchComment.ts
+var postResearchComment = async (ctx) => {
+  if (!ctx.data.agentDone) return;
+  const targetType = ctx.data.commentTargetType;
+  const targetNumber = Number(ctx.data.commentTargetNumber ?? 0);
+  const body = ctx.data.prSummary?.trim();
+  if (targetType !== "issue" || !targetNumber || !body) return;
+  try {
+    postIssueComment(targetNumber, renderResearchComment(targetNumber, body), ctx.cwd);
+  } catch {
+  }
+};
+function renderResearchComment(issueNumber, body) {
+  return `## Research for issue #${issueNumber}
+
+${body}`;
+}
+
 // src/scripts/postReviewResult.ts
 function detectVerdict(body) {
   const m = body.match(/##\s*Verdict\s*:\s*(PASS|CONCERNS|FAIL)\b/i);
@@ -3781,6 +3799,7 @@ var postflightScripts = {
   ensurePr: ensurePr2,
   postIssueComment: postIssueComment2,
   postPlanComment,
+  postResearchComment,
   postReviewResult,
   persistArtifacts,
   writeRunSummary,

package/dist/executables/research/profile.json

@@ -0,0 +1,78 @@
+{
+  "name": "research",
+  "describe": "Research an issue: understand the ask, map relevant repo context, and surface clarifying questions + gaps. Read-only — no branches, no commits, no prescribed next steps.",
+  "inputs": [
+    {
+      "name": "issue",
+      "flag": "--issue",
+      "type": "int",
+      "required": true,
+      "describe": "GitHub issue number to research."
+    }
+  ],
+  "claudeCode": {
+    "model": "inherit",
+    "permissionMode": "default",
+    "maxTurns": null,
+    "systemPromptAppend": null,
+    "tools": [
+      "Read",
+      "Grep",
+      "Glob",
+      "Bash"
+    ],
+    "hooks": [],
+    "skills": [],
+    "commands": [],
+    "subagents": [],
+    "plugins": [],
+    "mcpServers": []
+  },
+  "cliTools": [],
+  "scripts": {
+    "preflight": [
+      {
+        "script": "loadIssueContext"
+      },
+      {
+        "script": "loadTaskState"
+      },
+      {
+        "script": "loadConventions"
+      },
+      {
+        "script": "composePrompt"
+      }
+    ],
+    "postflight": [
+      {
+        "script": "parseAgentResult"
+      },
+      {
+        "script": "persistArtifacts"
+      },
+      {
+        "script": "postResearchComment"
+      },
+      {
+        "script": "writeRunSummary"
+      },
+      {
+        "script": "saveTaskState"
+      }
+    ]
+  },
+  "output": {
+    "actionTypes": [
+      "RESEARCH_COMPLETED",
+      "RESEARCH_FAILED"
+    ],
+    "artifacts": [
+      {
+        "name": "research",
+        "format": "markdown",
+        "from": "prSummary"
+      }
+    ]
+  }
+}

package/dist/executables/research/prompt.md

@@ -0,0 +1,61 @@
+You are a senior engineer **researching** a GitHub issue. Your job is to fill in missing information so a downstream planner (human or agent) can make a decision. You will NOT write code. You will NOT run git or gh commands. You will NOT modify files. You will NOT prescribe a next step.
+
+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").
+
+---
+
+# Repo
+- {{repoOwner}}/{{repoName}}, default branch: {{defaultBranch}}
+
+# Issue #{{issue.number}}: {{issue.title}}
+
+{{issue.body}}
+
+Recent comments (most recent first, truncated):
+{{issue.commentsFormatted}}
+
+{{conventionsBlock}}
+
+---
+
+# Required output
+
+Your FINAL message must be exactly this shape (no extra text before or after):
+
+```
+DONE
+COMMIT_MSG: research: <very short title>
+PR_SUMMARY:
+<A research doc in markdown with EXACTLY these sections, in order:
+
+## Understood request
+One paragraph restating what the issue is asking for, in your own words.
+
+## Repo context
+Files, modules, and existing patterns most relevant to the request. Use
+`path/to/file.ts` references. Note anything that constrains the solution
+space (existing abstractions, invariants from AGENTS.md / CLAUDE.md).
+
+## Clarifying questions
+Numbered list. Each question must include a one-line "Why:" explaining why
+the answer changes the implementation. Skip if there are genuinely none.
+
+## Gaps & assumptions
+What is unknown, and — for each gap — what assumption the implementer would
+have to make if it stays unanswered.
+
+## Proposed scope
+Two bullet lists: **In scope** and **Out of scope**. Keep tight: only what
+the issue asks for; call out adjacent work that should NOT be bundled.
+
+Keep the whole doc to ~80 lines or less. No filler. No marketing language.
+Do NOT include a "Next steps" / "Recommendation" / "How to proceed" section —
+research stops at findings.>
+```
+
+# Rules
+- Read-only. Do NOT modify any file.
+- Do NOT run git or gh commands.
+- Do NOT propose an implementation plan — that's the planner's job.
+- Do NOT tell the user what command to run next.
+- If the issue is empty or incomprehensible, output `FAILED: <why>` instead.

package/package.json

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