7b951e46ab
With every slice feeding the pin sync, two profiles can legitimately hold the same session id. The pull already tie-breaks toward the active gateway's row (rowsByPinId), but the push resolved the profile by first match — so an unpin PATCHed the other profile and the next page re-adopted the pin. Resolve the write's row with the same active-gateway preference. Case and test from #92609. Co-authored-by: Jake Vincent <45184202+jakewvincent@users.noreply.github.com>