{"version":"2.1.248","anchor":"a-per-session-flag-named-tetherlivegate-has-no-code-that-use","canonical_anchor":"a-per-session-flag-named-tetherlivegate-has-no-code-that-use","heading":"A per-session flag named tetherLiveGate has no code that uses it","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/a-per-session-flag-named-tetherlivegate-has-no-code-that-use","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### A per-session flag named tetherLiveGate has no code that uses it\n\nA session switch called tetherLiveGate is declared but nothing anywhere reads or writes it.\n\n**What**\n\nThe per-session cache of resolved feature switches now declares a field called `tetherLiveGate`, replacing one that previously held a plan-mode resume guard. The name occurs exactly once in the whole build, as the declaration: nothing writes it and nothing reads it, so whatever \"tether live\" is, its plumbing shipped ahead of the feature.\n\n**Details**\n\n- Two other fields added to the same object in this build, for workflow-authoring skill availability and kept deferred tools, do have readers.\n\n**Evidence**\n\n`tetherLiveGate`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}