Some database entries are corrupt

Due to a front-end bug, malformed policies were created. These policies still reside in the policy database; for example:

https://api.policyengine.org/us/policy/47728

Since attempts were made to analyze the economic impact of these malformed policies, the economy database may also contain incorrect entries.

We will encounter bugs in the front and back ends during development and after deployment. Are there any existing provisions to ensure that

1. tests during development don't touch production databases?
2. once a bug is found in production, e.g., malformed policies, then entries related to the bug or, in the worst case, all entries since the introduction of the bug can be deleted from the databases?

Ideally, the second case should be rare, but bugs in development are unavoidable. The first case is also important because dummy policies are often created on the front end to test UI features, which should not affect the production databases.

The issue names no files, tests, or entry points. Start with the linked malformed-policy discussion and the example policy at the supplied API URL, then trace how development tests and production database entries are handled. Done should be defined as concrete safeguards for test isolation and a dependable process for removing affected records.