@kody-ade/kody-engine 0.2.41 → 0.2.43

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/kody2.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.2.41",
6
+ version: "0.2.43",
7
7
  description: "kody2 \u2014 autonomous development engine. Single-session Claude Code agent behind a generic executor + declarative executable profiles.",
8
8
  license: "MIT",
9
9
  type: "module",
@@ -32,9 +32,15 @@ PR_SUMMARY:
32
32
  One paragraph restating what the issue is asking for, in your own words.
33
33
 
34
34
  ## Repo context
35
- Files, modules, and existing patterns most relevant to the request. Use
36
- `path/to/file.ts` references. Note anything that constrains the solution
37
- space (existing abstractions, invariants from AGENTS.md / CLAUDE.md).
35
+ **Issue-specific only.** Surface whatever you actually discover during your
36
+ read-only exploration files, modules, or existing patterns the implementer
37
+ would have to find by hand for *this* issue. Use real `path/to/file` references
38
+ from the repo (no placeholders or invented paths).
39
+
40
+ Do NOT restate general architecture, tech stack, or conventions already
41
+ documented in `AGENTS.md` / `CLAUDE.md` — reference those files by path
42
+ ("see AGENTS.md") and move on. If a constraint lives in one of those files,
43
+ cite it; don't copy it.
38
44
 
39
45
  ## Clarifying questions
40
46
  Numbered list. Each question must include a one-line "Why:" explaining why
@@ -53,6 +59,29 @@ Do NOT include a "Next steps" / "Recommendation" / "How to proceed" section —
53
59
  research stops at findings.>
54
60
  ```
55
61
 
62
+ # Delta mode — if a prior research comment exists
63
+
64
+ Before writing your findings, scan the "Recent comments" block above for a
65
+ previous comment whose body starts with `## Research for issue`. If one
66
+ exists, you are in **delta mode**:
67
+
68
+ - Treat its Clarifying questions as the open set, not a blank slate.
69
+ - For each prior question, check whether later comments (user replies or
70
+ other output) have answered it. If answered, fold the answer into
71
+ Understood request / Repo context / Proposed scope as appropriate and
72
+ drop the question.
73
+ - Keep questions that are still open. Add new questions only if the latest
74
+ comments exposed genuinely new gaps.
75
+ - Prepend a `## Delta since last research` section at the TOP of
76
+ PR_SUMMARY (before Understood request) with short bullets:
77
+ `**Answered:** …`, `**Still open:** …`, `**New:** …`.
78
+ - For any section whose content has NOT changed, write
79
+ `(unchanged — see prior research)` in place of the body. Do not re-derive
80
+ what's already established.
81
+
82
+ If no prior `## Research for issue` comment exists in the thread, produce
83
+ the full first-pass structure (no Delta section, all sections written out).
84
+
56
85
  # Rules
57
86
  - Read-only. Do NOT modify any file.
58
87
  - Do NOT run git or gh commands.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@kody-ade/kody-engine",
3
- "version": "0.2.41",
3
+ "version": "0.2.43",
4
4
  "description": "kody2 — autonomous development engine. Single-session Claude Code agent behind a generic executor + declarative executable profiles.",
5
5
  "license": "MIT",
6
6
  "type": "module",