Framework asked if setting a password in the firmware would help? It seems their support channels are clueless on how Secure Boot, their certificates, and their own firmware works and were dragging the whole troubleshooting steps out because they had no idea how to fix the issue. Framework claimed this was a unique one-off situation and their suggestion after their firmware caused the issue is to buy a new mainboard.
I’m not at all suspicious.
Thank god I found this thread and this post directly from Framework so I at least know I am not delusional. The final post I used was this.
I managed to restore the certificates starting with a downgrade 3.22 ClearVar firmware and got the firmware and Microsoft boot keys all up to date.
Unfortunate moral of the story - don’t trust Framework’s support.