Scott Werner 5e79285a43 Honor the workflow's configured run.scm repository in target derivation ... The replaced manifest builder resolved the run's repository identity from the workflow's run.scm settings before falling back to the checkout's origin. The new standalone derivation always used the checkout's origin, so a fork checkout of a workflow that names its upstream repository silently targeted the fork and pushed there. Read the run.scm layer from the resolved workflow.toml and project.toml (or from the inline workflow.toml bytes) and pass it through both the CLI and the standalone run-tool adapter. When the configured repository is not the checkout's origin, nothing can be proven about it, so derivation now fails with a message naming that mismatch instead of the generic "push the commit" hint. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-09-12 10:58:42 -06:00
..
apps	Honor the workflow's configured run.scm repository in target derivation	2026-09-12 10:58:42 -06:00
components	Honor the workflow's configured run.scm repository in target derivation	2026-09-12 10:58:42 -06:00
foundation	Collect inline workflows at their exact entrypoint	2026-09-12 10:58:21 -06:00
packages/fabro-api-client	Add content-based workflow version registration tools	2026-09-12 10:15:19 -06:00