ralphctl 0.24.0 → 0.25.0

package/dist/cli.mjs

@@ -2,5 +2,7 @@
 
 // src/index.ts
 process.env.NODE_ENV ??= "production";
-var { runCli } = await import("./cli-FHPDHGP5.mjs");
+var { isColorDisabled } = await import("./use-no-color-NEMCAVY3.mjs");
+if (isColorDisabled()) process.env.FORCE_COLOR = "0";
+var { runCli } = await import("./cli-GQBXYNFN.mjs");
 await runCli(process.argv);

package/dist/manifest.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
-  "packageVersion": "0.24.0",
-  "generatedAt": "2026-09-30T06:53:55.509Z",
+  "packageVersion": "0.25.0",
+  "generatedAt": "2026-10-04T21:06:53.092Z",
   "assets": [
     "agent-definitions/ralphctl-evaluator.md",
     "agent-definitions/ralphctl-generator.md",
@@ -28,6 +28,7 @@
     "prompts/evaluate/template.md",
     "prompts/ideate/template.md",
     "prompts/implement-continuation/template.md",
+    "prompts/implement-crash-resume/template.md",
     "prompts/implement/template.md",
     "prompts/plan/template.md",
     "prompts/readiness/template.md",

package/dist/prompts/implement-crash-resume/template.md

@@ -0,0 +1,33 @@
+# Resume — Interrupted Attempt
+
+<role>
+You are the same AI coding agent, resuming the SAME task on a continued session. The tool that
+runs you was interrupted partway through your previous turn, so that turn may have stopped
+mid-step — files may be half-edited, a command may have been cut off, and the signals file may be
+missing or incomplete. The task brief and your earlier work are already in this conversation; this
+message does not repeat them.
+</role>
+
+<reconcile>
+Before changing anything, find out what is already done:
+
+- Run `git status` and `git diff` to see which files you already changed and how far each edit got.
+- When the signals file named in the output contract below already exists, read it to see what you
+  reported before the interruption.
+
+Treat what you remember as unverified until the working tree confirms it. Keep edits that are
+complete and correct, finish the ones that were cut off, and redo any that are broken. Do not
+revert or restart work that is already sound.
+</reconcile>
+
+Then continue the task to completion, exactly as you would have without the interruption. You are
+operating autonomously and the user cannot answer questions, so do the remaining work with tool
+calls instead of ending this turn on a plan. Re-run each `auto` criterion's command once the
+work is in place — or, when the task defines no `auto` criteria, run the verify script once — and emit `task-verified` with the bounded evidence, `commit-message` when any
+file was touched, and `task-complete` only once every criterion passes. When something is
+genuinely blocked, emit `task-blocked` with the concrete reason. Emit `change`, `decision`,
+`learning` and `note` as applicable. The no-test-weakening rule still applies — fix the
+implementation, not the test — except when a declared step explicitly changes the behaviour the
+test asserts.
+
+{{OUTPUT_CONTRACT_SECTION}}

package/dist/use-no-color-NEMCAVY3.mjs

@@ -0,0 +1,9 @@
+#!/usr/bin/env node
+import {
+  isColorDisabled,
+  useNoColor
+} from "./chunk-BAAV7AGY.mjs";
+export {
+  isColorDisabled,
+  useNoColor
+};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ralphctl",
-  "version": "0.24.0",
+  "version": "0.25.0",
   "description": "A ralph harness for long-running AI coding tasks — a generator-evaluator loop that drives Claude Code, GitHub Copilot CLI, OpenAI Codex CLI, OpenCode or Grok Build CLI across one or more repositories",
   "homepage": "https://github.com/lukas-grigis/ralphctl",
   "type": "module",