@kody-ade/kody-engine 0.2.9 → 0.2.11

package/dist/bin/kody2.js

@@ -3,7 +3,7 @@
 // package.json
 var package_default = {
   name: "@kody-ade/kody-engine",
-  version: "0.2.9",
+  version: "0.2.11",
   description: "kody2 \u2014 autonomous development engine. Single-session Claude Code agent behind a generic executor + declarative executable profiles.",
   license: "MIT",
   type: "module",
@@ -1963,6 +1963,27 @@ var loadCoverageRules = async (ctx) => {
   ctx.data.coverageRules = ctx.config.testRequirements ?? [];
 };
 
+// src/scripts/loadIssueContext.ts
+var DEFAULT_COMMENT_LIMIT = 12;
+var DEFAULT_COMMENT_MAX_BYTES = 4e3;
+var loadIssueContext = async (ctx) => {
+  const issueNumber = ctx.args.issue;
+  if (typeof issueNumber !== "number" || issueNumber <= 0) {
+    throw new Error("loadIssueContext: ctx.args.issue (positive integer) is required");
+  }
+  const issue = getIssue(issueNumber, ctx.cwd);
+  const cfgCtx = ctx.config.issueContext ?? {};
+  const limit = cfgCtx.commentLimit ?? DEFAULT_COMMENT_LIMIT;
+  const maxBytes = cfgCtx.commentMaxBytes ?? DEFAULT_COMMENT_MAX_BYTES;
+  const sorted = [...issue.comments].sort((a, b) => a.createdAt < b.createdAt ? 1 : -1);
+  const kept = sorted.slice(0, limit);
+  const commentsFormatted = kept.length === 0 ? "(no comments yet)" : kept.map((c) => `- **${c.author}** (${c.createdAt}):
+  ${truncate2(c.body, maxBytes).replace(/\n/g, "\n  ")}`).join("\n\n");
+  ctx.data.issue = { ...issue, commentsFormatted };
+  ctx.data.commentTargetType = "issue";
+  ctx.data.commentTargetNumber = issueNumber;
+};
+
 // src/state.ts
 import { execFileSync as execFileSync10 } from "child_process";
 var STATE_BEGIN = "<!-- kody2:state:v1:begin -->";
@@ -2966,6 +2987,7 @@ var preflightScripts = {
   releaseFlow,
   watchStalePrsFlow,
   loadTaskState,
+  loadIssueContext,
   loadConventions,
   loadCoverageRules,
   composePrompt

package/dist/executables/orchestrator/profile.json

@@ -37,13 +37,12 @@
 
   "scripts": {
     "preflight": [
-      { "script": "runFlow" },
+      { "script": "loadIssueContext" },
       { "script": "loadTaskState" },
       { "script": "composePrompt" }
     ],
     "postflight": [
       { "script": "parseAgentResult" },
-      { "script": "postIssueComment" },
       { "script": "writeRunSummary" },
       { "script": "saveTaskState" }
     ]

package/dist/executables/orchestrator/prompt.md

@@ -0,0 +1,56 @@
+You are the **kody2 orchestrator** for issue #{{issue.number}} on {{repoOwner}}/{{repoName}}.
+
+Your job: drive a 2-step flow **plan → build** by posting `@kody2 <subcommand>` comments on the issue and watching the state-comment for completion signals. You do NOT edit files. You do NOT run git. You use `gh` (via Bash) only to post comments and read the state-comment.
+
+---
+
+# Issue #{{issue.number}}: {{issue.title}}
+
+{{issue.body}}
+
+# Required flow (plan-then-build)
+
+1. **Kick off plan.** Post an issue comment with EXACTLY this body:
+   ```
+   @kody2 plan
+   ```
+   Use: `gh issue comment {{issue.number}} --body "@kody2 plan"` (in the cwd).
+2. **Wait for plan to complete.** Poll the issue's state-comment every ~30s. The state-comment is the one whose body starts with `<!-- kody2:state:v1:begin -->`. Fetch it with:
+   ```
+   gh api repos/{{repoOwner}}/{{repoName}}/issues/{{issue.number}}/comments --paginate --jq '.[] | select(.body | contains("kody2:state:v1:begin")) | .body'
+   ```
+   Parse the JSON block inside the sentinels. Look for `core.lastOutcome.type == "PLAN_COMPLETED"`.
+   If `core.lastOutcome.type == "PLAN_FAILED"` OR if 10 minutes pass without completion → abort with:
+   ```
+   FAILED: plan did not complete (<reason from state or "timeout">)
+   ```
+3. **Kick off build.** Post:
+   ```
+   @kody2 build
+   ```
+   Same `gh issue comment` command.
+4. **Wait for build to complete.** Same poll technique. Look for `core.lastOutcome.type == "RUN_COMPLETED"` (build's success marker) or `RUN_FAILED`. If `RUN_FAILED` or 30 minutes pass → abort with `FAILED: build did not complete (...)`.
+5. **Emit final summary.**
+
+# Required final output
+
+On success:
+
+```
+DONE
+COMMIT_MSG: chore(orchestrator): plan-then-build for #{{issue.number}}
+PR_SUMMARY:
+- Posted `@kody2 plan` and observed PLAN_COMPLETED.
+- Posted `@kody2 build` and observed RUN_COMPLETED.
+- Final PR: <prUrl from state>
+```
+
+On failure, a single line: `FAILED: <concrete reason>`.
+
+# Rules
+
+- NEVER edit files. Read-only flow.
+- NEVER run git. Only `gh` via Bash for comment posting and state polling.
+- Between polls, sleep ~30 seconds. Do NOT poll faster than once every 30 seconds.
+- Hard cap: 40 turns total across the whole flow. If you're approaching the cap, fail early with `FAILED: turn budget exhausted`.
+- If you post an `@kody2` comment and the state-comment does NOT update within the poll window, the child executable likely didn't run — check the GitHub Actions runs tab URL via `gh run list --limit 5 --json conclusion,status,url` to diagnose, then fail with a concrete reason.

package/dist/executables/plan/profile.json

@@ -30,14 +30,13 @@
 
   "scripts": {
     "preflight": [
-      { "script": "runFlow" },
+      { "script": "loadIssueContext" },
       { "script": "loadTaskState" },
       { "script": "loadConventions" },
       { "script": "composePrompt" }
     ],
     "postflight": [
       { "script": "parseAgentResult" },
-      { "script": "postIssueComment" },
       { "script": "writeRunSummary" },
       { "script": "saveTaskState" }
     ]

package/dist/executables/plan/prompt.md

@@ -0,0 +1,42 @@
+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:
+
+1. Use Read / Grep / Glob / Bash (read-only) to study the codebase as much as needed.
+2. Emit a final message with the plan 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: 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.>
+```
+
+# 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.
+- If the issue is ambiguous and you cannot make progress without input, output `FAILED: <what's unclear>` instead of a plan.

package/package.json

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