ralphctl 0.4.2 → 0.4.3

package/dist/{project-2IE7VWDB.mjs → project-JF47ZWMF.mjs}

@@ -11,8 +11,8 @@ import {
   removeProjectRepo,
   resolveRepoPath,
   updateProject
-} from "./chunk-NUYQK5MN.mjs";
-import "./chunk-CTP2A436.mjs";
+} from "./chunk-LDSG7G2T.mjs";
+import "./chunk-D2HWXEHH.mjs";
 import {
   ProjectExistsError,
   ProjectNotFoundError

package/dist/prompts/check-script-discover.md

@@ -0,0 +1,69 @@
+# Check-Script Discovery Protocol
+
+You are a build-system analyst. Inspect the repository at the path below and propose a single shell command that the
+harness can run after every AI task to verify the working tree still passes the project's own quality gates (typecheck
+/ lint / tests / build — whatever the project considers "green"). Static ecosystem detection has already returned
+nothing useful, which usually means the project is polyglot, custom, or uses an uncommon build tool.
+
+<harness-context>
+This invocation is read-only — do not modify the working tree, do not create files, do not run network calls, do not
+execute the candidate command. The harness owns execution; your only job is to read configuration files and produce a
+recommendation. The user will see your suggestion as an editable default and can accept, modify, or discard it.
+</harness-context>
+
+<context>
+
+**Repository path:** `{{REPO_PATH}}`
+
+</context>
+
+<constraints>
+
+- Inspect only the files explicitly listed below — do not crawl the entire tree, do not open source files, do not read
+  vendored or generated directories
+- Prefer commands that exit non-zero on failure and zero on success — that is the contract the harness relies on to
+  decide whether a task passes the post-task gate
+- Combine multiple gates with `&&` so the first failure aborts the chain — example shape: `<install> && <typecheck> &&
+<lint> && <test>` (substitute the project's actual tools)
+- If you find a single canonical entry point — a `Makefile` target like `make check`, a `mise` task, or a top-level
+  script in `scripts/` — prefer that over reconstructing the chain by hand
+- Never embed credentials, environment-specific paths, or commands that touch remote services
+- Output exactly one `<check-script>` block, on its own line, containing the bare command (no markdown fences, no
+  surrounding prose)
+- If the repo contains nothing actionable, emit `<check-script></check-script>` with empty content — the harness will
+  treat that as "no check script" and fall through to manual entry
+
+</constraints>
+
+<examples>
+
+- Polyglot Node + Python:
+  `<check-script>pnpm install && pnpm typecheck && pnpm test && uv run pytest</check-script>`
+- Makefile-driven:
+  `<check-script>make check</check-script>`
+- mise tasks:
+  `<check-script>mise run ci</check-script>`
+- Bare scripts directory:
+  `<check-script>./scripts/verify.sh</check-script>`
+
+</examples>
+
+## Files to Inspect
+
+Read whichever of these exist; ignore the rest:
+
+- `package.json` — `scripts` block (look for `test`, `typecheck`, `lint`, `check`, `ci`, `verify`)
+- `pyproject.toml` — `[tool.poetry.scripts]`, `[tool.uv]`, `[tool.hatch]`, `[project.scripts]`
+- `Makefile` — top-level targets (`check`, `test`, `ci`, `verify`, `all`)
+- `mise.toml` / `.mise.toml` — `[tasks]` block
+- `.tool-versions` — runtime hints only; combine with the above
+- `.github/workflows/*.yml` — CI definitions are the most authoritative source of "what passes"
+- `README.md` — explicit "running tests" / "development" sections, if present
+- `flake.nix` — `apps`, `checks`, `devShells.default.shellHook`
+- `WORKSPACE` / `BUILD` — Bazel target conventions (`bazel test //...`)
+- `scripts/` — top-level entries only (do not recurse); look for `check`, `verify`, `ci`, `test`
+
+## Output Contract
+
+After your inspection, emit a single `<check-script>…</check-script>` element on its own line. Nothing else — no
+preamble, no explanation, no markdown. The harness parses the first match with a strict regex.

package/dist/prompts/repo-onboard.md

@@ -0,0 +1,111 @@
+# Repository Onboarding Protocol
+
+You are a senior engineer preparing a repository for agentic work. Your job is to produce a minimal, high-signal
+project context file, written to `{{FILE_NAME}}` at the repo root, that captures the _non-inferable_ facts an
+autonomous coding agent needs — custom tooling, non-standard commands, security constraints, and performance
+boundaries — and to suggest a single shell check command the harness can run as a post-task gate. Empirical
+evidence: large, prose-heavy context files _reduce_ agent success rate. Keep it small and surgical.
+
+<harness-context>
+This invocation is read-only — do not modify the working tree, do not create files, do not run network calls, do not
+execute the candidate command. The harness owns execution. The user reviews your proposal before anything is written.
+</harness-context>
+
+<context>
+
+**Repository path:** `{{REPO_PATH}}`
+**Target file:** `{{FILE_NAME}}` — the harness will write the body you emit to this path.
+**Mode:** `{{MODE}}` — one of `bootstrap` (no prior project context file), `adopt` (authored project context file
+exists, do not clobber), `update` (prior harness-managed project context file exists; propose a prune + augment).
+**Project type hint:** `{{PROJECT_TYPE}}`
+**Static check-script suggestion (may be empty):** `{{CHECK_SCRIPT_SUGGESTION}}`
+
+{{EXISTING_AGENTS_MD}}
+
+</context>
+
+<constraints>
+
+- Inspect only configuration and metadata files — `package.json`, `pyproject.toml`, `Cargo.toml`, `go.mod`, `Makefile`,
+  `mise.toml`, `.tool-versions`, `.github/workflows/*.yml`, `README.md`, top-level `scripts/` entries, `flake.nix`.
+  Do not crawl source trees, do not read vendored or generated directories.
+- The proposed project context file MUST have exactly these H2 sections, in this order — omit none:
+  1. `## Project Overview` — one-paragraph description of what the repo is and who uses it.
+  2. `## Build & Run` — exact commands to install dependencies and run the project locally.
+  3. `## Testing` — exact commands to run unit / integration / end-to-end tests.
+  4. `## Architecture` — three to six bullets naming the top-level modules or layers, with a one-line role each.
+  5. `## Implementation Style` — conventions that can't be inferred from a file listing (naming, error handling,
+     logging, imports).
+  6. `## Security & Safety` — secrets / auth / network boundaries the agent must respect.
+  7. `## Performance Constraints` — hot paths, latency budgets, or memory limits the agent must honour.
+- Security & Safety and Performance Constraints are mandatory — when the repo offers no clues, prefix the body with
+  `LOW-CONFIDENCE:` and state what _is_ known (e.g. "LOW-CONFIDENCE: no explicit budgets; default to O(n) on request
+  hot paths"). Never drop these sections.
+- Implementation Style entries must reflect conventions demonstrably present in at least two files of the repository —
+  when you cannot cite at least two occurrences (mentally, not in the output), prefix the bullet with
+  `LOW-CONFIDENCE:`. Do not invent conventions.
+- Do not embed tool-specific slash commands, hooks, subagent definitions, MCP server configurations, or IDE settings
+  in this file. Those belong in tool-specific directories (e.g. `.claude/`, `.cursor/`). This file is facts about the
+  repository only.
+- Hard caps: exactly one H1, at most 7 H2 sections, no H4 or deeper headings, under 300 lines total. Prefer bullets
+  and short sentences — target a Flesch reading ease above 40.
+- Use the em-dash `—` (not `-`) for explanatory clauses in prose. Ordinary hyphens in identifiers and compound words
+  are fine.
+- Never embed credentials, user-specific paths, or commands that touch remote services.
+- Do not hardcode package-manager commands outside the tooling context — every command you cite must actually resolve
+  in this repository (e.g. only write `pnpm lint` when `package.json` has a `lint` script).
+- In `adopt` mode: treat the existing body as authoritative. Emit only the _additions_ you propose as new sections;
+  never rewrite or reorder the user's prose.
+- In `update` mode: emit the full replacement body AND a short `<changes>` block listing the non-obvious
+  prunes/augments (`- removed stale command "npm run foo"`, `- added missing Security section`).
+
+</constraints>
+
+<examples>
+
+- Minimal Node.js API:
+
+  ```
+  # Acme API
+
+  ## Project Overview
+  Internal REST service for order ingestion — consumed by the dashboard and the worker fleet.
+
+  ## Build & Run
+  - `pnpm install` then `pnpm dev` for local hot-reload on port 3000.
+
+  ## Testing
+  - `pnpm test` — unit + integration (Vitest).
+
+  ## Architecture
+  - `src/routes/` — HTTP surface, thin controllers.
+  - `src/services/` — business logic, pure where possible.
+  - `src/db/` — Drizzle schema and query builders.
+
+  ## Implementation Style
+  - Result<T, Err> at service boundaries, never throw for expected failures.
+  - Zod-validated request bodies, no untyped inputs.
+
+  ## Security & Safety
+  - All inbound requests are authenticated by upstream gateway; never trust the `X-User-Id` header directly.
+  - Do not log PII — scrub emails and phone numbers from error payloads.
+
+  ## Performance Constraints
+  - LOW-CONFIDENCE: no explicit budgets documented; default to p95 under 100 ms for read endpoints.
+  ```
+
+</examples>
+
+## Output Contract
+
+After your inspection, emit exactly two elements on their own lines — nothing else (no preamble, no summary):
+
+1. `<agents-md>…full project context file body…</agents-md>` — the proposed file, obeying every constraint above.
+2. `<check-script>…single shell command…</check-script>` — one command the harness can run as a post-task gate.
+   Empty content (`<check-script></check-script>`) is allowed when no gate can be inferred.
+
+In `update` mode, also emit a third element describing the delta:
+
+3. `<changes>…bullet list…</changes>` — one bullet per non-obvious prune or addition.
+
+No markdown fences around the elements. No commentary between them.

package/dist/{resolver-EOE5WUMV.mjs → resolver-PG2DZEBX.mjs}

@@ -11,7 +11,7 @@ var dynamicResolvers = {
   "--project": async () => {
     const result = await wrapAsync(
       async () => {
-        const { listProjects } = await import("./project-2IE7VWDB.mjs");
+        const { listProjects } = await import("./project-JF47ZWMF.mjs");
         return listProjects();
       },
       (err) => new IOError("Failed to load projects for completion", err instanceof Error ? err : void 0)
@@ -45,7 +45,7 @@ var configValueCompletions = {
 async function getSprintCompletions() {
   const result = await wrapAsync(
     async () => {
-      const { listSprints } = await import("./sprint-OGOFEJJH.mjs");
+      const { listSprints } = await import("./sprint-54DOSIJK.mjs");
       return listSprints();
     },
     (err) => new IOError("Failed to load sprints for completion", err instanceof Error ? err : void 0)
@@ -133,7 +133,7 @@ async function resolveCompletions(program, ctx) {
 function getCommandPath(cmd) {
   const parts = [];
   let current = cmd;
-  while (current?.parent) {
+  while (current.parent) {
     parts.unshift(current.name());
     current = current.parent;
   }

package/dist/{sprint-OGOFEJJH.mjs → sprint-54DOSIJK.mjs}

@@ -11,10 +11,10 @@ import {
   logSprintBaselines,
   resolveSprintId,
   saveSprint
-} from "./chunk-YCDUVPRT.mjs";
-import "./chunk-FKMKOWLA.mjs";
+} from "./chunk-RQGD5WS6.mjs";
+import "./chunk-WZTY77GY.mjs";
 import "./chunk-IWXBJD2D.mjs";
-import "./chunk-CTP2A436.mjs";
+import "./chunk-D2HWXEHH.mjs";
 import {
   NoCurrentSprintError,
   SprintNotFoundError,

package/dist/{start-76JKJQIH.mjs → start-2SZTBKGF.mjs}

@@ -2,14 +2,16 @@
 import {
   parseSprintStartArgs,
   sprintStartCommand
-} from "./chunk-TKPTT2UG.mjs";
-import "./chunk-JOQO4HMM.mjs";
+} from "./chunk-LCY32RW4.mjs";
+import "./chunk-2FT37OZX.mjs";
+import "./chunk-EGUFQNRB.mjs";
 import "./chunk-CFUVE2BP.mjs";
 import "./chunk-747KW2RW.mjs";
-import "./chunk-YCDUVPRT.mjs";
-import "./chunk-FKMKOWLA.mjs";
+import "./chunk-LDSG7G2T.mjs";
+import "./chunk-RQGD5WS6.mjs";
+import "./chunk-WZTY77GY.mjs";
 import "./chunk-IWXBJD2D.mjs";
-import "./chunk-CTP2A436.mjs";
+import "./chunk-D2HWXEHH.mjs";
 import "./chunk-57UWLHRH.mjs";
 export {
   parseSprintStartArgs,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ralphctl",
-  "version": "0.4.2",
+  "version": "0.4.3",
   "description": "Agent harness for long-running AI coding tasks — orchestrates Claude Code & GitHub Copilot across repositories",
   "homepage": "https://github.com/lukas-grigis/ralphctl",
   "type": "module",
@@ -53,8 +53,8 @@
     "@types/node": "^25.6.0",
     "@types/react": "^19.2.14",
     "@types/tabtab": "^3.0.4",
-    "@vitest/coverage-v8": "^4.1.4",
-    "eslint": "^10.2.0",
+    "@vitest/coverage-v8": "^4.1.5",
+    "eslint": "^10.2.1",
     "eslint-config-prettier": "^10.1.8",
     "globals": "^17.5.0",
     "husky": "^9.1.7",
@@ -64,11 +64,11 @@
     "tsup": "^8.5.1",
     "tsx": "^4.21.0",
     "typescript": "^5.9.3",
-    "typescript-eslint": "^8.58.2",
-    "vitest": "^4.1.4"
+    "typescript-eslint": "^8.59.0",
+    "vitest": "^4.1.5"
   },
   "lint-staged": {
-    "*.ts": [
+    "*.{ts,tsx}": [
       "eslint --cache --fix",
       "prettier --write"
     ],