mirror of
https://github.com/fabro-sh/fabro.git
synced 2026-10-01 02:04:24 +00:00
e0b546d465
The projector takes two pools: the one Petri's records live in and the one the view tables live in. In the server both are the one database; a test fixture keeps the runs row, the platform records and the projection tables in the run summary store's own pool, which the projector was not reading, so a run projected in a test server folded its Petri events before its run.created record. The startup run-history verification checks only a Petri run's identity and legacy guard, since its row is the projector's. An agent stage's response is the response.<node> its outcome wrote into the run context, as the prompt step writes it. The scenario tests assert each branch's own index. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| fabro-acp | ||
| fabro-automation | ||
| fabro-checkpoint | ||
| fabro-dump | ||
| fabro-environment | ||
| fabro-github | ||
| fabro-graphviz | ||
| fabro-hooks | ||
| fabro-install | ||
| fabro-interview | ||
| fabro-llm | ||
| fabro-manifest | ||
| fabro-mcp | ||
| fabro-mcp-store | ||
| fabro-petri | ||
| fabro-sandbox | ||
| fabro-slack | ||
| fabro-store | ||
| fabro-tool | ||
| fabro-tracker | ||
| fabro-validate | ||
| fabro-variable | ||
| fabro-workflow | ||
| fabro-workflow-version | ||