@kody-ade/kody-engine 0.4.203 → 0.4.204-next.10

package/dist/executables/types.ts

@@ -17,6 +17,15 @@ import type { Phase } from "../state.js"
 
 export interface Profile {
   name: string
+  /**
+   * Optional staff member this executable runs *as*. When set, the executor
+   * loads `.kody/staff/<staff>.md` and injects that persona (authoritative
+   * identity) ahead of the executable's own system-prompt append. This is the
+   * unification hook: a "duty" is just an executable + a staff member. Absent →
+   * runs with no persona (unchanged legacy behaviour). A declared-but-missing
+   * staff file is fatal at run time (see src/staff.ts).
+   */
+  staff?: string
   describe: string
   /**
    * Semantic role — what this executable IS, not when it runs.
@@ -40,6 +49,28 @@ export interface Profile {
    * `schedule:`). Scheduled profiles must declare a `schedule` cron string.
    */
   kind: "oneshot" | "scheduled"
+  /**
+   * Recurrence cadence for a duty that runs on a timer (unified successor to a
+   * markdown duty's `every:` frontmatter). One of the ScheduleEvery values
+   * ("15m".."7d" | "manual"). Present → the duty-scheduler fires a one-shot run
+   * when due (no target). Absent → on-demand only (runs against an issue/PR).
+   * This is what makes "scheduled" just a field on the one duty shape.
+   */
+  every?: string
+  /**
+   * Locked-toolbox palette (unified successor to a markdown duty's `tools:`
+   * frontmatter). When non-empty, loadDutyState sets ctx.data.dutyTools so the
+   * executor spins up the in-process kody-duty MCP server and the agent runs
+   * MCP-only (Bash/Read revoked unless also in claudeCode.tools). Absent →
+   * normal SDK tools.
+   */
+  dutyTools?: string[]
+  /**
+   * GitHub logins (no leading `@`) this duty's output should mention. Rendered
+   * to `@a @b` and exposed to the prompt as {{mentions}} (and as the duty-MCP
+   * operator mention), mirroring a markdown duty's `mentions:` frontmatter.
+   */
+  mentions?: string[]
   /** Cron expression for scheduled profiles (e.g. "0 8 * * MON"). */
   schedule?: string
   /**
@@ -127,6 +158,14 @@ export interface Profile {
    * ENOENT even though profile.json (read here, earlier) loaded fine.
    */
   promptTemplates?: Record<string, string>
+  /**
+   * Subagent markdown captured (by declared name) at load time, BEFORE any
+   * task branch switch — same rationale as promptTemplates. loadSubagents
+   * prefers this snapshot so a duty's `agents/` surviving only on the default
+   * checkout (e.g. `.kody/duties/<slug>/agents/` absent on a PR branch) doesn't
+   * crash a PR-targeted duty. Populated by captureSubagentTemplates.
+   */
+  subagentTemplates?: Record<string, string>
 }
 
 /**

package/package.json

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