docs: #100 — stabilize Task 2 SHA reference in ISSUES.md

Task 2's commit landed at 64518d59, then an amend (to fix the original
placeholder SHA in the same file) produced the new HEAD a64e6f2 with
identical content. The in-file SHA still pointed at the pre-amend
64518d59 — reachable today only via reflog, unreachable after the next
git gc. Switch to a64e6f2 which is on the branch and survives gc.

This is a follow-up commit (not an amend) so the canonical SHA is
itself stable on the branch from this commit forward.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Erik 2026-05-25 21:47:37 +02:00
parent a64e6f20da
commit 84e3b72b27

View file

@ -3424,11 +3424,11 @@ Unverified. The likely culprits, ranked by suspected probability:
# Recently closed
## #100 — [DONE 2026-05-25 · f48c74aa + 64518d59] Transparent rectangular patches around every house (terrain rendering)
## #100 — [DONE 2026-05-25 · f48c74aa + a64e6f2] Transparent rectangular patches around every house (terrain rendering)
**Status:** DONE
**Closed:** 2026-05-25
**Commits:** `f48c74aa`, `64518d59`
**Commits:** `f48c74aa`, `a64e6f2`
**Component:** rendering, terrain
**Resolution (2026-05-25 · #100):** Replaced the cell-level