Bryan Helmkamp 23c422f9a2 Cover the run tools inside a Petri run through the server and its worker ... Three scenarios on the real binary: an agent creates a child run with `fabro_run_create` from inside a Petri run and the child carries the parent link; a `[[run.hooks]]` pre_tool_use hook blocks a run tool, the model reads the reason, and Petri's record holds the report and the denied call; a sub-agent calls an inherited run tool, recorded under the parent stage naming the parent session. The Petri scenario harness is shared: the server can start with extra settings and vault entries, and the detached run takes extra arguments. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-09-18 01:52:46 -04:00
..
apps	Cover the run tools inside a Petri run through the server and its worker	2026-09-18 01:52:46 -04:00
components	Register Fabro's run tools on a Petri run through the host tool capability	2026-09-18 01:52:46 -04:00
foundation	Carry Petri's sandbox plugin variables into workers and test servers	2026-09-17 21:20:22 -04:00
packages/fabro-api-client	Add the Petri run store endpoints to the API	2026-09-17 20:12:20 -04:00