Unclear What consumes the new isStillEnabled/onEnabledChange inputs, and what hasUnservedChange/inFlightCalls/whenIdle are used for downstream, is not shown.
The device bridge's start path now subscribes to feature-gate changes in addition to egress-gate changes, and shuts down with a distinct stop reason when the feature gate flips off mid-session; the egress stop path also gained its own reason string ("egress_denied" versus "gate_off"). The gate check runs through a new k8s() function that resolves gate tengu_violin_wood (falling back to false) and treats payload, override, or disabled sources as "now off". Two new inputs, isStillEnabled and onEnabledChange, are read at the default site but nothing in the bundle currently supplies them, so they appear to be seams for tests or a host rather than active code paths yet. The same call also has the bridge announce hasUnservedChange, inFlightCalls, and whenIdle to the session.
tengu_violin_wood Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.235: off
Read once, for one account on one subscription tier, against v2.1.235. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
What consumes the new isStillEnabled/onEnabledChange inputs, and what hasUnservedChange/inFlightCalls/whenIdle are used for downstream, is…