@kody-ade/kody-engine 0.4.224 → 0.4.225

package/dist/executables/resolve/profile.json

@@ -1,107 +0,0 @@
-{
-  "name": "resolve",
-  "role": "primitive",
-  "describe": "Resolve merge conflicts between a PR branch and the default branch.",
-  "inputs": [
-    {
-      "name": "pr",
-      "flag": "--pr",
-      "type": "int",
-      "required": true,
-      "describe": "GitHub PR number whose branch has conflicts with the default branch."
-    },
-    {
-      "name": "prefer",
-      "flag": "--prefer",
-      "type": "enum",
-      "values": ["ours", "theirs"],
-      "required": false,
-      "describe": "Force one side for every conflict: 'ours' = PR branch (HEAD), 'theirs' = base branch. Omit to let the agent merge by judgement."
-    }
-  ],
-  "claudeCode": {
-    "model": "inherit",
-    "permissionMode": "acceptEdits",
-    "maxTurns": null,
-    "systemPromptAppend": null,
-    "tools": [
-      "Read",
-      "Write",
-      "Edit",
-      "Bash",
-      "Grep",
-      "Glob"
-    ],
-    "hooks": ["block-git"],
-    "skills": [],
-    "commands": [],
-    "subagents": [],
-    "plugins": [],
-    "mcpServers": []
-  },
-  "cliTools": [],
-  "scripts": {
-    "preflight": [
-      {
-        "script": "setLifecycleLabel",
-        "with": {
-          "label": "kody:resolving",
-          "color": "b60205",
-          "description": "kody: resolving merge conflicts"
-        }
-      },
-      {
-        "script": "resolveFlow"
-      },
-      {
-        "shell": "apply-prefer.sh",
-        "runWhen": { "args.prefer": ["ours", "theirs"] }
-      },
-      {
-        "script": "loadTaskState"
-      },
-      {
-        "script": "loadConventions"
-      },
-      {
-        "script": "loadMemoryContext"
-      },
-      {
-        "script": "loadCoverageRules"
-      },
-      {
-        "script": "composePrompt"
-      }
-    ],
-    "postflight": [
-      {
-        "script": "parseAgentResult"
-      },
-      {
-        "script": "stageMergeConflicts"
-      },
-      {
-        "script": "commitAndPush"
-      },
-      {
-        "script": "ensurePr"
-      },
-      {
-        "script": "postIssueComment"
-      },
-      {
-        "script": "writeRunSummary"
-      },
-      {
-        "script": "saveTaskState"
-      }
-    ]
-  },
-  "output": {
-    "actionTypes": [
-      "RESOLVE_COMPLETED",
-      "RESOLVE_FAILED",
-      "AGENT_NOT_RUN"
-    ]
-  }
-}

package/dist/executables/resolve/prompt.md

