Under the hood
Useful2 Signal3
If the bridge event rules are unreadable, only fully verified events are accepted.
What's wrong with this entry?
Anonymous. No account, no email.
What
If the configuration controlling which bridge events are accepted fails to parse, verification now falls back to the strictest setting (accept only fully verified events, no other statuses allowed) and reports "malformed_config" once, rather than proceeding on a partial config.
Details
- Unverified events that are not control requests are dropped with a warning that classifies the payload as
control_request_otherorother_payload_type. - Drops are reported as
bridge_stray_event_attestation, deduplicated to once per class per process so a flood does not spam telemetry.
Evidence
bridge_stray_event_attestation
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Remote bridge replaces stale-epoch recovery with a one-shot supersession close
Both mention bridge
-
v2.1.236
Remote bridge waits for the disconnect notice, and an inbox fetch that is always off
Both mention bridge
-
v2.1.236
Bridge shuts down cleanly on SIGHUP
Both mention bridge