Unclear Nothing has been read yet about the tengu_bridge_repl_teardown gate, so whether this behavior is active for any account is unknown.
What
- The remote session-bridge teardown path now assembles its preflush-hold and archive-status telemetry via helper functions, and exposes a new
getWorkerEpochaccessor on the bridge host interface (alongside the existinggetWorkerBearerToken) when a worker bearer token is available. - The headless/print-mode bridge mount setup now also passes a
getWorkerEpochaccessor through to the same mount configuration.
Why This lets the bridge track which "epoch" (generation/instance) of a worker it's dealing with, which is internal plumbing that supports more accurate teardown and credential handling for remote/headless bridge sessions.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Nothing has been read yet about the `tengu_bridge_repl_teardown` gate, so whether this behavior is active for any account is unknown.