@@ -1,51 +0,0 @@
-You are Kody, an autonomous engineer. A `git merge origin/{{baseBranch}}` into PR #{{pr.number}} (`{{branch}}`) produced conflicts. Resolve them. The wrapper handles git/gh — you do not.
-
-# Repo
-- {{repoOwner}}/{{repoName}}
-
-# PR #{{pr.number}}: {{pr.title}}
-
-# Conflicted files
-
-{{conflictedFiles}}
-
-{{preferBlock}}{{conventionsBlock}}{{memoryContext}}{{toolsUsage}}# Working-tree conflict markers (truncated)
-
-{{conflictMarkersPreview}}
-
-# Required steps
-1. For each conflicted file: read it, understand both sides of the `<<<<<<<` / `=======` / `>>>>>>>` markers, and produce the correct merged content. Remove all conflict markers.
-2. If a conflict resolution directive is given above, follow it exactly — take the specified side for every conflict, no judgement. Otherwise, preserve the PR's intent (the HEAD side) unless `origin/{{baseBranch}}` made a change that should be preserved (e.g. security fix, renamed API), and use judgement.
-3. **Asymmetric conflicts.** Symmetric conflicts (both sides modified the same lines) are easy: merge the content. Asymmetric ones are harder — apply this decision tree:
-
-   - **One side deletes, the other modifies.** Read commit messages and surrounding code on both sides.
-     - If base deletes (file/function removed) and HEAD modifies → likely the PR was written against an older revision; **prefer deletion**, then check whether HEAD's modification still has a home elsewhere (it may have moved). If the modification was a refactor, deletion wins.
-     - If base modifies and HEAD deletes (PR removed something that base improved) → **prefer deletion** unless the base modification was a security/correctness fix the PR depends on.
-     - If you cannot determine intent from the code, emit `FAILED: cannot resolve asymmetric conflict in <file> — <one-line description>` and stop. Do NOT guess.
-
-   - **Both sides add (parallel additions of the same name/symbol).** Keep both if they are genuinely different (e.g. two new functions with similar names that do different things — rename one). Keep one if they are duplicates of the same intent.
-
-4. **Generated files.** Do NOT manually merge generated artifacts:
-   - Lockfiles (`package-lock.json`, `pnpm-lock.yaml`, `yarn.lock`, `bun.lockb`, `Cargo.lock`, `go.sum`, `poetry.lock`, `Pipfile.lock`).
-   - Test snapshots (`__snapshots__/*.snap`, `*.snap`, Playwright snapshots).
-   - Build outputs (anything under `dist/`, `build/`, `.next/`, `out/`).
-   - Schema dumps (`prisma/schema.prisma` migrations directory, generated GraphQL schemas).
-
-   For these, take the conflicted file from base (`origin/{{baseBranch}}`), then re-run the generator (`pnpm install`, `pnpm test -u` *only with confirmation that the snapshot diff is intentional*, `pnpm prisma generate`, etc.). If you cannot determine the right generator command from the repo, emit `FAILED: generated-file conflict in <file> — needs manual regeneration` and stop.
-
-5. After resolving, run the quality commands with Bash and fix any issues YOUR resolution introduced.
-6. Final message format (or `FAILED: <reason>` on failure):
-
-   ```
-   DONE
-   COMMIT_MSG: fix: resolve merge conflicts with {{baseBranch}}
-   PR_SUMMARY:
-   <2-4 bullets: which files had conflicts, how you resolved each, any judgement calls>
-   ```
-
-# Rules
-- Do NOT run git/gh. Wrapper handles the merge commit.
-- Do NOT delete files to "resolve" conflicts. Merge the content.
-- Do NOT leave any `<<<<<<<`, `=======`, or `>>>>>>>` markers in files.
-- Stay on `{{branch}}`.
-{{systemPromptAppend}}

package/dist/executables/revert/profile.json

