chore(changelog): point the codes fix at its rebased hash (d290e65)

Rebasing changed it from bfa9668, and check-changelog still passed because the old
object stays local. Recorded in AGENTS.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

AGENTS.md

@@ -1205,7 +1205,10 @@ to an open page). Four things hold it up:
   own hash, so the entry lands in a follow-up `chore(changelog)` commit naming the one before it. A
   feature spanning several commits also gets a release note when it lands — a few paragraphs from
   its spec, with its `from..to` range and spec paths. Run `bun run scripts/check-changelog.ts`
-  after: tests check a ref's shape only, because CI's checkout is shallow. Data refreshes and
+  after: tests check a ref's shape only, because CI's checkout is shallow. **Rebasing an unpushed
+  commit changes the hash a changelog ref names, and the check still passes** because the old object
+  stays in your local repository (2026-11-07, `bfa9668`). The refresh pushes to `main` twice a day, so
+  this is an ordinary way to get here: re-read any new ref after a rebase and before pushing. Data refreshes and
   changes invisible to readers get no entry.
 - **Zod schemas are the single source of truth for types.** Derive with `z.infer<>`; never
   hand-write an interface that duplicates a schema.

src/shared/changelog.ts

@@ -56,7 +56,7 @@ export const ENTRIES: Entry[] = [
     kind: "fix",
     title: "Wuthering Waves redeem codes are updating again",
     body: "Our source renamed the section we read, so the list had been stuck since late October.",
-    ref: "bfa9668",
+    ref: "d290e65",
   },
   {
     id: "genshin-exact-ends",