Editors are now told live whether telemetry is off, on a second channel besides startup.
What's wrong with this entry?
The boolean saying the CLI has telemetry turned off, previously only in the startup message an editor extension receives, is now also published on a second control-protocol surface, computed from a live check rather than a static value.
- It sits alongside the feedback-survey config and the remote-control auto-enable flag on that surface, and is always sent there.
- The description states that IDE hosts fold it into the gate for their own direct telemetry, and that an older CLI which omits it should be treated as unknown rather than as enabled.
- Nothing changes for someone using the CLI directly; it changes what an attached IDE is told.
IDE hosts fold it into the gate for their own direct telemetry. Absent (older CLI) → unknown.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.