@kody-ade/kody-engine-lite 0.1.148 → 0.1.150

package/dist/bin/cli.js

@@ -5231,7 +5231,7 @@ function getDevServerInfo(taskDir) {
     command: ds.command,
     url: ds.url,
     readyPattern: ds.readyPattern ?? "Ready in|compiled|started server|Local:",
-    readyTimeout: ds.readyTimeout ?? 30
+    readyTimeout: ds.readyTimeout ?? 180
   };
 }
 function getBrowserToolGuidance(stageName, taskDir) {
@@ -5521,7 +5521,7 @@ async function waitForReady(url, timeoutSec, stdoutMatch) {
   return false;
 }
 async function startDevServer(opts) {
-  const timeout = opts.readyTimeout ?? 60;
+  const timeout = opts.readyTimeout ?? 180;
   const patternStr = opts.readyPattern ?? DEFAULT_READY_PATTERN;
   const pattern = new RegExp(patternStr, "i");
   const useStdoutDetection = Boolean(opts.readyPattern);
@@ -5665,7 +5665,7 @@ async function executeAgentStage(ctx, def) {
     devServerHandle = await startDevServer({
       command: ds.command,
       url: ds.url,
-      readyTimeout: ds.readyTimeout ?? 60,
+      readyTimeout: ds.readyTimeout ?? 180,
       readyPattern: ds.readyPattern ?? "Ready in|compiled|started server|Local:|localhost:",
       envVars
     });

package/kody.config.schema.json

@@ -262,7 +262,7 @@
             },
             "readyTimeout": {
               "type": "number",
-              "description": "Seconds to wait for the server to be ready. Default: 30"
+              "description": "Seconds to wait for the server to be ready. Default: 180"
             },
             "env": {
               "type": "array",
@@ -294,7 +294,7 @@
         },
         "readyTimeout": {
           "type": "number",
-          "description": "Seconds to wait for the server to be ready. Default: 30"
+          "description": "Seconds to wait for the server to be ready. Default: 180"
         },
         "env": {
           "type": "array",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kody-ade/kody-engine-lite",
-  "version": "0.1.148",
+  "version": "0.1.150",
   "description": "Autonomous SDLC pipeline: Kody orchestration + Claude Code + LiteLLM",
   "license": "MIT",
   "type": "module",

package/templates/kody.yml

@@ -181,6 +181,11 @@ jobs:
             echo "${DELIM}" >> $GITHUB_ENV
           done
 
+      - name: Warm up Next.js build cache
+        continue-on-error: true
+        run: npx next build 2>/dev/null || true
+        timeout-minutes: 15
+
       - name: Run Kody pipeline
         env:
           GH_TOKEN: ${{ steps.app-token.outputs.token || secrets.GITHUB_TOKEN }}

package/templates/watch-agents/branch-cleanup/agent.json

@@ -0,0 +1,7 @@
+{
+  "name": "branch-cleanup",
+  "description": "Finds stale remote branches with no recent activity and suggests cleanup",
+  "schedule": {
+    "every": 96
+  }
+}

package/templates/watch-agents/branch-cleanup/agent.md

@@ -0,0 +1,13 @@
+List remote branches and identify stale ones that should be cleaned up.
+
+1. Run `gh api repos/{{repo}}/branches --paginate --jq '.[] | {name: .name, protected: .protected}'` to get all branches.
+2. For each non-protected branch, check its last commit date using `gh api repos/{{repo}}/commits?sha=BRANCH_NAME&per_page=1 --jq '.[0].commit.committer.date'`.
+3. Flag any branch whose last commit is **older than 30 days**.
+4. Ignore these branches: `main`, `dev`, `staging`, `production`, and any branch starting with `release/`.
+5. Check if there is already an open issue with label `kody:watch:stale-branches` — if so, do NOT create a new one.
+6. If stale branches are found, create **one** GitHub issue:
+   - Title: `Branch cleanup: N stale branches older than 30 days`
+   - Label: `kody:watch:stale-branches`
+   - Body: a markdown table with columns: Branch Name, Last Commit Date, Days Stale. End with the command to delete them: `git push origin --delete branch-name`.
+
+If no stale branches are found, do not create an issue.

package/templates/watch-agents/readme-health/agent.json

@@ -0,0 +1,7 @@
+{
+  "name": "readme-health",
+  "description": "Checks if README.md exists and documents essential sections",
+  "schedule": {
+    "every": 96
+  }
+}

package/templates/watch-agents/readme-health/agent.md

@@ -0,0 +1,17 @@
+Check the repository's README.md for completeness and essential documentation.
+
+1. Read `README.md` from the repository root. If it does not exist, that is a critical finding.
+2. Check for the presence of these essential sections (look for headings or keywords):
+   - **Project description** — what the project does (first paragraph or a "## About" section)
+   - **Getting started / Installation** — how to install and set up
+   - **Usage / Running** — how to run the project (e.g. dev server, scripts)
+   - **Environment variables** — required env vars or reference to .env.example
+   - **Tech stack** — frameworks, languages, databases used
+3. Also read `package.json` to understand what scripts are available and cross-reference with the README.
+4. Check if there is already an open issue with label `kody:watch:readme-health` — if so, do NOT create a new one.
+5. If any essential sections are missing, create **one** GitHub issue:
+   - Title: `README health: N missing sections`
+   - Label: `kody:watch:readme-health`
+   - Body: list which sections are present (with a checkmark) and which are missing, with a brief suggestion for each missing section.
+
+If README is complete with all essential sections, do not create an issue.

package/templates/watch-agents/todo-scanner/agent.json

@@ -0,0 +1,7 @@
+{
+  "name": "todo-scanner",
+  "description": "Scans source code for TODO, FIXME, and HACK comments and creates tracking issues",
+  "schedule": {
+    "every": 48
+  }
+}

package/templates/watch-agents/todo-scanner/agent.md

@@ -0,0 +1,10 @@
+Scan the repository source code for TODO, FIXME, and HACK comments that indicate unfinished work or known issues.
+
+1. Use `grep -rn "TODO\|FIXME\|HACK\|XXX" src/ --include="*.ts" --include="*.tsx"` to find all markers.
+2. Group findings by type (TODO, FIXME, HACK).
+3. Check if there is already an open issue with label `kody:watch:todo-scan` — if so, do NOT create a new one.
+4. If no existing issue, create **one** GitHub issue summarizing all findings:
+   - Title: `Code health: N unresolved TODO/FIXME/HACK markers found`
+   - Label: `kody:watch:todo-scan`
+   - Body: a markdown table with columns: Type, File, Line, Comment text
+   - End with a brief recommendation to address high-priority items (FIXME, HACK) first.