Under the hood
No documentation found
The 'dev_intent' system message subtype is now filtered as routine, like other benign background messages
What
Internal message-filtering and deduplication logic now treats a system message subtype called dev_intent the same way it treats other routine, benign subtypes like files_persisted, mirror_error, and vcs_state_changed. This means it gets consistently skipped or filtered rather than being handled as an unrecognized message type.
Why
This keeps a new category of routine internal signaling from being surfaced or mishandled as if it were unexpected, consistent with how other background status messages are already treated.
Names in the bundledev_intent