Scott Werner 44dccfa3d2 Require version config to be workflow.toml beside its graph ... WorkflowLocation dispatches any `.toml` path to the config loader, so a supplied entrypoint such as `sub/run.toml` was accepted, its graph became the version entrypoint, and the config file was registered under its own name. Runtime only reads WorkflowVersion::config_path(), the fixed sibling `workflow.toml`, so the version's goal, environment, and Dockerfile settings were silently dropped on every run. In workflow-version projection, reject a config whose collected path is not the graph's sibling `workflow.toml`. This applies to every caller that packages versions, including `fabro run <dir>/other.toml`, which previously registered the config and then ignored it; failing at packaging replaces a silent drop. Manifest bundling for the legacy run path does not project versions and is unchanged. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-09-12 10:15:29 -06:00
..
apps	Simplify workflow version registration tool layering	2026-09-12 10:15:29 -06:00
components	Require version config to be workflow.toml beside its graph	2026-09-12 10:15:29 -06:00
foundation	Drop the duplicate-key guard that no tool route can reach	2026-09-12 10:15:29 -06:00
packages/fabro-api-client	Add content-based workflow version registration tools	2026-09-12 10:15:19 -06:00