@@ -1,82 +0,0 @@
-{
-  "name": "revert",
-  "role": "primitive",
-  "describe": "Revert one or more commits on an existing PR branch via `git revert`. No agent — fully mechanical.",
-  "inputs": [
-    {
-      "name": "pr",
-      "flag": "--pr",
-      "type": "int",
-      "required": true,
-      "describe": "GitHub PR number whose branch to revert commits on."
-    },
-    {
-      "name": "shas",
-      "flag": "--shas",
-      "type": "string",
-      "required": true,
-      "bindsCommentRest": true,
-      "describe": "One or more commit SHAs (whitespace-separated) to revert. Each must exist in the PR branch's history."
-    }
-  ],
-  "claudeCode": {
-    "model": "inherit",
-    "permissionMode": "acceptEdits",
-    "maxTurns": 0,
-    "maxThinkingTokens": null,
-    "systemPromptAppend": null,
-    "tools": [],
-    "hooks": [],
-    "skills": [],
-    "commands": [],
-    "subagents": [],
-    "plugins": [],
-    "mcpServers": []
-  },
-  "cliTools": [
-    {
-      "name": "git",
-      "install": { "required": true, "checkCommand": "git --version" },
-      "verify": "git --version",
-      "usage": "Used by revert.sh to stage `git revert --no-commit` and by commitAndPush to land the revert.",
-      "allowedUses": ["revert", "rev-parse", "merge-base", "log", "commit", "push", "rev-list"]
-    },
-    {
-      "name": "gh",
-      "install": { "required": true, "checkCommand": "gh --version" },
-      "verify": "gh --version",
-      "usage": "Used by revertFlow to read PR metadata and post status / failure comments.",
-      "allowedUses": ["pr", "api", "issue"]
-    }
-  ],
-  "scripts": {
-    "preflight": [
-      {
-        "script": "setLifecycleLabel",
-        "with": {
-          "label": "kody:reverting",
-          "color": "cccccc",
-          "description": "kody: reverting commits"
-        }
-      },
-      { "script": "revertFlow" },
-      { "script": "loadTaskState" },
-      { "shell": "revert.sh" }
-    ],
-    "postflight": [
-      { "script": "markFlowSuccess" },
-      { "script": "commitAndPush" },
-      { "script": "ensurePr" },
-      { "script": "postIssueComment" },
-      { "script": "recordOutcome" },
-      { "script": "saveTaskState" },
-      { "script": "writeRunSummary" }
-    ]
-  },
-  "output": {
-    "actionTypes": [
-      "REVERT_COMPLETED",
-      "REVERT_FAILED"
-    ]
-  }
-}

package/dist/executables/revert/revert.sh

@@ -1,33 +0,0 @@
-#!/usr/bin/env bash
-#
-# revert: stage `git revert` of one or more commits on the PR branch.
-#
-# Runs as a preflight shell entry after revertFlow has validated inputs and
-# checked out the branch. revertFlow:
-#   - Resolved every requested SHA to its full form and re-set
-#     ctx.args.shas to a whitespace-separated list (we read it via
-#     KODY_ARG_SHAS).
-#   - Set ctx.skipAgent=true and ctx.data.commitMessage already, so the
-#     agent never runs and commitAndPush will use that message.
-#
-# This script does only the staging — `--no-commit` so commitAndPush
-# (postflight) makes the actual commit. That keeps kody's invariant
-# intact (only commitAndPush commits) and means the message comes from
-# revertFlow, not from git's auto-generated revert subject.
-#
-# Exits:
-#   0   — staged successfully
-#   1+  — git revert failed (executor surfaces stderr; postflight bails)
-
-set -euo pipefail
-
-shas="${KODY_ARG_SHAS:-}"
-if [[ -z "$shas" ]]; then
-  echo "revert.sh: KODY_ARG_SHAS is empty (revertFlow should have set it)" >&2
-  exit 64
-fi
-
-# shellcheck disable=SC2086 # Intentional word-splitting on whitespace-separated SHAs.
-git revert --no-commit --no-edit $shas
-
-echo "revert.sh: staged revert of: $shas"

package/dist/executables/sync/profile.json

@@ -1,48 +0,0 @@
-{
-  "name": "sync",
-  "role": "primitive",
-  "describe": "Merge the default (base) branch into a PR branch and push. No agent.",
-  "inputs": [
-    {
-      "name": "pr",
-      "flag": "--pr",
-      "type": "int",
-      "required": true,
-      "describe": "GitHub PR number to update from its base branch."
-    }
-  ],
-  "claudeCode": {
-    "model": "inherit",
-    "permissionMode": "acceptEdits",
-    "maxTurns": null,
-    "systemPromptAppend": null,
-    "tools": [],
-    "hooks": [],
-    "skills": [],
-    "commands": [],
-    "subagents": [],
-    "plugins": [],
-    "mcpServers": []
-  },
-  "cliTools": [],
-  "scripts": {
-    "preflight": [
-      {
-        "script": "setLifecycleLabel",
-        "with": {
-          "label": "kody:syncing",
-          "color": "c5def5",
-          "description": "kody: syncing PR with base"
-        }
-      },
-      {
-        "script": "syncFlow",
-        "with": { "announceOnSuccess": true }
-      },
-      {
-        "script": "skipAgent"
-      }
-    ],
-    "postflight": []
-  }
-}

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

