{"version":"2.1.239","anchor":"cloud-sessions-can-accept-a-pre-made-checkout-but-nothing-pr","canonical_anchor":"cloud-sessions-can-accept-a-pre-made-checkout-but-nothing-pr","heading":"Cloud sessions can accept a pre-made checkout, but nothing produces one","tier":"soon","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/cloud-sessions-can-accept-a-pre-made-checkout-but-nothing-pr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Cloud sessions can accept a pre-made checkout, but nothing produces one\n\nCloud sessions can accept a ready-made checkout, but the function producing one is empty.\n\n**What**\n\nThe cloud session startup path now threads an optional pre-made repository checkout through to the checkout step, alongside the existing pre-fetched commit. The function meant to produce that checkout has an empty body and returns nothing, so the value is always absent and the branch that would use it never runs.\n\n**Details**\n\n- The git source is assembled as `{...source, ...(tip && {prefetchedTip}), ...(standby && {standbyCheckout})}`, and the repository setup forwards `standbyCheckout` onward.\n- The producer takes `{claimed, useWorktrees, source, onDebug, dir}` and its body is a bare `return;`. Plumbing is in place for a later fill-in.\n\n**Evidence**\n\n`standbyCheckout`\n\n- Area: Cloud Sessions\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}