Inbound UDP packets not reaching bridged modem after Xfinity reprovisioning

My Xfinity service was reset/reprovisioned on April 29. Before that reset, inbound UDP traffic to my self-hosted server worked. After the reset, outside users can no longer use send packets via 10000/udp to my server.

This is not a Wi-Fi issue, speed issue, DNS issue, or customer-router configuration request.

Current setup:

Xfinity gateway in bridge mode
Firewalla router connected behind the gateway
Firewalla WAN receives the public IPv4 address directly
Server behind Firewalla
UDP 10000 port-forward rule exists on Firewalla to server.

LAN clients can send the packets to the server. Outside clients, including cellular, fail. I tested from an external IPVanish VPN to my ip on UDP destination port 10000. Firewalla shows zero hits on the UDP 10000 rule.

I also ran packet capture on the Firewalla/router side for UDP destination port 10000 during the external test, and no packets appeared.

Regular internet works and the modem signal may look good, but that does not test unsolicited inbound UDP delivery. I need this escalated beyond modem-health troubleshooting. Please have Tier 2, network/provisioning, or CSA verify whether unsolicited inbound UDP packets to my public IPv4 address are being filtered, dropped, or affected by security/provisioning before reaching my bridged modem/router handoff.

So far all techs only seem to have tools to test modem health.  I've even replaced the modem after I was promised escalation to the next group.  Now that is being refused since "the signal is good."  Customer requests Tier 2/network/provisioning/CSA review for possible filtering, security profile, or provisioning issue.  So far this request has fallen on deaf ears.  How can I get this request in front of someone that can restore the service to the way it worked on 4/27?