Scott Werner b413b9b29c Inherit the parent branch, not its pinned commit, for child run targets ... A child created without a target copied the parent's full Git target, including the sha admitted for the parent. Clone-based providers never fall back to branch HEAD, so a child created after the parent pushed new commits was checked out at the parent's starting commit and never saw the work it was meant to review or continue. Inherit the repository and branch only, so the child resolves the branch's current remote HEAD at admission; the parent's pinned commit and tag stay on the parent. Callers that want a pinned child pass an explicit target. Folder and none targets are unchanged. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-09-12 10:58:42 -06:00
..
apps	Inherit the parent branch, not its pinned commit, for child run targets	2026-09-12 10:58:42 -06:00
components	Inherit the parent branch, not its pinned commit, for child run targets	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