fix: switch kuaishou route from HTML scraping to GraphQL API

[RyoSXu]

Summary

The kuaishou route was relying on scraping the __APOLLO_STATE__ data embedded in the HTML homepage. Kuaishou has changed their page structure and the visionHotRank data is no longer present in the initial HTML, causing the route to fail with 快手页面结构变更 errors.

This PR replaces the HTML scraping approach with a direct GraphQL API request to https://www.kuaishou.com/graphql using the visionHotRank query, which still returns the hot ranking data reliably.

Changes

• Replace get() HTML request with post() GraphQL request
• Remove APOLLO_STATE parsing logic (~50 lines of fragile JSON extraction)
• Simplify KuaishouHotItem interface for GraphQL response shape
• Add fallback search URL when photoId is unavailable

Testing

• ESLint passes (0 errors)
• TypeScript compilation passes (tsc --noEmit)
• Prettier formatting passes
• Manual test: server returns 50 items with correct titles, hot values, and video URLs

GET /kuaishou -> 200 OK
Total: 50 items
FromCache: false

Fixes #127

[gemini-code-assist]

Code Review

This pull request refactors the Kuaishou route to fetch hot ranking data directly via a GraphQL POST request instead of scraping the HTML page and parsing the Apollo state. This significantly simplifies the data retrieval logic and types. The review feedback highlights two important improvements: throwing an error if the GraphQL response structure is missing or malformed to prevent silent failures, and wrapping decodeURIComponent in a try-catch block to prevent potential URIError crashes from malformed external URLs.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

If the GraphQL API response structure changes or the request fails, result.data?.data?.visionHotRank?.items will be undefined, and items will default to an empty array []. This causes the route to silently return an empty list (with a 200 OK status) instead of throwing an error, making it difficult to detect and monitor failures.

We should throw an error if the expected data structure is missing, similar to how the previous implementation handled structural changes.

  const items = result.data?.data?.visionHotRank?.items;
  if (!items) {
    throw new Error("快手接口返回数据格式异常，未找到 visionHotRank.items");
  }

[gemini-code-assist]

Calling decodeURIComponent directly on external data (item.poster) without error handling is risky. If Kuaishou returns a malformed URL containing an invalid percent-encoded sequence (e.g., a single % not followed by two hex digits), decodeURIComponent will throw a URIError and crash the entire request.

It is safer to wrap this in a try-catch block or use a safe decoding helper to ensure the route remains resilient.

    let poster: string | undefined;
    if (item.poster) {
      try {
        poster = decodeURIComponent(item.poster);
      } catch {
        poster = item.poster;
      }
    }