fabro/lib/apps/fabro-server
Bryan Helmkamp 7b466ad9f3
Drive the Petri projector from the server
The server holds one projector over its database and signals it after
each committed worker append, after each committed platform record
(through the run summary store's hook), at worker exit, and over every
Petri run at startup after the restart reconcile. A run executing in
the server process under the test override appends through the
projector's observing store, so it is signalled the same way. The
scenario tests read GET /runs/{id}/state after the view settles: the
hello prompt stage with its response, the command stage with its
output, and a two-branch parallel bundle whose branches are grouped
under the fork with the fork's results.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-17 22:32:23 -04:00
..
migrations Run fabro exec through pebble's command-line session 2026-09-11 20:51:01 -06:00
src Drive the Petri projector from the server 2026-09-17 22:32:23 -04:00
tests Drive the Petri projector from the server 2026-09-17 22:32:23 -04:00
build.rs refactor: organize crates into three layers 2026-07-23 17:59:34 -04:00
Cargo.toml Run a workflow through Petri in the server, behind the engine flag 2026-09-17 20:27:44 -04:00