Bryan Helmkamp 03309d4240 Let Petri compile and execute a Fabro run through fabro-petri ... `check` materializes a workflow version's bundle into a temporary directory (`Runtime::check` reads files from disk), lowers it with the run's inputs and launch, and returns the admitted graphs or Petri's diagnostics in a shape the server maps onto Fabro's. `admission` keeps the admitted graphs in the blob store, named on the run spec and verified by digest on load. `runtime` assembles the same Petri runtime at create and at execution: the Fabro frontend with the server's settings layer, the Attractor step kinds, the model client as the PebbleClient capability so admission pins every model. `engine` runs the admitted graph in the server process over SqliteRunStore under the Fabro run id, with the standalone defaults, an interviewer that fails any question, and cancel on a token, and derives the outcome from inspect_run over the run's record. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-09-17 20:27:44 -04:00
..
apps	Add the engine flag and record the engine on the run spec	2026-09-17 20:02:47 -04:00
components	Let Petri compile and execute a Fabro run through fabro-petri	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