Files
ryaneggzandClaude Opus 4.7 ddbf2d504a task: remove dead config.example.json seed template
config.example.json was the tracked seed for the gitignored config.json,
but the base ships zero compose overlays and every reader (Makefile,
install.sh, banner.sh) tolerates a missing config.json via jq fallbacks.
Remove the file and its now-dead seeding block in install.sh.

Closes #323

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-21 01:38:42 +00:00
..
2026-05-03 18:48:25 -06:00

scripts/

Orchestrator scripts that run on the host, not inside the sandbox. Provisioning, Ralph execution, and the cron runtime live here.

File Purpose
install.sh Curl-piped installer — bootstraps a fresh harness checkout
ralph.sh Ralph loop runner: scripts/ralph.sh [--harness=…] <taskdesc>
cron-runtime.ts Croner runtime — scans crons/*.md, schedules, fires each job
__tests__/ Vitest unit tests (vitest.config.ts at repo root targets this)

Conventions

  • Bash scripts use set -euo pipefail and an ERR trap so silent exits surface as ERROR: lines (see install.sh header for the pattern).
  • TypeScript scripts are run via tsx from the root package.json scripts; tests run via pnpm test.
  • Scripts here are orchestrator-scope only. Anything an in-sandbox agent needs lives under workspace/ or install/. Per CLAUDE.md, application code does not belong in scripts/.

Adding a script

  1. Drop it in scripts/ with a one-line purpose comment in its header.
  2. Add a row to the table above.
  3. If it's TypeScript, add a unit test under scripts/__tests__/.
  4. If it's a long-running entry point, wire a pnpm script in the root package.json rather than expecting users to invoke it directly.