{"version":"2.1.236","anchor":"remote-bridge-waits-for-the-disconnect-notice-and-an-inbox-f","canonical_anchor":"remote-bridge-waits-for-the-disconnect-notice-and-an-inbox-f","heading":"Remote bridge waits for the disconnect notice, and an inbox fetch that is always off","tier":"soon","area":"Remote Bridge","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/remote-bridge-waits-for-the-disconnect-notice-and-an-inbox-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Remote bridge waits for the disconnect notice, and an inbox fetch that is always off\n\nRemote bridge shutdown waits for its disconnect notice, and a new inbox fetch always refuses.\n\n**What**\n\nBridge teardown now waits for the pending disconnect notice on both the normal and skip-archive exits. A new message-fetch entry point is present but hard-disabled: it always returns a failure with the reason `feature_disabled`.\n\n**Details**\n\n- The polling client marks the worker generation as superseded before every fatal generation mismatch: repeated 404s, an expired session token, and exhausted authentication failures. That lets shutdown tell a replaced session apart from a live one.\n- The flush is exposed on the transport alongside close.\n\n**Evidence**\n\n`feature_disabled`\n\n- Area: Remote Bridge\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}