[grojof]

Second audit, group C: restores, duplications and their neutralisation. The catalogue was checked against the Odoo 14.0–19.0 and OCA l10n-spain sources.

• One step per copy. Each copy runs seed → identity → Odoo's own neutralize.sql → catalogue → check → hand-over as a single step.
  • A failure drops only the database that step created, so no armed or blocking leftover remains.
  • A staging comment marks an interrupted copy, so the next run replaces it.
• Access before the hand-over. The role gets CONNECT only at the hand-over. Before, an Odoo with db_name set could connect by name.
• Restore.
  • Local: runs like a duplication, with no service stop.
  • Remote: atomic. It drops the database and restarts the service on failure.
  • Uses --no-comments, and the service starts after the files.
• Odoo's own neutralisation (16–19) runs every installed module's neutralize.sql. It is read from the checkout as the instance user and run as the copy's owner.
• Catalogue gaps closed:
  • SII and TicketBAI on 14–17, the EDI proxy on 14–16, Google Calendar on 15–17, and IAP on 18–19;
  • VERI*FACTU, Odoo's and OCA's;
  • OCA TicketBAI;
  • web push, cloud storage, certificates and SMS;
  • the Malaysian and Greek EDI;
  • cli mail servers, and archived servers that 12–15 still use;
  • citations corrected.

Verified:

• verify_privilege (CI) checks the staged copy: success, failure partway, an existing target, and a leftover.
• verify_neutralisation passes with real Odoo 14 and 18. It covers Odoo's own SQL, the EDI demo parameter armed as prod, and the web push key.
• verify_data_safety, verify_secrets, unit tests, and openspec 1.4.1 all pass.

OpenSpec: 2026-10-08-copies-done-whole.

Assisted-by: Claude