{"version":"2.1.224","anchor":"bridge-event-checks-fail-closed-when-their-config-is-malform","canonical_anchor":"bridge-event-checks-fail-closed-when-their-config-is-malform","heading":"Bridge event checks fail closed when their config is malformed","tier":"internal","area":"Editor Bridge","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/bridge-event-checks-fail-closed-when-their-config-is-malform","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Bridge event checks fail closed when their config is malformed\n\nIf the bridge event rules are unreadable, only fully verified events are accepted.\n\n**What**\n\nIf 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.\n\n**Details**\n\n- Unverified events that are not control requests are dropped with a warning that classifies the payload as `control_request_other` or `other_payload_type`.\n- Drops are reported as `bridge_stray_event_attestation`, deduplicated to once per class per process so a flood does not spam telemetry.\n\n**Evidence**\n\n`bridge_stray_event_attestation`\n\n- Area: Editor Bridge\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}