Before tearing a remote session down for an account change, the bridge cross-checks the local identity file against which account the server says the credential belongs to. A genuine switch ends the episode and archives using the original owner's credential; a disagreement where the server still attributes the credential to the owner just re-baselines and keeps going. Gated on tengu_bridge_owner_pinned_end, fallback on.
- The session pins both the account and organization it started under.
- The re-baseline case is logged rather than silent.
[bridge:owner-pin] identity file names another account but the server attributes the credential to the owner — re-baselining
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_bridge_owner_pinned_end Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.234: on
Read once, for one account on one subscription tier, against v2.1.234. It isn't a statement about your account. What a flag value here can and cannot tell you
New in this build: tengu_bridge_owner_pinned_end