@@ -1,44 +0,0 @@
-{
-  "name": "task-job-fail-once",
-  "role": "utility",
-  "describe": "Live-test executable that fails the first planned job attempt and succeeds on rerun.",
-  "kind": "oneshot",
-  "inputs": [
-    {
-      "name": "issue",
-      "flag": "--issue",
-      "type": "int",
-      "required": true,
-      "describe": "GitHub issue number that owns the task state."
-    }
-  ],
-  "claudeCode": {
-    "model": "inherit",
-    "permissionMode": "default",
-    "maxTurns": 0,
-    "maxThinkingTokens": null,
-    "systemPromptAppend": null,
-    "tools": [],
-    "hooks": [],
-    "skills": [],
-    "commands": [],
-    "subagents": [],
-    "plugins": [],
-    "mcpServers": []
-  },
-  "cliTools": [],
-  "inputArtifacts": [],
-  "outputArtifacts": [],
-  "scripts": {
-    "preflight": [
-      { "script": "loadIssueContext" },
-      { "script": "loadTaskState" },
-      { "script": "skipAgent" }
-    ],
-    "postflight": [
-      { "script": "failOnceTaskJob" },
-      { "script": "recordOutcome" },
-      { "script": "saveTaskState" }
-    ]
-  }
-}

package/dist/executables/task-job-fail-once/prompt.md

@@ -1 +0,0 @@
-This executable is script-only.

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

@@ -1,43 +0,0 @@
-{
-  "name": "task-job-pass-a",
-  "role": "utility",
-  "describe": "Live-test executable that deterministically succeeds as planned task slice A.",
-  "kind": "oneshot",
-  "inputs": [
-    {
-      "name": "issue",
-      "flag": "--issue",
-      "type": "int",
-      "required": true,
-      "describe": "GitHub issue number that owns the task state."
-    }
-  ],
-  "claudeCode": {
-    "model": "inherit",
-    "permissionMode": "default",
-    "maxTurns": 0,
-    "maxThinkingTokens": null,
-    "systemPromptAppend": null,
-    "tools": [],
-    "hooks": [],
-    "skills": [],
-    "commands": [],
-    "subagents": [],
-    "plugins": [],
-    "mcpServers": []
-  },
-  "cliTools": [],
-  "inputArtifacts": [],
-  "outputArtifacts": [],
-  "scripts": {
-    "preflight": [
-      { "script": "loadIssueContext" },
-      { "script": "loadTaskState" },
-      { "script": "skipAgent" }
-    ],
-    "postflight": [
-      { "script": "recordOutcome" },
-      { "script": "saveTaskState" }
-    ]
-  }
-}

package/dist/executables/task-job-pass-a/prompt.md

@@ -1 +0,0 @@
-This executable is script-only.

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

@@ -1,43 +0,0 @@
-{
-  "name": "task-job-pass-b",
-  "role": "utility",
-  "describe": "Live-test executable that deterministically succeeds as planned task slice B.",
-  "kind": "oneshot",
-  "inputs": [
-    {
-      "name": "issue",
-      "flag": "--issue",
-      "type": "int",
-      "required": true,
-      "describe": "GitHub issue number that owns the task state."
-    }
-  ],
-  "claudeCode": {
-    "model": "inherit",
-    "permissionMode": "default",
-    "maxTurns": 0,
-    "maxThinkingTokens": null,
-    "systemPromptAppend": null,
-    "tools": [],
-    "hooks": [],
-    "skills": [],
-    "commands": [],
-    "subagents": [],
-    "plugins": [],
-    "mcpServers": []
-  },
-  "cliTools": [],
-  "inputArtifacts": [],
-  "outputArtifacts": [],
-  "scripts": {
-    "preflight": [
-      { "script": "loadIssueContext" },
-      { "script": "loadTaskState" },
-      { "script": "skipAgent" }
-    ],
-    "postflight": [
-      { "script": "recordOutcome" },
-      { "script": "saveTaskState" }
-    ]
-  }
-}

