durable-jobslisted

# Durable Jobs Use `repowire jobs` when work needs durable lifecycle state, recovery after peer death, retry/cancel/result inspection, spawned-on-demand execution, or recurrence. Use `schedule` only for future ask/notify wakeups to an existing target. Agent folders are a convention, not a registry. Scaffold them with: ```bash repowire agents create <name> --backend <runtime> ``` Then create jobs targeting the folder's absolute path with `--path <abs-path> --backend <runtime>`. The folder's `AGENTS.md` is the source of truth; `CLAUDE.md` is only a shim for Claude Code. Other supported runtimes load `AGENTS.md` directly. `--result-surface` is metadata only until delivery routing exists. Do not claim jobs send Telegram, email, or dashboard notifications automatically. Workers must update job results explicitly. ## Daily email brief User intent: "Every morning, summarize important email and send me a brief." Route: ```bash repowire agents create daily-email-brief --backend codex repowire jobs create "Daily email brief" \ --path "$(pwd)/.repowire/agents/daily-email-brief" \ --backend codex \ --cron "0 8 * * *" \ --prompt "Prepare today's email brief. Use the job_id and attempt_id from this prompt when updating lifecycle state." \ --result-surface telegram ``` Put standing worker guidance in `.repowire/agents/daily-email-brief/AGENTS.md`: email tool expectations, privacy boundaries, what counts as important, and output format. Keep credentials outside the folder