The 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.
Container arming handles a head-behind-remote probe result
Container arming adds a case for when the local head is behind the remote
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
ImprovementsKind: in v2.1.235,
ImprovementsSection of the release