Bryan Helmkamp d2f0e70dca Run a workflow through Petri in the server, behind the engine flag ... When a run's engine is Petri, the create handler hands the bundle, inputs and launch to Petri's check instead of the legacy compile, lint and model pinning, refuses the run with the validation error the legacy validator uses (Petri's codes as the rules, listed in the API detail), and records the admission on the run spec. The Fabro graph the read side displays is parsed without validation. The scheduler executes a Petri run in the server process through fabro_petri::engine, appending only the run lifecycle events the read side needs (run.starting, run.running, run.completed or run.failed); no stage or agent event is projected yet. Scenario tests run the hello bundle on the OpenAI twin under the version flag and a command-only bundle under the server setting, check Petri's record agrees, and cover the refusals for an unknown attribute, an undeclared node and an unknown model. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-09-17 20:27:44 -04:00
..
apps	Run a workflow through Petri in the server, behind the engine flag	2026-09-17 20:27:44 -04:00
components	Run a workflow through Petri in the server, behind the engine flag	2026-09-17 20:27:44 -04:00
foundation	Add the engine flag and record the engine on the run spec	2026-09-17 20:02:47 -04:00
packages/fabro-api-client	Delete fabro's own pricing: lithos-llm prices every response once	2026-09-14 14:46:44 -06:00