Unpushable history: Oct 2024 commits reference 69 LFS objects that exist on no server

[endolith]

Pushing any branch containing the October 2024 history to an LFS-enabled remote fails, and the missing objects cannot be fetched from here either.

Evidence:

• 3d7d1e7 (2024-10-17, "LFS setup") began tracking *.zip; f488d08 (2024-10-18, "Delete .gitattributes") ended it. The 9 commits in between reference 69 LFS objects (~2.0 GB: 68 zip/dataset plus zip/type zips).
• LFS is disabled on this repo: git lfs fetch --all upstream fails with "batch response: Git LFS is disabled for this repository". Current tip carries no LFS files (zip/ was later removed in 8062eff "Delete zip"; the large .dat files are stored directly, see the >50MB warnings on push).
• Consequence: pushing any branch based on current main to an LFS-enabled fork is rejected with GH008: Your push referenced at least 69 unknown Git LFS objects. The objects cannot be supplied because they exist on no server to download from.

Possible resolutions:

• Re-upload the exact zip bytes and re-enable LFS (note: object IDs are content hashes, so the bytes must match exactly; the v1.0 release assets may differ).
• Rewrite those 9 commits to drop the dead pointers (coordinated history rewrite).
• Do nothing: accept that branches based on current main cannot be pushed to LFS-enabled forks, and take contributions as patches (git am works fine) until then.

— opencode