@kody-ade/kody-engine 0.3.16 → 0.3.18

package/dist/bin/kody.js

@@ -3,7 +3,7 @@
 // package.json
 var package_default = {
   name: "@kody-ade/kody-engine",
-  version: "0.3.16",
+  version: "0.3.18",
   description: "kody \u2014 autonomous development engine. Single-session Claude Code agent behind a generic executor + declarative executable profiles.",
   license: "MIT",
   type: "module",
@@ -675,10 +675,10 @@ function autoDispatch(opts) {
     if (!Number.isNaN(n) && n > 0) {
       return { executable: "run", cliArgs: { issue: n }, target: n };
     }
-    return { executable: "manager", cliArgs: {}, target: 0 };
+    return { executable: "mission-scheduler", cliArgs: {}, target: 0 };
   }
   if (eventName === "schedule") {
-    return { executable: "manager", cliArgs: {}, target: 0 };
+    return { executable: "mission-scheduler", cliArgs: {}, target: 0 };
   }
   if (eventName !== "issue_comment") return null;
   const body = String(event.comment?.body ?? "").toLowerCase();
@@ -2735,26 +2735,26 @@ function postPrReviewComment(prNumber, body, cwd) {
   }
 }
 
-// src/scripts/dispatchManagerTicks.ts
-var dispatchManagerTicks = async (ctx, _profile, args) => {
+// src/scripts/dispatchMissionTicks.ts
+var dispatchMissionTicks = async (ctx, _profile, args) => {
   ctx.skipAgent = true;
   const label = String(args?.label ?? "");
   const targetExecutable = String(args?.targetExecutable ?? "");
-  if (!label) throw new Error("dispatchManagerTicks: `with.label` is required");
-  if (!targetExecutable) throw new Error("dispatchManagerTicks: `with.targetExecutable` is required");
+  if (!label) throw new Error("dispatchMissionTicks: `with.label` is required");
+  if (!targetExecutable) throw new Error("dispatchMissionTicks: `with.targetExecutable` is required");
   const issueArg = String(args?.issueArg ?? "issue");
   const issues = listIssuesByLabel(label, ctx.cwd);
-  ctx.data.managerIssueCount = issues.length;
+  ctx.data.missionIssueCount = issues.length;
   if (issues.length === 0) {
-    process.stdout.write(`[manager] no open issues with label "${label}"
+    process.stdout.write(`[missions] no open issues with label "${label}"
 `);
     return;
   }
-  process.stdout.write(`[manager] ticking ${issues.length} issue(s) via ${targetExecutable}
+  process.stdout.write(`[missions] ticking ${issues.length} issue(s) via ${targetExecutable}
 `);
   const results = [];
   for (const issue of issues) {
-    process.stdout.write(`[manager] \u2192 tick #${issue.number}: ${issue.title}
+    process.stdout.write(`[missions] \u2192 tick #${issue.number}: ${issue.title}
 `);
     try {
       const out = await runExecutable(targetExecutable, {
@@ -2766,17 +2766,17 @@ var dispatchManagerTicks = async (ctx, _profile, args) => {
       });
       results.push({ issue: issue.number, exitCode: out.exitCode, reason: out.reason });
       if (out.exitCode !== 0) {
-        process.stderr.write(`[manager] tick #${issue.number} failed (exit ${out.exitCode}): ${out.reason ?? ""}
+        process.stderr.write(`[missions] tick #${issue.number} failed (exit ${out.exitCode}): ${out.reason ?? ""}
 `);
       }
     } catch (err) {
       const msg = err instanceof Error ? err.message : String(err);
-      process.stderr.write(`[manager] tick #${issue.number} crashed: ${msg}
+      process.stderr.write(`[missions] tick #${issue.number} crashed: ${msg}
 `);
       results.push({ issue: issue.number, exitCode: 99, reason: msg });
     }
   }
-  ctx.data.managerTickResults = results;
+  ctx.data.missionTickResults = results;
   ctx.output.exitCode = 0;
 };
 function listIssuesByLabel(label, cwd) {
@@ -5544,7 +5544,7 @@ var preflightScripts = {
   skipAgent,
   classifyByLabel,
   diagMcp,
-  dispatchManagerTicks
+  dispatchMissionTicks
 };
 var postflightScripts = {
   parseAgentResult: parseAgentResult2,

package/dist/executables/{manager → mission-scheduler}/profile.json

@@ -1,7 +1,7 @@
 {
-  "name": "manager",
+  "name": "mission-scheduler",
   "role": "watch",
-  "describe": "Scheduled: for every open issue labeled kody:manager, invoke manager-tick once. No agent on the scheduler itself.",
+  "describe": "Scheduled: for every open issue labeled kody:mission, invoke mission-tick once. No agent on the scheduler itself.",
   "kind": "scheduled",
   "schedule": "*/5 * * * *",
   "inputs": [],
@@ -36,12 +36,12 @@
   "scripts": {
     "preflight": [
       {
-        "script": "dispatchManagerTicks",
+        "script": "dispatchMissionTicks",
         "with": {
-          "label": "kody:manager",
+          "label": "kody:mission",
           "color": "1d76db",
-          "description": "kody: issue is a manager mission — scheduler will tick it on every cron wake",
-          "targetExecutable": "manager-tick",
+          "description": "kody: issue is a mission — scheduler ticks it every cron wake",
+          "targetExecutable": "mission-tick",
           "issueArg": "issue"
         }
       }

package/dist/executables/{manager-tick → mission-tick}/profile.json

@@ -1,7 +1,7 @@
 {
-  "name": "manager-tick",
+  "name": "mission-tick",
   "role": "primitive",
-  "describe": "One classifier tick for one manager issue: read intent + state, decide and execute via gh, emit next state.",
+  "describe": "One classifier tick for one mission issue: read intent + state, decide and execute via gh, emit next state.",
   "kind": "oneshot",
   "inputs": [
     {
@@ -9,7 +9,7 @@
       "flag": "--issue",
       "type": "int",
       "required": true,
-      "describe": "GitHub issue number that owns this manager mission."
+      "describe": "GitHub issue number that owns this mission."
     }
   ],
   "claudeCode": {
@@ -45,7 +45,7 @@
       {
         "script": "loadIssueStateComment",
         "with": {
-          "marker": "kody-manager-state",
+          "marker": "kody-mission-state",
           "issueArg": "issue"
         }
       },
@@ -57,13 +57,13 @@
       {
         "script": "parseIssueStateFromAgentResult",
         "with": {
-          "fenceLabel": "kody-manager-next-state"
+          "fenceLabel": "kody-mission-next-state"
         }
       },
       {
         "script": "writeIssueStateComment",
         "with": {
-          "marker": "kody-manager-state",
+          "marker": "kody-mission-state",
           "issueArg": "issue"
         }
       }

package/dist/executables/{manager-tick → mission-tick}/prompt.md

@@ -1,4 +1,4 @@
-You are **kody manager-tick**, the coordinator for one GitHub-issue-scoped mission. You do **not** touch code, do **not** commit, and do **not** edit files. You coordinate other kody executables by dispatching their workflows, observing their runs, and writing back state.
+You are **kody mission-tick**, the coordinator for one GitHub-issue-scoped mission. You do **not** touch code, do **not** commit, and do **not** edit files. You coordinate other kody executables by dispatching their workflows, observing their runs, and writing back state.
 
 ## The mission
 
@@ -16,25 +16,26 @@ This is the state you wrote at the end of the previous tick (or `null` if this i
 {{issueStateJson}}
 ```
 
-`cursor` is *your* enum — pick whatever labels map cleanly to your mission's phases (e.g. `seed`, `spawn-release`, `waiting-release`, `merge-to-dev`, `finalize`, `done`). `data` is where you stash anything you need on the next tick (run IDs, SHAs, child issue numbers, budget counters). `done: true` tells the scheduler to stop calling you.
+`cursor` is *your* enum — pick whatever labels map cleanly to your mission's phases (e.g. `seed`, `spawn-release`, `waiting-release`, `merge-to-dev`, `finalize`, `done`). `data` is where you stash anything you need on the next tick (run IDs, SHAs, child issue numbers, budget counters). `done: true` is how you signal to future-you that the mission is over — check for it first on every tick and exit early without acting if it's set. Closing the issue also stops ticks (the scheduler only lists open issues).
 
 ## What to do on this tick
 
-1. **Re-read the mission.** If the human has edited the description in a way that changes what "on track" means, adapt.
-2. **Decide the single next step** based on (cursor, data, mission).
+1. **Check `done`.** If the prior state has `done: true`, emit the same state back unchanged and exit without any other action. The mission is over; don't resurrect it.
+2. **Re-read the mission.** If the human has edited the description in a way that changes what "on track" means, adapt.
+3. **Decide the single next step** based on (cursor, data, mission).
    - If `cursor` is `null`/first-run, initialize: plan the pipeline, pick an initial cursor, record any baseline info in `data`.
    - If you're waiting on a child run, check its status via `gh run view <id> --json status,conclusion`. If still running, just update cursor/data minimally and exit — the next cron wake will check again. If succeeded, advance. If failed, record the failure and either spawn a remediation child or mark `done: true` with an error.
    - If it's time to spawn a child executable, use `gh workflow run kody.yml -f issue_number=<N>` (or the appropriate workflow + inputs for the consumer repo). Capture the dispatched run's ID via `gh run list --workflow=kody.yml --limit 1 --json databaseId --jq '.[0].databaseId'` and stash it in `data`.
    - If the mission is complete, set `done: true` and a terminal cursor like `done`.
-3. **Optionally post a human-readable narration comment** on the issue summarizing what you just did (spawned run #12345, waiting on CI, etc.). Keep it short. Use `gh issue comment {{issueNumber}} --body "..."`.
-4. **Emit the new state** at the very end of your response using the fenced block below. Do not include `version` or `rev` — the postflight script manages those.
+4. **Optionally post a human-readable narration comment** on the issue summarizing what you just did (spawned run #12345, waiting on CI, etc.). Keep it short. Use `gh issue comment {{issueNumber}} --body "..."`.
+5. **Emit the new state** at the very end of your response using the fenced block below. Do not include `version` or `rev` — the postflight script manages those.
 
 ## Output contract (MANDATORY, exactly once, at the end)
 
-End your response with a single fenced block using the `kody-manager-next-state` language tag:
+End your response with a single fenced block using the `kody-mission-next-state` language tag:
 
 ````
-```kody-manager-next-state
+```kody-mission-next-state
 {
   "cursor": "<your-next-cursor>",
   "data": { ... },

package/package.json

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