Leanmerce Commerce Assistant 0.12.9 — update and legacy identities

NORMAL UPDATE: leanmerce-commerce-assistant 0.12.7 or 0.12.8 -> 0.12.9
Version 0.12.9 verifies existing tables, required columns and full ordered
indexes before enabling Commerce Assistant document/audit features. An old
version marker alone is not trusted. Missing schema is repaired additively;
failed attempts wait 60 seconds before automatic retry. A visible admin
notice remains while setup is unavailable; ordinary WooCommerce checkout
continues. Correct database permissions before retrying a persistent failure.
Conflicting existing constraints or data are not dropped automatically.
Do not delete settings, archive files, encryption keys or history to repair
an update. Back up the database, files and encryption material together.

The 0.12.7 -> 0.12.8 archive changes retained below also apply when updating
from 0.12.7 directly to 0.12.9.
Folder, main file, text domain, namespaces and stored identifiers do not
change. Update in place; do not uninstall/reinstall. Preserve database,
private document files and encryption material in the same backup set.
Schema 3 -> 4 adds lmcc_confirmation_originals and lmcc_document_dispatches
(with the site's table prefix). It does not clear settings, change orders,
backfill historical originals or rewrite existing documents. Orders without
the new archive have no fabricated My Account original; current printouts
are separate. Preserve separately saved old PDFs. Review the selected
enabled customer email after updating. Tested companion: unchanged Pro
0.14.2-dev.17; older compatibility is not thereby certified. Code rollback
must retain the same current database/storage so new orders are not erased.
An older runtime may not expose newer archive features. Never restore an old
database over orders accepted since the backup.

LEGACY FOLDER TRANSITIONS — not the same-identity update above

The new leanmerce-commerce-assistant/leanmerce-commerce-assistant.php basename
is a SEPARATE plugin from commerce-assistant/commerce-assistant.php and
leanmerce-commerce-compliance/leanmerce-commerce-compliance.php. Installation
is not an automatic in-place update. Production migration is not authorized
by this review remediation. Never activate both Free identities.

Before a separately approved migration: back up database, existing package,
private document storage and encryption material; pause new processing;
deactivate Pro first, then old Free; install and activate new Free; confirm
only one Free runtime, unchanged settings/orders/history/document hashes.
Do not uninstall or delete historical data. Validate translations under the
new leanmerce-commerce-assistant domain and each add-on before reactivation.
The exact legacy dependency alias maps leanmerce-commerce-compliance to the
new slug; commerce-assistant is not globally aliased. Unchanged Pro RC6 with
Requires Plugins: commerce-assistant requires separate native compatibility
validation and potentially a later Pro update. No Pro sources were changed.

Rollback: pause processing, deactivate add-ons and new Free, restore original
package/activation order. Keep database/storage snapshots if schema changes
were observed. The rename does not migrate schema or rewrite stored data.
Old cached/multi-node workers require operator draining; no universal safety
claim is made. Existing translation files must be reviewed and recompiled
with the new domain. See owner compatibility report for actual test results.
