@kody-ade/kody-engine 0.4.5 → 0.4.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/bin/kody.js
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
// package.json
|
|
4
4
|
var package_default = {
|
|
5
5
|
name: "@kody-ade/kody-engine",
|
|
6
|
-
version: "0.4.
|
|
6
|
+
version: "0.4.7",
|
|
7
7
|
description: "kody \u2014 autonomous development engine. Single-session Claude Code agent behind a generic executor + declarative executable profiles.",
|
|
8
8
|
license: "MIT",
|
|
9
9
|
type: "module",
|
|
@@ -26,7 +26,7 @@ If a prior-art block is present above, scan it before editing — those are earl
|
|
|
26
26
|
# Required steps
|
|
27
27
|
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.
|
|
28
28
|
2. **Number each item** internally (Item 1, Item 2, …). You will account for every one of them in your final message below.
|
|
29
|
-
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 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.
|
|
29
|
+
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.
|
|
30
30
|
|
|
31
31
|
**Research floor (MUST be met before any Edit/Write):**
|
|
32
32
|
- Read the **full** contents of every file you intend to change.
|
|
@@ -143,7 +143,11 @@ fi
|
|
|
143
143
|
|
|
144
144
|
echo "[goal-tick] dispatching @kody on task #$next_issue"
|
|
145
145
|
gh issue comment "$next_issue" --body "@kody"
|
|
146
|
-
|
|
146
|
+
# Ensure the dedup label exists in the repo. It lives outside the `kody:`
|
|
147
|
+
# namespace so `ensureLabels` doesn't create it at init time, and a missing
|
|
148
|
+
# label silently swallowed here would re-dispatch the same issue every tick.
|
|
149
|
+
gh label create "$dispatched_label" --color ededed --description "kody goal-runner: already dispatched this tick" --force >/dev/null 2>&1 || true
|
|
150
|
+
gh issue edit "$next_issue" --add-label "$dispatched_label"
|
|
147
151
|
|
|
148
152
|
# Bump updatedAt so the file changes (cheap audit trail in git log).
|
|
149
153
|
python3 - "$state_file" "$next_issue" <<'PY'
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@kody-ade/kody-engine",
|
|
3
|
-
"version": "0.4.
|
|
3
|
+
"version": "0.4.7",
|
|
4
4
|
"description": "kody — autonomous development engine. Single-session Claude Code agent behind a generic executor + declarative executable profiles.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"type": "module",
|