package/dist/executables/task-job-pass-b/prompt.md

@@ -1 +0,0 @@
-This executable is script-only.

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

@@ -1,41 +0,0 @@
-{
-  "name": "task-jobs",
-  "role": "utility",
-  "describe": "Runs the next pending executable from a hidden task job plan on an issue.",
-  "inputs": [
-    {
-      "name": "issue",
-      "flag": "--issue",
-      "type": "int",
-      "required": true,
-      "describe": "GitHub issue number that carries the task job plan."
-    }
-  ],
-  "claudeCode": {
-    "model": "inherit",
-    "permissionMode": "default",
-    "maxTurns": 0,
-    "maxThinkingTokens": null,
-    "systemPromptAppend": null,
-    "tools": [],
-    "hooks": [],
-    "skills": [],
-    "commands": [],
-    "subagents": [],
-    "plugins": [],
-    "mcpServers": []
-  },
-  "cliTools": [],
-  "inputArtifacts": [],
-  "outputArtifacts": [],
-  "scripts": {
-    "preflight": [
-      { "script": "loadIssueContext" },
-      { "script": "loadTaskState" },
-      { "script": "planTaskJobs" },
-      { "script": "dispatchNextTaskJob" },
-      { "script": "skipAgent" }
-    ],
-    "postflight": []
-  }
-}

package/dist/executables/task-jobs/prompt.md

@@ -1 +0,0 @@
-This executable is script-only.

package/dist/executables/worker-ask/profile.json

@@ -1,70 +0,0 @@
-{
-  "name": "worker-ask",
-  "role": "primitive",
-  "describe": "Ad-hoc one-shot: run a staff persona against an inline message + context (from a dashboard @staff mention). Stateless — no duty folder, no state, no commit. Replies into the originating thread.",
-  "kind": "oneshot",
-  "inputs": [
-    {
-      "name": "worker",
-      "flag": "--worker",
-      "type": "string",
-      "required": true,
-      "describe": "Staff slug — basename (without .md) of the persona file under .kody/staff/."
-    },
-    {
-      "name": "thread",
-      "flag": "--thread",
-      "type": "string",
-      "describe": "Where to post the reply: `discussion:<n>` (or a bare number) for a Discussion, or `issue:<n>` for an issue/PR. When set, the worker answers as a comment on that thread."
-    },
-    {
-      "name": "message",
-      "flag": "--message",
-      "type": "string",
-      "bindsCommentRest": true,
-      "describe": "Fallback inline message when no triggering comment body is available (CLI/testing). In production the message is read verbatim from the dispatching comment body."
-    }
-  ],
-  "claudeCode": {
-    "model": "inherit",
-    "permissionMode": "default",
-    "maxTurns": 20,
-    "maxThinkingTokens": null,
-    "systemPromptAppend": null,
-    "tools": ["Bash", "Read"],
-    "hooks": [],
-    "skills": [],
-    "commands": [],
-    "subagents": [],
-    "plugins": [],
-    "mcpServers": []
-  },
-  "cliTools": [
-    {
-      "name": "gh",
-      "install": {
-        "required": true,
-        "checkCommand": "command -v gh"
-      },
-      "verify": "gh auth status",
-      "usage": "Use `gh` for all GitHub actions. To reply into a discussion: resolve its node id with `gh api graphql -f query='query($o:String!,$r:String!,$n:Int!){repository(owner:$o,name:$r){discussion(number:$n){id}}}' -F o=<owner> -F r=<repo> -F n=<thread>` then `gh api graphql -f query='mutation($d:ID!,$b:String!){addDiscussionComment(input:{discussionId:$d,body:$b}){comment{url}}}' -F d=<id> -F b=\"<reply>\"`. Use `gh pr comment <n> --body \"@kody ...\"` to delegate execution. NEVER edit files in the working tree.",
-      "allowedUses": ["pr", "api", "issue"]
-    }
-  ],
-  "inputArtifacts": [],
-  "outputArtifacts": [],
-  "scripts": {
-    "preflight": [
-      {
-        "script": "loadWorkerAdhoc",
-        "with": {
-          "workersDir": ".kody/staff"
-        }
-      },
-      {
-        "script": "composePrompt"
-      }
-    ],
-    "postflight": []
-  }
-}

