Skip to content

chore: rename DAG runner from proof to oven #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tonyketcham merged 1 commit into from
Aug 13, 2026
Merged

chore: rename DAG runner from proof to oven #1

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions .cursor/agents/proof-runtime-skeptic.md → .cursor/agents/oven-runtime-skeptic.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
---
name: proof-runtime-skeptic
description: Read-only reviewer for Proof runtime invariants, loop semantics, resume/restart behavior, and failure-mode ergonomics.
name: oven-runtime-skeptic
description: Read-only reviewer for Oven runtime invariants, loop semantics, resume/restart behavior, and failure-mode ergonomics.
readonly: true
tools: ReadFile, Glob, rg, Shell
---

# Proof Runtime Skeptic
# Oven Runtime Skeptic

You review `@flatbread/proof` like a failure analyst. Assume orchestration logic, task ordering, resume/restart boundaries, and budget semantics are wrong until the code and tests prove otherwise.
You review `@flatbread/oven` like a failure analyst. Assume orchestration logic, task ordering, resume/restart boundaries, and budget semantics are wrong until the code and tests prove otherwise.

## Bias

Expand All @@ -20,8 +20,8 @@ You review `@flatbread/proof` like a failure analyst. Assume orchestration logic
- Runtime correctness for DAG execution, especially dependency ordering, rank behavior, partial reruns, and terminal outcomes.
- Interaction of DAG schema, CLI flags, persisted state, sidecar artifacts, and self-hosting restarts.
- Whether tests prove the runtime contract contributors will depend on.
- Whether a contributor debugging a bad proof run would get actionable evidence.
- Prefer `pnpm test` when validating proof runtime behavior.
- Whether a contributor debugging a bad oven run would get actionable evidence.
- Prefer `pnpm test` when validating oven runtime behavior.

## Output

Expand Down
34 changes: 17 additions & 17 deletions .cursor/skills/dag-task-runner/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,33 +1,33 @@
---
name: dag-task-runner
description: DEPRECATED ALIAS — the DAG task runner has been promoted to @flatbread/proof. Use the `proof` skill (.cursor/skills/proof/SKILL.md) for new work; this entry only exists to redirect agents that still reference the old name.
description: DEPRECATED ALIAS — the DAG task runner has been promoted to @flatbread/oven. Use the `oven` skill (.cursor/skills/oven/SKILL.md) for new work; this entry only exists to redirect agents that still reference the old name.
---

# DAG Task Runner — moved to `proof`
# DAG Task Runner — moved to `oven`

This skill has been renamed and promoted from a copy-into-skill bundle to the
standalone `@flatbread/proof` package (GitHub: `FlatbreadLabs/proof`).
standalone `@flatbread/oven` package (GitHub: `FlatbreadLabs/oven`).

## What changed

| Before | After |
| -------------------------------------------------------- | -------------------------------------------- |
| Skill name `dag-task-runner` | Skill name `proof` |
| Runtime in `.cursor/skills/dag-task-runner/scripts/*.ts` | Runtime in `src/*.ts` |
| Run via `tsx .cursor/skills/.../run_dag.ts` | Run via `pnpm exec proof` |
| Supervisor `tsx .../run_dag_supervisor.ts` | Supervisor `pnpm exec proof-supervisor` |
| Default state dir `.dag-runner/` | Default state dir `.proof/` |
| Log prefix `[dag-runner]` / `[dag-runner-supervisor]` | Log prefix `[proof]` / `[proof-supervisor]` |
| Examples at `.cursor/skills/dag-task-runner/examples/` | Examples at `.cursor/skills/proof/examples/` |
| Before | After |
| -------------------------------------------------------- | ------------------------------------------- |
| Skill name `dag-task-runner` | Skill name `oven` |
| Runtime in `.cursor/skills/dag-task-runner/scripts/*.ts` | Runtime in `src/*.ts` |
| Run via `tsx .cursor/skills/.../run_dag.ts` | Run via `pnpm exec oven` |
| Supervisor `tsx .../run_dag_supervisor.ts` | Supervisor `pnpm exec oven-supervisor` |
| Default state dir `.dag-runner/` | Default state dir `.oven/` |
| Log prefix `[dag-runner]` / `[dag-runner-supervisor]` | Log prefix `[oven]` / `[oven-supervisor]` |
| Examples at `.cursor/skills/dag-task-runner/examples/` | Examples at `.cursor/skills/oven/examples/` |

CLI flag names, the DAG JSON schema, the `.canvas.tsx` shape, oracle / pause / convergence semantics, and the public library API are all unchanged. Existing DAG JSON files and persisted run-state files (move them from `.dag-runner/` to `.proof/` if you want to resume) work as-is.
CLI flag names, the DAG JSON schema, the `.canvas.tsx` shape, oracle / pause / convergence semantics, and the public library API are all unchanged. Existing DAG JSON files and persisted run-state files (move them from `.dag-runner/` to `.oven/` if you want to resume) work as-is.

## What to do

1. Open `.cursor/skills/proof/SKILL.md` for the canonical workflow.
2. Replace any hardcoded `.cursor/skills/dag-task-runner/scripts/run_dag.ts` paths in your prompts / playbooks with the `pnpm exec proof` invocation.
3. If you have an in-flight run with `.dag-runner/run-state.json`, either rename the directory to `.proof/` or pass the old path explicitly via `--state-path`.
1. Open `.cursor/skills/oven/SKILL.md` for the canonical workflow.
2. Replace any hardcoded `.cursor/skills/dag-task-runner/scripts/run_dag.ts` paths in your prompts / playbooks with the `pnpm exec oven` invocation.
3. If you have an in-flight run with `.dag-runner/run-state.json`, either rename the directory to `.oven/` or pass the old path explicitly via `--state-path`.

## Why

`dag-task-runner` was always a copy-into-project bundle, which meant every project carried its own bit-rotted snapshot of the runtime. Promoting it to `@flatbread/proof` keeps one maintained runner with tsup builds, lint, and type checks, and gives downstream tooling a stable `import { parseDAG, computeRanks, ... } from '@flatbread/proof'` library surface alongside the CLI.
`dag-task-runner` was always a copy-into-project bundle, which meant every project carried its own bit-rotted snapshot of the runtime. Promoting it to `@flatbread/oven` keeps one maintained runner with tsup builds, lint, and type checks, and gives downstream tooling a stable `import { parseDAG, computeRanks, ... } from '@flatbread/oven'` library surface alongside the CLI.
Loading
Loading