Bridge failures are now labelled as authentication or terminal, though nothing reads the label yet.
Auth-versus-terminal tagging on REPL bridge failures is recorded but not yet surfaced anywhere.
What's wrong with this entry?
Bridge failures are now tagged as either an authentication problem or a terminal one, alongside the existing error. Missing OAuth token, missing organization and unenrolled trusted device count as auth; everything else defaults to terminal. Nothing user-visible changes yet.
replBridgeErrorKind
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.