You'll notice
Useful3 Signal3
Container sessions from a checkout behind its remote can now seed from the remote ref.
What's wrong with this entry?
Anonymous. No account, no email.
What
When starting a container-backed session from a repo whose checkout is behind the remote, a pinned session now seeds from the remote ref using the tree it probed; otherwise it reports as not armed through the same builder used for uncommitted tracked changes and other diverged states.
Evidence
case "head_behind_remote":
Strings lifted out of the shipped bundle, so the claim above can be checked against them.