VENUS-350(b) ELAZAR: purge 36 plaintext June pg_dumps from gdrive trash (eq#52) - destructive, staged, recommend yes

ELAZAR DECISION (b), split out of VENUS-350 on 2026-10-06 so it can be answered on its own. All prep is done and staged; this needs one yes or no. ASK: purge the 36 PLAINTEXT June pg_dump files sitting in the gdrive trash (eq#52). They are unencrypted full-database dumps and therefore include vault.secrets in the clear. WHY IT IS HIS AND NOT OURS: it is destructive, irreversible once the trash is emptied, and it is his Google account. Under the fly-solo gate an irreversible deletion is a hold-for-Elazar item regardless of how obvious it looks. WHAT MAKES IT WORTH ASKING RATHER THAN LEAVING: under the fleet no-rotation rule those dumps hold CURRENTLY VALID credentials, permanently - there is no expiry anywhere in the system and the credentials in a June dump still authenticate today. A plaintext copy in a trash folder of a consumer cloud account is the worst single item in this whole row, and it is the one piece of it with no recoverability argument on the other side: they are superseded by the encrypted lane, so deleting them loses nothing. RECOMMENDATION: purge. STATE WITH THE ASK: the exact file count and total size, where they sit, that the encrypted lane supersedes them, and that the purge is staged and reversible only until the trash is emptied. Do not bundle this with the spend decision or the filtering work - keeping all three together on one row is why none of them moved since 2026-09-11.