Then just given people a certain grace period to reactivate or get their data out before it's removed.
It wouldn't fix production deployments where you want alarms, not a shutdown, when you hit spending caps, but it would help people on the dev stage to avoid issues like this.
People bring this every time. You give a grace period and then yes - assuming the user opted into a "turn everything off".
Its not some impossible engineering feat & clouds are full of "out of money data gone" stuff already. e.g.
>If a paid subscription ends or is terminated, Microsoft retains customer data stored in Microsoft 365 in a limited-function account for 90 days to enable the subscriber to extract the data.
It makes way more sense for me to build my stuff using a dev/testing account. After that I'll have a good enough understanding of the resources I'm using that it's practical for me to configure more complicated cost controls using a production account.
It's not all or none.