fabro/lib
Bryan Helmkamp 806ac90c98
Freeze the engine half of fabro-workflow to bug fixes
The integration plan's F4.1: once Fabro runs on Petri, the engine half of
fabro-workflow (handler/, lifecycle/, pipeline/execute, graph/routing,
node_handler, retry, condition, context, model_fallback) takes bug fixes
only, and new engine behaviour goes to Petri.

scripts/check-engine-freeze.sh holds the frozen path list, diffs the
branch against a base ref and exits 1 when any frozen file gained lines;
scripts/check-engine-freeze-test.sh proves that on a synthetic
repository. The Engine freeze workflow runs both on every pull request
that touches the crate's src, re-runs on label changes, and fails unless
the pull request carries the `bugfix` label. AGENTS.md and the
fabro-petri README name the freeze, the label and the script.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-18 02:19:29 -04:00
..
apps Merge branch 'petri-integration-tools' into petri-integration 2026-09-18 02:02:51 -04:00
components Freeze the engine half of fabro-workflow to bug fixes 2026-09-18 02:19:29 -04:00
foundation Merge branch 'petri-integration-api' into petri-integration 2026-09-18 01:39:53 -04:00
packages/fabro-api-client Merge branch 'petri-integration-api' into petri-integration 2026-09-18 01:39:53 -04:00