# P26C2 R01 cleanup / recovery

This STEP changes no Machine Git source and no database schema.

Before semantic core acceptance, any failure is handled by the VM121 live driver with best-effort idempotent cleanup:

- tear down temporary network namespaces/interfaces;
- stop the localhost-only temporary auth API;
- disable any synthetic VM100 lifecycle peer;
- reconcile the agent to an empty desired set;
- delete synthetic Domain V2 rows;
- verify VM100 registry/runtime zero when possible.

A fresh encrypted PostgreSQL backup is created and restore-tested before live mutation and is retained under `/root/router-ops-backups/p26c2-r01-*`. It is an emergency recovery artifact, not an automatic rollback mechanism.

Do not blindly restore the database merely because a late postcheck/report/publication step fails. Once the full semantic core (first handshake, revoke, reissue, second handshake, final revoke and cleanup) is accepted, any later failure is a continuation/publication problem and the live core must not be replayed destructively.