Define login-attempt retention without weakening rate limiting or evidence

Conditional design only: decide a security-evidence retention period for login_attempts separately from app_logs. Read-only PROD census at 11:58 ART found 814/824 rows before 2026-10-14 00:00 ART; rate limiter reads a 15-minute failed-attempt window, but operational/security investigations may need older events. Inventory request-ID/IP/email evidence and any compliance requirement before choosing a cutoff. If later approved, db lane must use a bounded predicate, verified recovery copy, rehearsal, fresh postchecks, and Elazar's explicit lock/write authorization. No current DELETE/TRUNCATE or other write.