file-history minting is only stoppable host-wide: no per-path exclusion exists, and a file's FIRST snapshot is exempt from eviction forever

SCOPE: the MINTING half of OPS-253. OPS-253's leak surface was cleared on venus 2026-10-06 (78 copies holding a literal credential value, removed and residue-checked out of Trash); this row is what makes it come back. Measured out of claude 2.1.291 on venus, read from the binary and not from docs. 1. THE ONLY CONTROL IS GLOBAL. fileHistoryEnabled() is Zo('fileCheckpointingEnabled',true).value AND NOT env CLAUDE_CODE_DISABLE_FILE_CHECKPOINTING; fileHistoryTrackEdit() returns {kind:touch} and writes nothing when that is false. Either switch stops the minting completely. 2. NO PER-PATH EXCLUSION EXISTS. Searched every combination of Exclude/Ignore/Deny against Checkpoint/Snapshot/History in the 249MB binary: zero hits. So 'exclude the dotenv path' is not an available remedy and was not merely overlooked. 3. THEREFORE THE TRADE IS /rewind FOR THE LEAK, HOST-WIDE, AND IT IS NOT A SEAT'S CALL. Flipping either switch removes /rewind for every session on the host, which is Elazar's own undo capability. pmmaster-evolutiva-cc, 2026-10-06, explicit: do NOT flip either one. Neither switch has been touched. 4. A FILE'S FIRST SNAPSHOT IS PERMANENT. The eviction loop adds a backup to its delete set only when version !== 1, so the v1 snapshot of any file is exempt from eviction forever. A secret that was ever written into version 1 of a file is NOT removable by waiting, by retention, or by any cleanup period - only by a content-keyed sweep like the one run on OPS-253. THIS is what makes the current state insufficient rather than merely untidy. 5. WHAT THE RESIDUE ACTUALLY IS, narrowly. llmmsg-env-set.sh v1.0 sets or unsets one overlay key without Read/Write/Edit, so the .llmmsg-env write path mints nothing when it is used. What still mints is any dotenv edited directly through Read/Write/Edit by a session that does not use the tool. That is a CONVENTION, not a gate, and nothing detects a violation - the first a sweep learns of one is by reading content. NOT IN SCOPE: rotation of anything, for any of the 78 already removed or any minted since. The standing fleet rule is absolute and a credential whose only exposure is a local file history is not grounds to break a live client. MEASURED ON VENUS ONLY. whey and lezama were not scanned in this pass. WHAT A DECISION HERE LOOKS LIKE: either Elazar accepts the convention plus a recurring content-keyed sweep, or he trades /rewind for the gate. There is no third option in 2.1.291.