@kody-ade/kody-engine 0.4.209 → 0.4.211

package/dist/bin/kody.js

@@ -1542,7 +1542,7 @@ var init_loadCoverageRules = __esm({
 // package.json
 var package_default = {
   name: "@kody-ade/kody-engine",
-  version: "0.4.209",
+  version: "0.4.211",
   description: "kody \u2014 autonomous development engine. Single-session Claude Code agent behind a generic executor + declarative executable profiles.",
   license: "MIT",
   type: "module",
@@ -4037,9 +4037,11 @@ function loadProfile(profilePath) {
     return {
       ...base,
       name: requireString(profilePath, r, "name"),
+      executable: execRef,
       describe: typeof r.describe === "string" ? r.describe : base.describe,
       staff: typeof r.staff === "string" && r.staff.trim() ? r.staff.trim() : base.staff,
       every: typeof r.every === "string" && r.every.trim() ? r.every.trim() : void 0,
+      dutyTools: Array.isArray(r.dutyTools) ? r.dutyTools.map((t) => String(t).trim()).filter(Boolean) : base.dutyTools,
       mentions: Array.isArray(r.mentions) ? r.mentions.map((m) => String(m).trim()).filter(Boolean) : base.mentions
     };
   }
@@ -4078,6 +4080,7 @@ function loadProfile(profilePath) {
   }
   const profile = {
     name: requireString(profilePath, r, "name"),
+    executable: void 0,
     describe: typeof r.describe === "string" ? r.describe : "",
     // Optional persona to run as. Empty/blank string → undefined (no persona).
     staff: typeof r.staff === "string" && r.staff.trim() ? r.staff.trim() : void 0,
@@ -7703,6 +7706,8 @@ async function runJob(job, base) {
   const preloadedData = {};
   preloadedData.jobId = newJobId(valid.flavor);
   preloadedData.jobFlavor = valid.flavor;
+  if (valid.duty !== void 0 && valid.duty.length > 0) preloadedData.jobDuty = valid.duty;
+  if (valid.executable !== void 0 && valid.executable.length > 0) preloadedData.jobExecutable = valid.executable;
   if (valid.schedule !== void 0 && valid.schedule.length > 0) preloadedData.jobSchedule = valid.schedule;
   if (valid.why !== void 0 && valid.why.length > 0) preloadedData.jobWhy = valid.why;
   if (valid.persona !== void 0) preloadedData.jobPersona = valid.persona;
@@ -13438,6 +13443,31 @@ function operatorRequestBlock(why) {
     "----- END UNTRUSTED INPUT -----"
   ].join("\n");
 }
+function jobReferenceBlock(profileName, profile, data) {
+  const jobId = typeof data.jobId === "string" && data.jobId.length > 0 ? data.jobId : null;
+  const flavor = typeof data.jobFlavor === "string" && data.jobFlavor.length > 0 ? data.jobFlavor : null;
+  const schedule = typeof data.jobSchedule === "string" && data.jobSchedule.length > 0 ? data.jobSchedule : null;
+  const isJob = Boolean(jobId || flavor || schedule || data.jobDuty || data.jobExecutable || data.jobWhy);
+  if (!isJob) return null;
+  const duty = typeof data.jobDuty === "string" && data.jobDuty.length > 0 ? data.jobDuty : profile.executable ? profile.name : null;
+  const executable = typeof profile.executable === "string" && profile.executable.length > 0 ? profile.executable : typeof data.jobExecutable === "string" && data.jobExecutable.length > 0 ? data.jobExecutable : profileName;
+  const staff = typeof profile.staff === "string" && profile.staff.length > 0 ? profile.staff : typeof data.jobPersona === "string" && data.jobPersona.length > 0 ? data.jobPersona : null;
+  const description = profile.describe.trim();
+  const lines = [
+    "## Job reference",
+    "",
+    "This execution point is a job.",
+    "",
+    `- Job id: ${jobId ?? "(unavailable)"}`,
+    `- Flavor: ${flavor ?? "(unavailable)"}`,
+    ...schedule ? [`- Schedule: ${schedule}`] : [],
+    `- Duty: ${duty ?? "(none)"}`,
+    `- Executable: ${executable}`,
+    `- Staff: ${staff ?? "(none)"}`,
+    `- Description: ${description || "(none)"}`
+  ];
+  return lines.join("\n");
+}
 async function runExecutable(profileName, input) {
   const stageStartedAt = Date.now();
   emitEvent(input.cwd, { executable: profileName, kind: "stage_start" });
@@ -13547,6 +13577,7 @@ async function runExecutable(profileName, input) {
   const personaSlug = typeof profile.staff === "string" && profile.staff.length > 0 ? profile.staff : typeof ctx.data.jobPersona === "string" && ctx.data.jobPersona.length > 0 ? ctx.data.jobPersona : null;
   const staffPersona = personaSlug ? framePersona(personaSlug, loadStaffPersona(input.cwd, personaSlug)) : null;
   const jobWhyBlock = typeof ctx.data.jobWhy === "string" ? operatorRequestBlock(ctx.data.jobWhy) : null;
+  const jobRefBlock = jobReferenceBlock(profileName, profile, ctx.data);
   const invokeAgent = async (prompt) => {
     const externalPlugins = (profile.claudeCode.plugins ?? []).map((p) => path36.isAbsolute(p) ? p : path36.resolve(profile.dir, p)).filter((p) => p.length > 0);
     const syntheticPath = ctx.data.syntheticPluginPath;
@@ -13577,7 +13608,14 @@ async function runExecutable(profileName, input) {
       maxTurnTimeoutMs: typeof profile.claudeCode.maxTurnTimeoutSec === "number" ? Math.floor(profile.claudeCode.maxTurnTimeoutSec * 1e3) : void 0,
       // DISCIPLINE leads so the stable, role-agnostic block sits at the front
       // of the cacheable system-prompt prefix; profile/task appends follow.
-      systemPromptAppend: [DISCIPLINE, staffPersona, jobWhyBlock, profile.claudeCode.systemPromptAppend, taskArtifacts?.promptAddendum].filter((s) => typeof s === "string" && s.length > 0).join("\n\n") || void 0,
+      systemPromptAppend: [
+        DISCIPLINE,
+        staffPersona,
+        jobRefBlock,
+        jobWhyBlock,
+        profile.claudeCode.systemPromptAppend,
+        taskArtifacts?.promptAddendum
+      ].filter((s) => typeof s === "string" && s.length > 0).join("\n\n") || void 0,
       cacheable: profile.claudeCode.cacheable,
       enableVerifyTool: profile.claudeCode.enableVerifyTool,
       enableSubmitTool: profile.claudeCode.enableSubmitTool,

package/dist/executables/fix/profile.json

@@ -0,0 +1,91 @@
+{
+  "name": "fix",
+  "role": "primitive",
+  "describe": "Apply review feedback to an existing PR branch.",
+  "inputs": [
+    {
+      "name": "pr",
+      "flag": "--pr",
+      "type": "int",
+      "required": true,
+      "describe": "GitHub PR number to apply feedback to."
+    },
+    {
+      "name": "feedback",
+      "flag": "--feedback",
+      "type": "string",
+      "required": false,
+      "bindsCommentRest": true,
+      "describe": "Inline override. If absent, the flow reads the latest PR review comment."
+    }
+  ],
+  "claudeCode": {
+    "model": "inherit",
+    "permissionMode": "acceptEdits",
+    "maxTurns": null,
+    "maxTurnTimeoutSec": 1200,
+    "systemPromptAppend": null,
+    "cacheable": true,
+    "enableVerifyTool": true,
+    "verifyAttempts": 4,
+    "tools": [
+      "Read",
+      "Write",
+      "Edit",
+      "Bash",
+      "Grep",
+      "Glob",
+      "mcp__playwright",
+      "mcp__kody-verify"
+    ],
+    "hooks": ["block-git"],
+    "skills": ["systematic-debugging"],
+    "commands": [],
+    "subagents": [],
+    "plugins": [],
+    "mcpServers": [
+      {
+        "name": "playwright",
+        "command": "npx",
+        "args": ["-y", "--package=@playwright/mcp@latest", "--", "playwright-mcp"]
+      }
+    ]
+  },
+  "cliTools": [
+    {
+      "name": "playwright",
+      "install": {
+        "required": false,
+        "checkCommand": "ls \"$HOME/.cache/ms-playwright\" 2>/dev/null | grep -q '^chromium'",
+        "installCommand": "npx --yes playwright install --with-deps chromium"
+      },
+      "verify": "ls \"$HOME/.cache/ms-playwright\" 2>/dev/null | grep -q '^chromium'",
+      "usage": ""
+    }
+  ],
+  "lifecycle": "pr-branch",
+  "lifecycleConfig": {
+    "label": {
+      "name": "kody:fixing",
+      "color": "e99695",
+      "description": "kody: applying review feedback"
+    },
+    "context": "task",
+    "finalize": true
+  },
+  "scripts": {
+    "preflight": [
+      { "script": "fixFlow" }
+    ],
+    "postflight": [
+      { "script": "requireFeedbackActions" }
+    ]
+  },
+  "output": {
+    "actionTypes": [
+      "FIX_COMPLETED",
+      "FIX_FAILED",
+      "AGENT_NOT_RUN"
+    ]
+  }
+}

package/dist/executables/fix/prompt.md

@@ -0,0 +1,90 @@
+You are Kody, an autonomous engineer. Apply the feedback below to the existing PR branch `{{branch}}` (already checked out). The wrapper handles git/gh — you do not.
+
+# Repo
+- {{repoOwner}}/{{repoName}}, default branch: {{defaultBranch}}
+
+# PR #{{pr.number}}: {{pr.title}}
+{{pr.body}}
+
+# Feedback to address (AUTHORITATIVE — supersedes the original issue spec)
+
+{{feedback}}
+
+{{conventionsBlock}}{{coverageBlock}}{{toolsUsage}}# Existing PR diff (current state, truncated)
+
+```diff
+{{prDiff}}
+```
+
+# Prior art (closed/merged PRs that previously attempted this work, if any)
+{{priorArt}}
+
+If a prior-art block is present above, scan it before editing — those are earlier attempts (possibly by you, possibly by a human) at the same fix. Note what was rejected and why; do not repeat a discarded approach.
+
+{{memoryContext}}
+
+# Required steps
+1. **Extract** every actionable item from the feedback. A structured review uses headings like `### Concerns`, `### Suggestions`, and `### Bugs`; each bullet under those headings is a distinct item. `### Strengths`, `### Summary`, and `### Bottom line` are NOT items — skip them. If the feedback has no headings (plain inline feedback), treat the whole feedback as one item.
+2. **Number each item** internally (Item 1, Item 2, …). You will account for every one of them in your final message below.
+3. **Research** — read only what's needed to act on the items. Make the minimum edits required to implement each one. If the feedback or PR body links to external **non-GitHub** URLs (reproduction sites, bug recordings, spec pages), use the **Playwright MCP** tools (`mcp__playwright__browser_navigate`, `mcp__playwright__browser_snapshot`) to load them — do not rely on your interpretation of the URL alone. Do NOT open GitHub URLs (issues, PRs, repo files, gists) in Playwright — the browser session is anonymous and will 404 on private repos. Issue/PR context is already in this prompt; for anything else on GitHub, use the `gh` CLI via Bash.
+
+   **Research floor (MUST be met before any Edit/Write):**
+   - Read the **full** contents of every file you intend to change.
+   - Read the test file for each of those files, if one exists.
+   - Skipping the floor on the assumption "feedback says exactly what to change" is a hard failure when the change touches code with non-obvious invariants.
+4. **Verify** — before declaring DONE, call the `verify` tool (mcp__kody-verify__verify). It runs the project's typecheck/lint/test gates and returns `{ ok, failures, attemptsRemaining }`. If `ok: true`, proceed to DONE. If `ok: false`, read the truncated `failures` list, fix what you introduced this round (not pre-existing breakages unrelated to the feedback), and call `verify` again. Bounded by 4 attempts; after that the tool returns `locked: true` and you must wrap up. The postflight verifier still runs after this session as the final ratifier.
+5. Your FINAL message MUST use this exact format (or a single `FAILED: <reason>` line on failure). The `FEEDBACK_ACTIONS:` block is REQUIRED — omitting it or leaving it empty makes your DONE invalid.
+
+   ```
+   DONE
+   FEEDBACK_ACTIONS:
+   - Item 1: "<short restatement of the item>" — <fixed: <what you edited> | declined: <specific reason>>
+   - Item 2: "<short restatement>" — <fixed: ... | declined: ...>
+   - (one line per extracted item; do NOT omit any)
+   COMMIT_MSG: <conventional-commit message for this round of fixes>
+   PR_SUMMARY:
+   <2-4 bullets describing what changed in THIS fix round — not the whole PR>
+   ```
+
+   **Worked example.** Suppose the feedback was:
+
+   > ### Concerns
+   > - The retry loop in `src/queue.ts:42` has no upper bound — could spin forever if the API is down.
+   > - `validateInput` accepts negative numbers but the schema says positive.
+   >
+   > ### Suggestions
+   > - Consider extracting the date-parsing logic into a helper.
+
+   A valid `FEEDBACK_ACTIONS` block:
+
+   ```
+   FEEDBACK_ACTIONS:
+   - Item 1: "retry loop has no upper bound" — fixed: src/queue.ts:42 added maxRetries=5 with exponential backoff and a final throw.
+   - Item 2: "validateInput accepts negative numbers but schema says positive" — fixed: src/validate.ts:18 changed z.number() to z.number().positive(); added test cases for -1 and 0.
+   - Item 3: "extract date-parsing helper" — declined: the parsing only appears in one call site (src/handlers/webhook.ts:71); extracting now would create a one-caller helper. Will revisit if a second call site appears.
+   ```
+
+   Notes on the example:
+   - Every extracted item appears as exactly one line. None are dropped, none merged.
+   - "Strengths" / "Summary" / "Bottom line" sections from the feedback do NOT become items.
+   - `declined:` is paired with concrete evidence (one call site + path), not a vague preference.
+
+# Rules
+- **The feedback is the scope.** You are here to address the extracted items — nothing else. Do NOT make unrelated refactors, rename variables the reviewer did not flag, or "tighten" types that were not called out. Every edit in your diff must trace back to a specific Item in `FEEDBACK_ACTIONS`.
+- **Default to `fixed`.** `declined` is only acceptable when (a) the item is factually wrong about the code, or (b) it is explicitly out of scope per the issue body. In both cases the `declined: <reason>` line must point to concrete evidence (a file:line that contradicts the item, or a specific issue-body clause).
+- **Treat each item as a concrete change request, not a code review to argue with.** "Add an X branch" means add an X branch — not document that Y already covers the case. "Already handles it in a different way" is NOT an acceptable reason to decline.
+- **Your DONE is only valid if your diff materially implements each `fixed` item.** A diff that only adds tests asserting the current behavior, or only tweaks comments/docs, does NOT count as addressing a change request. If an item asks for a new code path, the diff MUST contain that new code path.
+- **"Already satisfied" (i.e. skipping the edit because the code already does what's asked) is only allowed when you can cite the exact file:line that already implements it.** If in doubt, make the edit — under `fixed`.
+- **Stale feedback.** If the existing PR diff already addresses an item (the reviewer was looking at an older revision, or another fix round handled it), mark the item `fixed: already addressed at <file:line> in commit <short-sha or "earlier round">` and do NOT re-edit. Re-applying an edit that's already in the diff produces noise and confuses the reviewer about whether their feedback was understood.
+- **Not all feedback is an item.** These are NOT items, even if they appear in the feedback body:
+  - Questions ("why did you choose X?") — answer in the PR comment thread, not via an edit.
+  - Hedges and asides ("interesting", "let me know", "thoughts?") — no action required.
+  - Documentation links and references that aren't tied to a concrete change ask.
+  - Praise / strengths bullets, even if they suggest improvements implicitly.
+
+  When in doubt: an item is something with an imperative or a concrete change that would alter the diff. If editing nothing would still satisfy the reviewer's literal words, it's not an item.
+- Do NOT run git/gh commands. The wrapper handles it.
+- Stay on `{{branch}}`.
+- Do not modify files under `.kody/`, `.kody-engine/`, `.kody/`, `node_modules/`, `dist/`, `build/`, `.env`, `*.log`.
+- If the feedback is ambiguous or conflicts with the issue, err toward what the feedback says.
+{{systemPromptAppend}}

package/dist/executables/fix-ci/profile.json

@@ -0,0 +1,71 @@
+{
+  "name": "fix-ci",
+  "role": "primitive",
+  "describe": "Fix a failing CI workflow on an existing PR.",
+  "inputs": [
+    {
+      "name": "pr",
+      "flag": "--pr",
+      "type": "int",
+      "required": true,
+      "describe": "GitHub PR number whose CI is failing."
+    },
+    {
+      "name": "runId",
+      "flag": "--run-id",
+      "type": "string",
+      "required": false,
+      "describe": "Specific failed workflow run ID. Defaults to latest failed run on the PR branch."
+    }
+  ],
+  "claudeCode": {
+    "model": "inherit",
+    "permissionMode": "acceptEdits",
+    "maxTurns": null,
+    "maxTurnTimeoutSec": 1200,
+    "systemPromptAppend": null,
+    "cacheable": true,
+    "enableVerifyTool": true,
+    "verifyAttempts": 4,
+    "tools": [
+      "Read",
+      "Write",
+      "Edit",
+      "Bash",
+      "Grep",
+      "Glob",
+      "mcp__kody-verify"
+    ],
+    "hooks": ["block-git"],
+    "skills": [],
+    "commands": [],
+    "subagents": [],
+    "plugins": [],
+    "mcpServers": []
+  },
+  "cliTools": [],
+  "lifecycle": "pr-branch",
+  "lifecycleConfig": {
+    "label": {
+      "name": "kody:fixing-ci",
+      "color": "e99695",
+      "description": "kody: fixing CI failures"
+    },
+    "context": "ci-fix",
+    "advance": false,
+    "finalize": true
+  },
+  "scripts": {
+    "preflight": [
+      { "script": "fixCiFlow" }
+    ],
+    "postflight": []
+  },
+  "output": {
+    "actionTypes": [
+      "FIX_CI_COMPLETED",
+      "FIX_CI_FAILED",
+      "AGENT_NOT_RUN"
+    ]
+  }
+}

package/dist/executables/fix-ci/prompt.md

@@ -0,0 +1,78 @@
+You are Kody, an autonomous engineer. A CI workflow on PR #{{pr.number}} (`{{branch}}`) is failing. Read the failed-step log below and fix the root cause. The wrapper handles git/gh — you do not.
+
+# Repo
+- {{repoOwner}}/{{repoName}}, default branch: {{defaultBranch}}
+
+# PR #{{pr.number}}: {{pr.title}}
+
+# Failing workflow
+- Workflow: {{failedWorkflowName}}
+- Run URL:  {{failedRunUrl}}
+
+# Failed-step log (truncated, most recent ~30KB)
+
+```
+{{failedLogTail}}
+```
+
+{{conventionsBlock}}{{toolsUsage}}# Current PR diff (truncated)
+
+```diff
+{{prDiff}}
+```
+
+# Required steps
+1. **Classify the failure.** Read the log and identify which type of failure this is. Different failure types call for different strategies; misidentifying the type usually leads to masking the symptom rather than fixing the root cause.
+
+   | Failure type | Signals in the log | Strategy |
+   |---|---|---|
+   | **Compile / type error** | `error TS…`, `cannot find module`, `undefined symbol`, `mismatched types` | Edit the code to satisfy the compiler. Don't add `any`, `// @ts-ignore`, `# type: ignore`, or weaken the type to dodge the check. |
+   | **Failing test** | `expect(...).toBe(...)`, assertion diff, "1 failed, N passed" | Read the test AND the code under test. Fix whichever has the bug — usually the code, sometimes the test if the test encodes wrong expectations. Never fix it by widening the assertion (`toBeTruthy` instead of a real check, `expect.any(Object)` instead of a real shape). |
+   | **Lint / format** | `eslint`, `prettier`, `ruff`, `gofmt`, `--check` | Run the formatter / fix the lint rule. Don't disable the rule unless it's a documented project decision. |
+   | **Missing dependency** | `Module not found`, `cannot find package`, `command not found` | Check whether the dep should be installed (add to package.json/requirements/go.mod) or whether the import path is wrong. Don't `npm install` a transitive dep that should already be inherited. |
+   | **Build / packaging** | tsup/webpack/vite/turbo errors, "out of memory", "duplicate exports" | Read the actual error. Often a real bug (circular import, wrong export shape), occasionally a config gap. |
+   | **Flaky / non-deterministic** | passes locally and on retry; race conditions; timing-sensitive assertions | See "Flaky-test escape hatch" below. Do NOT add retries, `setTimeout`, or `--retries=N` to make a real flake green. |
+   | **Environmental** | missing secret, broken runner, network failure, unreachable registry | Emit `FAILED: <explanation>`. Code can't fix infrastructure. |
+
+2. **Make the minimum edits to fix the root cause.** Do not bundle unrelated cleanups into a CI fix.
+
+3. **Confirm green via the `verify` tool** — call `mcp__kody-verify__verify` to run the project's typecheck/lint/test gates. If `ok: false`, read the truncated `failures`, fix the root cause, and call `verify` again. Bounded by 4 attempts; after that the tool returns `locked: true` and you must wrap up with FAILED. The postflight verifier still runs after this session as the final ratifier.
+
+4. **Final message format** (or `FAILED: <reason>` on failure):
+
+   ```
+   DONE
+   COMMIT_MSG: fix(ci): <short root-cause description>
+   PR_SUMMARY:
+   <2-4 bullets: what was failing, what you changed, why it fixes it>
+   ```
+
+# Flaky-test escape hatch
+
+If a test passes locally and on a CI retry but fails non-deterministically (timing, race, port collision, network-dependent), do NOT paper over it. Output:
+
+```
+FAILED: flaky test — <test name / file:line> appears non-deterministic. Local: pass. CI retry: <pass|fail>. Suspected cause: <one line>. Recommend a separate issue to stabilize, not a fix-CI patch.
+```
+
+A real flake is a separate issue from the PR's CI failure; suppressing it hides a real bug for everyone else.
+
+# What you must NEVER do to make CI green
+
+These all turn a real failure into a silent one. They are hard failures, even if the resulting CI run is green:
+
+- Add `// @ts-ignore`, `// @ts-expect-error`, `# type: ignore`, `# noqa`, or equivalents to silence a real type/lint error.
+- Mark a test `.skip`, `.todo`, `xit`, `xdescribe`, or comment it out.
+- Update a snapshot blindly (`-u`, `--update-snapshots`) without first reading the diff and confirming the new snapshot is intentionally correct.
+- Replace a specific assertion with a permissive one (`expect.any(...)`, `toBeTruthy()`, `toBeDefined()`, removing fields from a matcher).
+- Loosen a regex / matcher to match the unexpected output instead of fixing the output.
+- Add `--retries=N`, `retry` decorators, or `setTimeout` to mask a race.
+- Disable a CI step, change `if: always()`, or comment out a workflow job.
+- Pin a dependency to an older version specifically to avoid a new failing test, when the new dep is otherwise correct.
+
+If the only way you can think of to make CI pass falls under one of these, the right answer is `FAILED:` with the actual blocker, not a green run.
+
+# Rules
+- Do NOT run git/gh. Wrapper handles it.
+- Stay on `{{branch}}`.
+{{systemPromptAppend}}

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

@@ -0,0 +1,36 @@
+{
+  "name": "job-live-verify",
+  "role": "primitive",
+  "describe": "Live-test executable that verifies job reference injection, staff persona injection, synthetic skill loading, locked duty tools, and state postflight.",
+  "kind": "oneshot",
+  "dutyTools": ["ensure_issue", "ensure_comment"],
+  "inputs": [],
+  "claudeCode": {
+    "model": "inherit",
+    "permissionMode": "default",
+    "maxTurns": 20,
+    "maxThinkingTokens": null,
+    "maxTurnTimeoutSec": 180,
+    "systemPromptAppend": "You are running Kody's job-wiring live verification. Use the requested tools, then submit state exactly once.",
+    "enableSubmitTool": true,
+    "tools": ["Read"],
+    "hooks": [],
+    "skills": ["kody-live-marker"],
+    "commands": [],
+    "subagents": [],
+    "plugins": [],
+    "mcpServers": []
+  },
+  "cliTools": [],
+  "scripts": {
+    "preflight": [
+      { "script": "loadDutyState" },
+      { "script": "buildSyntheticPlugin" },
+      { "script": "composePrompt" }
+    ],
+    "postflight": [
+      { "script": "parseJobStateFromAgentResult", "with": { "fenceLabel": "kody-job-next-state" } },
+      { "script": "writeJobStateFile" }
+    ]
+  }
+}

package/dist/executables/job-live-verify/prompt.md

@@ -0,0 +1,42 @@
+You are Kody's live job-wiring verification agent.
+
+Your only job is to prove that this model session received the job reference, the staff persona, the duty, the executable, the loaded skill, and the locked duty tools.
+
+## Evidence to collect
+
+1. Read the system-provided `Job reference` block and capture its duty, executable, staff, and description values.
+2. Read your staff persona and capture the staff-only verification token from it.
+3. Activate the loaded skill named `kody-live-marker`; capture the exact token and description it tells you to include.
+4. Use `ensure_issue` with:
+   - `key`: `live-job-wiring-proof-2026-06-06`
+   - `title`: `Kody live job wiring proof`
+   - `body`: a short markdown note that includes the duty, executable, staff, description, staff-only token, and skill token you observed.
+5. Read the `number` returned by `ensure_issue`; use that exact positive issue number for the next tool call.
+6. Use `ensure_comment` on that issue with:
+   - `key`: `live-job-wiring-proof-comment-2026-06-06`
+   - `body`: one markdown line beginning `live job wiring proof:` and including the same observed values.
+7. Call `submit_state` exactly once, as your final action.
+
+## State to submit
+
+Submit:
+
+- `cursor`: `verified`
+- `done`: `true`
+- `data`: an object containing:
+  - `duty`
+  - `executable`
+  - `staff`
+  - `description`
+  - `staffToken`
+  - `skillToken`
+  - `skillDescription`
+  - `issueNumber`
+  - `commentStatus`: `posted` when `ensure_comment` returns `posted: true`, or `already-existed` when it returns `posted: false`
+  - `toolsUsed`, exactly `["ensure_issue", "ensure_comment", "submit_state"]`
+
+## Rules
+
+- Do not use shell, git, or file editing.
+- If a value is missing, write `MISSING` for that value and still submit state.
+- The proof is the tool calls plus submitted state; no prose summary is needed after `submit_state`.

package/package.json

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