Plan selective app_logs info retention without erasing audit events

Conditional implementation plan ONLY after MOVILBA-799 decision: assess whether to retain or remove pre-2026-10-14 00:00 ART app_logs level=info rows (70/357 total app_logs as of 11:58 ART). Preserve 8 audit-level rows that feed /api/admin/audit-log and do not silently remove 2 warnings, access/request-ID evidence, or post-cutoff rows. Before any execution, db lane must remeasure exact counts and dependencies, capture a verified durable recovery copy, use a bounded rehearsal and fresh postchecks, and obtain Elazar's separate authorization/lock disposition. Do not run prior MOVILBA-9 truncate script; it was already completed and is too broad. No current DB/code write authorized.