@kody-ade/kody-engine 0.4.621 → 0.4.622

package/README.md

@@ -57,7 +57,9 @@ key. It's built to keep that blast radius small:
   downstream CI.
 - **Write allowlist.** The agent commits through `commitAndPush`, which blocks
   writes to engine runtime or configuration paths — it can't touch your
-  runtime state.
+  runtime state. See [Delivery boundary](docs/delivery-boundary.md) for what is
+  silently discarded, what fails visibly, and how an approved workflow file is
+  delivered.
 - **Locked-toolbox mode.** A job can declare `tools: [...]` to drop `Bash` and
   shell entirely, running only a fixed set of high-level intents.
 - **Review like any contributor.** kody opens PRs; you merge them.

package/dist/bin/kody.js

@@ -15,7 +15,7 @@ var init_package = __esm({
   "package.json"() {
     package_default = {
       name: "@kody-ade/kody-engine",
-      version: "0.4.621",
+      version: "0.4.622",
       description: "kody \u2014 autonomous development engine. Single-session Claude Code agent behind a generic executor + declarative implementation profiles.",
       license: "MIT",
       repository: {
@@ -29,6 +29,7 @@ var init_package = __esm({
       files: [
         "dist",
         "templates",
+        "docs/delivery-boundary.md",
         "kody.config.schema.json"
       ],
       scripts: {

package/docs/delivery-boundary.md

@@ -0,0 +1,29 @@
+# Delivery boundary
+
+Kody may inspect the whole checkout, but it does not commit every changed file.
+The postflight delivery step separates product work from runtime state and
+operator-owned configuration before creating the PR.
+
+## What happens to each kind of change
+
+| Change | Result |
+|---|---|
+| Normal source, test, or documentation file | Committed and pushed to the task branch |
+| Engine-generated cache or runtime state (`.kody-engine/`, `.kody-lean/`, `.codegraph/`, `node_modules/`, `dist/`, `build/`, logs) | Discarded from delivery without failing otherwise valid product work |
+| Protected operator or security configuration (`.github/*.yml`, `.env`, `kody.config.json`, legacy `.kody/` state) | Excluded from the commit and reported as a blocked delivery; the run fails visibly instead of claiming full completion |
+
+This distinction matters because definition hydration updates
+`.kody-engine/definitions/manifest.json` on normal runs. That file belongs to
+the Engine runtime; it is not work the agent attempted to deliver.
+
+## Delivering an approved protected file
+
+Do not weaken the global boundary. A capability that legitimately owns a
+GitHub workflow or a repository loop definition must declare the exact path in
+its delivery contract. The Engine validates that allowlist and only then stages
+the ignored file. Ordinary `run` work cannot opt itself into that permission.
+
+When a requested protected change is blocked, the issue status names the exact
+omitted path and the workflow exits nonzero. The PR can still contain the safe
+files that were successfully delivered; treat it as partial work until an
+approved owner supplies the protected file.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kody-ade/kody-engine",
-  "version": "0.4.621",
+  "version": "0.4.622",
   "description": "kody — autonomous development engine. Single-session Claude Code agent behind a generic executor + declarative implementation profiles.",
   "license": "MIT",
   "repository": {
@@ -14,6 +14,7 @@
   "files": [
     "dist",
     "templates",
+    "docs/delivery-boundary.md",
     "kody.config.schema.json"
   ],
   "scripts": {