{"version":"2.1.235","anchor":"container-arming-handles-a-head-behind-remote-probe-result","canonical_anchor":"container-arming-handles-a-head-behind-remote-probe-result","heading":"Container arming handles a head-behind-remote probe result","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/container-arming-handles-a-head-behind-remote-probe-result","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Container arming handles a head-behind-remote probe result\n\nContainer arming adds a case for when the local head is behind the remote\n\nThe armed-container decision table gained a `head_behind_remote` case. When pinned, it seeds the container from the remote ref using the probed tree; otherwise it falls into the shared not-armed builder, which now also serves the `tracked_changes` and `head_not_at_remote` cases.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}