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
..
acknowledgements.mdx	refactor(docs): split docs/ into public/ and internal/	2026-04-27 07:21:13 -07:00
architecture.mdx	Describe the Petri layering in AGENTS.md and the architecture doc	2026-09-18 11:32:06 -04:00
cli.mdx	Steer a Petri run by stage	2026-09-18 19:59:23 -04:00
dot-language.mdx	Add on_failure="succeed" as an explicit failure policy	2026-08-26 07:34:24 -04:00
run-directory.mdx	refactor(workflow): remove retro stage (#230)	2026-05-09 10:18:20 -04:00
sdk.mdx	Delete fabro-hooks and the engine freeze check	2026-09-18 10:47:56 -04:00
server-operations.mdx	Remove the [server.slatedb] settings and the SlateDB prefix probe	2026-09-18 16:00:24 -04:00
shell-completions.mdx	refactor(docs): split docs/ into public/ and internal/	2026-04-27 07:21:13 -07:00
user-configuration.mdx	Remove the [server.slatedb] settings and the SlateDB prefix probe	2026-09-18 16:00:24 -04:00
verifying-releases.mdx	refactor(docs): split docs/ into public/ and internal/	2026-04-27 07:21:13 -07:00