Scott Werner 97a7bb06e5 Pin sibling config resolution to the supplied file keys ... Supplied files are staged on the host filesystem and WorkflowLocation probes the fixed sibling name `workflow.toml` there. A request that supplied `Workflow.toml` beside its graph therefore attached the config on a case-insensitive host (and then failed the not-supplied check), while the identical request on ext4 registered a version with no config. The outcome of a content-addressed registration depended on the server's filesystem. After collection, every version is checked against the supplied map: when no exact sibling `workflow.toml` was supplied, no supplied key may alias that name under the same case and normalization rules the tool already applies to supplied keys. A supplied sibling config still attaches only to the graph it selects, matching checkouts, since several graphs may share one directory. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-09-12 10:15:29 -06:00
..
apps	Move the supplied-content packager next to its collector	2026-09-12 10:15:29 -06:00
components	Pin sibling config resolution to the supplied file keys	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