{"version":"2.1.274","anchor":"remote-bridge-teardown-telemetry-reworked-with-archive-crede","canonical_anchor":"remote-bridge-teardown-telemetry-reworked-with-archive-crede","heading":"Remote bridge sessions gain worker-epoch tracking","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/remote-bridge-teardown-telemetry-reworked-with-archive-crede","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Remote bridge sessions gain worker-epoch tracking\n\nThe remote\/headless session bridge now tracks a worker epoch alongside the existing worker bearer token, and reworked its teardown telemetry.\n\n**Unclear.** Nothing has been read yet about the `tengu_bridge_repl_teardown` gate, so whether this behavior is active for any account is unknown.\n\n**What**\n\n- The remote session-bridge teardown path now assembles its preflush-hold and archive-status telemetry via helper functions, and exposes a new `getWorkerEpoch` accessor on the bridge host interface (alongside the existing `getWorkerBearerToken`) when a worker bearer token is available.\n\n- The headless\/print-mode bridge mount setup now also passes a `getWorkerEpoch` accessor through to the same mount configuration.\n\n**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.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}