Fix English language filter — non-English stories still showing

[realproject7]

Summary

When selecting "English" language filter on the home page (`?tab=new&lang=English`), non-English stories still appear.

Verified Data (NOT a data issue)

Supabase `storylines` table has correct values:

• ID 34-37: `language = 'English'`
• ID 38: `language = 'Korean'`
• ID 39: `language = 'Japanese'`
• ID 40: `language = 'Chinese'`
• ID 41: `language = 'Spanish'`
• ID 42: `language = 'French'`

Code (looks correct but doesn't work)

`src/app/page.tsx` line 126: `if (lang !== "all") filtered = filtered.eq("language", lang);`

Investigation Required

T3 must debug this via actual browser testing on plotlink.xyz:

1. Check if it's a Vercel cache issue — try adding a cache-busting query param or check if the server is returning stale HTML. Check the Vercel deployment timestamp vs migration timestamp.

2. Check the actual Supabase query — add temporary logging to see what query is being executed when `lang=English` is set. Verify the `STORY_FACTORY` env var value matches the DB's `contract_address`.

3. Check if the page is actually server-rendering with the filter — view page source for `?tab=new&lang=English` and check if the HTML contains non-English stories (SSR issue) or if they're injected client-side (hydration issue).

4. Also investigate: the screenshot shows some stories as "UNCATEGORIZED" with "1 plot" — but DB shows genres set and 3-4 plots. Could be stale rendering or additional orphan records.

5. Test all language filters: English, Korean, Japanese, Chinese, Spanish, French, All

Fix

Once root cause is found, fix and verify on plotlink.xyz with browser testing.

Acceptance Criteria

• English filter shows ONLY English stories (IDs 34-37)
• Each language filter shows only stories in that language
• Root cause identified and documented
• Verified on plotlink.xyz

[realproject7]

Fixed. Root cause: orphan storylines 25-33 (first E2E attempt, wrong content hashes) kept being re-indexed by backfill cron since they exist on-chain on the same v4b contract. Deleting them was ineffective — cron re-created them. Fix: set hidden=true for IDs 25-33. PR #559 also removed stale revalidate=120 from homepage.