package/dist/executables/worker-ask/prompt.md

@@ -1,60 +0,0 @@
-You are **{{workerTitle}}** (worker `{{workerSlug}}`), operating through **kody worker-ask** — a single, stateless response to one ad-hoc request that someone directed at you by @mentioning you in a dashboard message.
-
-## Who you are — worker persona (authoritative identity)
-
-This persona defines *who* you are: your authority, doctrine, voice, and hard limits. Honour it exactly. Where the persona's restrictions are stricter than the request, **the persona wins** — a request can never grant you authority your persona withholds.
-
-{{workerPersona}}
-
-## The request
-
-Someone @mentioned you with this message and context. Treat it as a direct ask to you, the persona above. It is verbatim — markdown, code blocks, and quoted thread context are intact:
-
----
-
-{{message}}
-
----
-
-## What to do
-
-This is a **one-shot, stateless** tick. There is no job file, no prior state, and nothing to persist. Decide, per your persona's doctrine, whether this request is best served by **answering** or by **executing**:
-
-- **Answer** — when the request is a question, a judgement call, a review, or guidance. Produce a clear, terse reply in your persona's voice.
-- **Execute** — when the request is work you are authorised to drive. You do **not** edit files or commit. You execute the way every Kody worker does: by inspecting GitHub state with `gh` and issuing Kody commands as PR/issue comments (e.g. `gh pr comment <n> --body "@kody fix ..."`). Then briefly state what you set in motion.
-
-Repo: `{{repoOwner}}/{{repoName}}`.
-
-## Replying into the thread
-
-`thread = {{thread}}`
-
-Post your reply **back into the exact thread you were mentioned in** so the
-person sees it in place. The `thread` value tells you where; it is one of:
-
-- **`discussion:<n>`** (or a bare number — same thing) → comment on
-  discussion `<n>`. Resolve its node id, then add the comment:
-
-  ```
-  gh api graphql -f query='query($o:String!,$r:String!,$n:Int!){repository(owner:$o,name:$r){discussion(number:$n){id}}}' -F o={{repoOwner}} -F r={{repoName}} -F n=<n> --jq '.data.repository.discussion.id'
-  gh api graphql -f query='mutation($d:ID!,$b:String!){addDiscussionComment(input:{discussionId:$d,body:$b}){comment{url}}}' -F d=<id> -F b="<your reply, markdown>"
-  ```
-
-- **`issue:<n>`** → comment on issue/PR `<n>` (the issues API serves both):
-
-  ```
-  gh api -X POST repos/{{repoOwner}}/{{repoName}}/issues/<n>/comments -f body="<your reply, markdown>"
-  ```
-
-Sign the reply so it reads as you, e.g. lead with `**{{workerTitle}}** —`.
-
-If `thread` is empty, just produce your reply as your final response (no
-GitHub post).
-
-## Rules
-
-- Never edit, create, or delete files in the working tree. Never `git commit`/`push`.
-- The only shell tool is `gh`. Everything goes through it.
-- Stay inside your persona's authority and restrictions at all times.
-- Be terse. One focused reply; do not spawn duplicate work.
-- There is **no state output contract** — do not emit a state fenced block. When you have replied (or posted to the thread), you are done.