@kody-ade/kody-engine 0.4.220 → 0.4.222

package/dist/duties/duty-scheduler/duty.md

@@ -0,0 +1,3 @@
+# Duty Scheduler
+
+Scan `.kody/duties/` for due duty folders and run each due duty through its declared executable.

package/dist/duties/duty-scheduler/profile.json

@@ -0,0 +1,6 @@
+{
+  "name": "duty-scheduler",
+  "action": "duty-scheduler",
+  "executable": "duty-scheduler",
+  "describe": "Schedule due duty folders."
+}

package/dist/duties/duty-tick/duty.md

@@ -0,0 +1,3 @@
+# Duty Tick
+
+Run one scheduled duty folder using its duty prompt, staff persona, tools, and state.

package/dist/duties/duty-tick/profile.json

@@ -0,0 +1,6 @@
+{
+  "name": "duty-tick",
+  "action": "duty-tick",
+  "executable": "duty-tick",
+  "describe": "Run one folder duty tick."
+}

package/dist/duties/duty-tick-scripted/duty.md

@@ -0,0 +1,3 @@
+# Duty Tick Scripted
+
+Run one scheduled duty folder through its deterministic tick script and persist the next duty state.

package/dist/duties/duty-tick-scripted/profile.json

@@ -0,0 +1,6 @@
+{
+  "name": "duty-tick-scripted",
+  "action": "duty-tick-scripted",
+  "executable": "duty-tick-scripted",
+  "describe": "Run one scripted folder duty tick."
+}

package/dist/duties/goal-scheduler/duty.md

@@ -0,0 +1,3 @@
+# Goal Scheduler
+
+Scan active goal state and run one goal tick per active goal.

package/dist/duties/goal-scheduler/profile.json

@@ -0,0 +1,6 @@
+{
+  "name": "goal-scheduler",
+  "action": "goal-scheduler",
+  "executable": "goal-scheduler",
+  "describe": "Schedule active goals."
+}

package/dist/duties/goal-tick/duty.md

@@ -0,0 +1,3 @@
+# Goal Tick
+
+Read one goal state file, dispatch the next ready task, or finalize the goal when all tasks are complete.

package/dist/duties/goal-tick/profile.json

@@ -0,0 +1,6 @@
+{
+  "name": "goal-tick",
+  "action": "goal-tick",
+  "executable": "goal-tick",
+  "describe": "Advance one goal."
+}

package/dist/duties/job-live-verify/duty.md

@@ -0,0 +1,3 @@
+# Job Live Verify
+
+Verify live job reference, staff, duty, executable, skill, and state wiring.

package/dist/duties/job-live-verify/profile.json

@@ -0,0 +1,6 @@
+{
+  "name": "job-live-verify",
+  "action": "job-live-verify",
+  "executable": "job-live-verify",
+  "describe": "Verify live job wiring."
+}

package/dist/duties/plan-verify/duty.md

@@ -0,0 +1,3 @@
+# Plan Verify
+
+Verify one planned task slice.

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

@@ -0,0 +1,6 @@
+{
+  "name": "plan-verify",
+  "action": "plan-verify",
+  "executable": "plan-verify",
+  "describe": "Verify a planned task slice."
+}

package/dist/duties/probe-skill/duty.md

@@ -0,0 +1,3 @@
+# Probe Skill
+
+Run the probe skill test executable.

package/dist/duties/probe-skill/profile.json

@@ -0,0 +1,6 @@
+{
+  "name": "probe-skill",
+  "action": "probe-skill",
+  "executable": "probe-skill",
+  "describe": "Run the probe skill test executable."
+}

package/dist/duties/qa-goal/duty.md

@@ -0,0 +1,3 @@
+# QA Goal
+
+Run one QA goal workflow.

package/dist/duties/qa-goal/profile.json

@@ -0,0 +1,6 @@
+{
+  "name": "qa-goal",
+  "action": "qa-goal",
+  "executable": "qa-goal",
+  "describe": "Run a QA goal."
+}

package/dist/duties/task-job-fail-once/duty.md

@@ -0,0 +1,3 @@
+# Task Job Fail Once
+
+Fail the first run and pass after a recorded failed attempt.

package/dist/duties/task-job-fail-once/profile.json

