wipeAssets mutation incompletely removes events from event_logs table

The wipeAssets mutation deletes ASSET_MATERIALIZATION events but leaves FRESHNESS_STATE_CHANGE and ASSET_WIPED events in the event_logs table. The asset_keys row is not deleted—it receives a wipe_timestamp but persists. As a result, the asset remains visible in the catalog UI after wipe, with historical freshness events intact.

For complete cleanup of orphaned assets, manually delete remaining FRESHNESS_STATE_CHANGE and ASSET_WIPED events from the event_logs table in PostgreSQL using the asset_key as filter. Consider also removing the asset_keys row if full deletion is required rather than soft-delete.