Bryan Helmkamp a70750f3f6 Steer a Petri run by stage ... `SteerRunRequest` takes an optional `stage`: the label the projection shows (`node@visit`, or `node/e<execution>@visit` when two executions share one) or the node's name. The server passes it on the worker control message; the worker's `RunControls` resolves a label to the live agent firing and steers that firing, and a node name through Petri's own live-stage index. Unnamed, the one-live-agent rule stays, and the refusal now names the live stages by their labels. `fabro steer --stage` sets it. A controls scenario runs two agent stages side by side, sees the unnamed steer refused with both named, and steers each apart, one over the API and one through the flag. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-09-18 19:59:23 -04:00
..
src	Steer a Petri run by stage	2026-09-18 19:59:23 -04:00
tests	Steer a Petri run by stage	2026-09-18 19:59:23 -04:00
build.rs	refactor: organize crates into three layers	2026-07-23 17:59:34 -04:00
Cargo.toml	Delete fabro-validate and fabro-acp; validate on Petri's check	2026-09-18 11:32:04 -04:00