chore(gacha): drop the last references to the retired beta route

Removes the test that checked /api/gachabeta answers 404 and the journal for the old beta animation, and points the research reports at /api/gacha.

renderer/plans/journals/2026-10-01-rewrite-gacha-beta-wish-animation.md

@@ -1,23 +0,0 @@
----
-title: Rewrite gacha beta wish animation
-date: 2026-10-01
-summary: "Clarified the comet approach, cloud piercing, and cosmic SSS food reveal."
----
-
-# Rewrite gacha beta wish animation
-
-## Changes
-
-Updated the existing eight-second beta composition with a fading night sky, a visible comet approach behind the main cloud, radial cloud dispersal and an impact ring, a perspective-spinning Remotion toon star, and an astrology-ring result reveal. The beta rank is always SSS, as requested; rarity still controls the light palette. Kept the existing caller-selected label contract, so the caller supplies its randomly chosen food. Updated the owning README section.
-
-## Validation
-
-Focused choreography tests passed. Lint, JavaScript type checking, and all 92 tests passed. Render smoke and API smoke passed, including the real beta MP4 response. Inspected rendered frames of the approach, cloud impact, flight, explosion, and final Vietnamese label with SSS. Reviewed the diff inline against the requested phases and API compatibility; no remaining findings.
-
-The bare session environment initially could not launch Chromium because libnspr4 and other runtime libraries were absent. Downloaded and unpacked runtime dependencies under /tmp without system installation. Still-frame inspection then revealed missing text because this environment had no installed fonts. Added temporary Noto and DejaVu fonts through FONTCONFIG_FILE and regenerated the smoke fixtures successfully. Docker already installs Noto fonts and Chromium runtime dependencies.
-
-## Result
-
-The local sample is fixtures/gachabeta-5-star.mp4 (ignored by Git). No commits or publication performed. Render processes exited cleanly. AgentWiki publish skipped.
-
-> Historical work record — not durable authority. Prefer docs/specs/ADRs for current decisions.

renderer/plans/reports/researcher-261001-1656-open-source-gacha-candidates.md

@@ -1,19 +1,19 @@
 ---
-title: Open-source web gacha projects as a code source for /api/gachabeta
+title: Open-source web gacha projects as a code source for /api/gacha
 date: 2026-10-01 16:56 (Asia/Saigon)
 ---
 
-# Open-source web gacha projects as a code source for /api/gachabeta
+# Open-source web gacha projects as a code source for /api/gacha
 
 ## Answer
 
-No candidate offers reusable code that would make the beta look more like the
+No candidate offers reusable code that would make the gacha wish look more like the
 real game. The realistic simulators get their look by playing MP4/WebM clips
 recorded from the commercial games. Their code is often MIT-licensed, but the
 clips belong to the publisher (HoYoverse, Nexon, and others). Mantan21's README
 says so directly: "all assets used for this application belongs to Hoyoverse".
 The projects with their own art (original games) have simple pixel or HTML
-reveals that are weaker than the current beta. Copying either kind of code
+reveals that are weaker than the current gacha wish. Copying either kind of code
 would give us one of two things: a `<video>` player that needs copyrighted
 footage, or an animation worse than what we already render.
 

renderer/plans/reports/researcher-261001-1703-code-built-gacha-animation.md

@@ -47,7 +47,7 @@ The risks, roughly in order of severity:
   clip length, or renders would have to run with concurrency 1.
 - **Rendering speed.** The server has no GPU. WebGPU will fall back to WebGL2
   on SwiftShader, which is likely several times slower than our CSS frames.
-  The current beta already takes about 15s at 854px and 30fps against the
+  The gacha wish at the time already took about 15s at 854px and 30fps against the
   15s timeout.
 - **Maturity.** Version 0.1.0, first published this week, pinned to one three
   release (r186), and the API can still change.
@@ -60,7 +60,7 @@ The risks, roughly in order of severity:
 1. **Prototype one shot with rollshade.** Render the meteor and impact shot in
    a separate composition, measure the render time on this server, and check
    frame determinism before committing to a rewrite. About one session of
-   work, with no changes to `/api/gachabeta` until it proves out.
+   work, with no changes to `/api/gacha` until it proves out.
 2. **Keep our own code and borrow techniques.** Port ideas such as rollshade's
    seeded variations, bloom-like layering, and impact timing into the existing
    CSS and canvas renderer. No new dependencies, and no render-time risk.

renderer/test/gacha-route.test.js

@@ -157,14 +157,4 @@ describe('POST /api/gacha', () => {
 
     await app.close();
   });
-
-  test('the retired beta path is gone', async () => {
-    const app = await build();
-
-    const response = await app.inject({method: 'POST', url: '/api/gachabeta', payload: {label: 'Pizza', rarity: 5}});
-
-    expect(response.statusCode).toBe(404);
-
-    await app.close();
-  });
 });