Pre-launch operational-log retention decision and safeguards

Pre-launch decision and, only if approved later, narrowly scoped retention of pre-2026-10-14 operational records in PROD. PROD movilba import lock remains until Elazar explicitly lifts it; this epic authorizes no DELETE, TRUNCATE, DB write, code edit, or deploy. Read-only census at 2026-10-14 11:58 ART, strict cutoff < 2026-10-14 00:00 ART: app_logs 80/357 (70 info, 2 warn, 8 audit); login_attempts 814/824; audit_log 0/0. Preserve app_logs level=audit (admin audit UI), audit_log (DEV edited-row provenance), all *_archive before-images, business/vehicle history, RUTAP snapshots/import manifests/control data. CHANGELOG.md is regenerated from Git, not a DB cleanup target. Existing MOVILBA-9 was completed on 2026-10-09 and must not be rerun; MOVILBA-11 is a separate deferred archive-purge decision, not implicitly reopened here. First decide whether any retention is desirable; if so, specify exact population, evidence retention, ART cutoff, recovery anchor, rehearsal and postchecks before a separately authorized operation. No current write authorization.