lootignore: local env files, which tools create without being asked (#808 follow-up)
`vercel link` writes a `.env.local` holding a VERCEL_OIDC_TOKEN as a side effect of
linking a project. It landed in a loot working change as `internal` on 2026-08-07,
unasked for, during the site deploy for #808. Nothing was landed or pushed, so there
was no exposure — but `internal` is readable by the relay, so riding along with a
land would have put a live token there.
⭐ .gitignore already covered it and .lootignore did not, so the two disagreed about
the same file. An ignore rule present in git but absent in loot is a gap, not a
duplicate: git's copy silences the warning that would otherwise have surfaced it.
`.env` / `.env.*` with `!.env.example`, matching how .gitignore treats them. Verified
by recreating .env.local and confirming `loot status` stays clean.
Also carries the `.vercel` / `.env*` lines `vercel link` appended to .gitignore, which
are correct and worth keeping. 82fab4e6 · dbf3dbe6…
Renames are not followed. loot's tree maps a path to an address, so a rename is a delete and an add. This list is the history of the name, not of the bytes.