Bryan Helmkamp 1fda9633e4 Bind the run's resolved goal into Petri's check ... An intent's goal override, and a `[run.goal]` layer, reached the run's display graph and its settings but not Petri's check, so the agent stages executed with the workflow's own goal while the run showed the override. The launch now carries the run's resolved goal (the settings' inline `run.goal`, layered as the create path layers it) as Petri's `petri.launch_goal` compile variable, which Petri binds over the bundle's `[run] goal` and the graph's own `goal`, so admission's frozen plan carries the goal the run shows. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-09-21 03:48:35 -04:00
..
apps	Bind the run's resolved goal into Petri's check	2026-09-21 03:48:35 -04:00
components	Bind the run's resolved goal into Petri's check	2026-09-21 03:48:35 -04:00
foundation	Name the fold's repeated shapes once: completion, model usage, pause, conclusion	2026-09-20 15:01:14 -04:00
packages/fabro-api-client	Forward every configured sandbox plugin to the Petri worker	2026-09-19 14:45:42 -04:00