{"version":"2.1.235","anchor":"device-bridge-stops-when-its-gate-is-served-off-not-merely","canonical_anchor":"device-bridge-stops-when-its-gate-is-served-off-not-merely","heading":"Device bridge stops when its gate is served off, not merely unset","tier":"internal","area":"Device Bridge","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/device-bridge-stops-when-its-gate-is-served-off-not-merely","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Device bridge stops when its gate is served off, not merely unset\n\nDevice bridge now stops only when its gate is explicitly served off, not merely absent\n\nA new helper distinguishes a remote-config value of `false` from the absence of any value at all. It reports true only when the off value actually came from the payload, an override, or a disabled source, falling back to a separate check for local-fallback values and returning false when the value is read from disk.\n\nThe device bridge now uses this helper as its liveness predicate, logging `stopping: the gate turned off` with reason `gate_off` when it is triggered.\n\n- Flag `tengu_violin_wood`: Off in both readings (read for one account on one subscription tier against v2.1.235; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Device Bridge\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}