@@ -0,0 +1,6 @@
+{
+  "name": "task-job-fail-once",
+  "action": "task-job-fail-once",
+  "executable": "task-job-fail-once",
+  "describe": "Fail once for task job retry verification."
+}

package/dist/duties/task-job-pass-a/duty.md

@@ -0,0 +1,3 @@
+# Task Job Pass A
+
+Run task job pass test A.

package/dist/duties/task-job-pass-a/profile.json

@@ -0,0 +1,6 @@
+{
+  "name": "task-job-pass-a",
+  "action": "task-job-pass-a",
+  "executable": "task-job-pass-a",
+  "describe": "Pass task job test A."
+}

package/dist/duties/task-job-pass-b/duty.md

@@ -0,0 +1,3 @@
+# Task Job Pass B
+
+Run task job pass test B.

package/dist/duties/task-job-pass-b/profile.json

@@ -0,0 +1,6 @@
+{
+  "name": "task-job-pass-b",
+  "action": "task-job-pass-b",
+  "executable": "task-job-pass-b",
+  "describe": "Pass task job test B."
+}

package/dist/duties/task-jobs/duty.md

@@ -0,0 +1,3 @@
+# Task Jobs
+
+Drain the next pending planned task job and return until the plan is complete.

package/dist/duties/task-jobs/profile.json

@@ -0,0 +1,6 @@
+{
+  "name": "task-jobs",
+  "action": "task-jobs",
+  "executable": "task-jobs",
+  "describe": "Run planned task jobs."
+}

package/dist/executables/types.ts

@@ -416,11 +416,11 @@ export interface Context {
      * `@kody <next>` comment, which is silently ignored when Kody comments as
      * a GitHub App (bot author), stalling the pipeline at classify.
      */
-    nextDispatch?: { executable: string; cliArgs: Record<string, unknown> }
+    nextDispatch?: { action?: string; duty?: string; executable?: string; cliArgs: Record<string, unknown> }
     /** In-process hand-off to a full Job, preserving job identity in task state. */
     nextJob?: Job
     /** Where to return after nextJob succeeds. Used by task-jobs to keep draining pending work. */
-    afterNextJob?: { executable: string; cliArgs: Record<string, unknown> }
+    afterNextJob?: { action?: string; duty?: string; executable?: string; cliArgs: Record<string, unknown> }
   }
   /**
    * If a preflight script sets this to true, the executor skips the agent
@@ -452,17 +452,15 @@ export type AnyScript = PreflightScript | PostflightScript
 // Job — the unified work request (task-state jobs collect run attempts).
 //
 // A Job is the required work the engine tries to execute, regardless of how it
-// was triggered. It REFERENCES the reusable nouns — `executable` (how),
-// `persona` (who), `duty` (why, by slug) — and OWNS its `schedule` (when).
+// was triggered. It must reference a duty/action (why). The executable is only
+// the duty-selected implementation detail (how), never a standalone request.
 // Task state stores this durable job separately from individual run attempts.
 // Two flavors:
 //   - "instant"   — run once now (an `@kody <verb>` comment or a manual dispatch)
 //   - "scheduled" — fired on `schedule` (cron) by the tick path
 //
-// Fields are optional-heavy on purpose: a comment-minted instant job carries
-// `executable` + inline `why`; a cron-minted scheduled job carries `duty` +
-// `schedule` + `persona`. `runJob` (src/job.ts) lowers a Job onto the existing
-// executor and seeds both stable job metadata and per-run metadata.
+// `runJob` (src/job.ts) lowers a Job onto the private executor after resolving
+// the duty, and seeds both stable job metadata and per-run metadata.
 // ────────────────────────────────────────────────────────────────────────────
 
 export type JobFlavor = "instant" | "scheduled"
@@ -470,8 +468,7 @@ export type JobFlavor = "instant" | "scheduled"
 export interface Job {
   /** Public action the user/operator invoked. Mirrors the duty action. */
   action?: string
-  /** How: executable (profile) name to run. 0–1; omitted when intent is
-   *  agent-only with no specific verb. */
+  /** How: implementation profile selected by the duty. Not valid by itself. */
   executable?: string
   /** Why (referenced): a duty slug whose intent drives the run. */
   duty?: string

package/package.json

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