Enhance error handling, navigation, and theme management

[Sealt]

This pull request includes several improvements and adjustments across the codebase, mainly focusing on localization of user-facing messages, API parameter enhancements, UI consistency, and minor bug fixes. The most significant changes are grouped and summarized below.

Localization and User-Facing Message Updates:

• Changed error and toast messages throughout the app to use more concise and localized (Chinese) language, improving clarity and user experience. This affects API error handling (e.g., missing parameters) and various toast notifications in GPA calculator and group chat pages. [1] [2] [3] [4] [5] [6] [7]

API and Logic Enhancements:

• Updated authentication API methods to include new options (handleAuthFailure and silent) for more granular control over authentication behavior. [1] [2]

UI and Page Configuration Adjustments:

• Removed the enablePageMeta: true property from multiple page configuration files, likely for consistency or to address compatibility issues. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13]

Code and Logic Simplification:

• Simplified the useThemePage composable by removing unnecessary initialization logic, returning the theme store directly.
• Updated logic in final-review/detail to use Taro.getWindowInfo() instead of Taro.getSystemInfoSync() for obtaining window height, improving reliability.

UI Bug Fixes and Improvements:

• Fixed layout issue in the GPA calculator's scroll view by adjusting padding and structure for better display. [1] [2]

These changes collectively improve localization, user experience, code maintainability, and UI consistency across the application.

[gemini-code-assist]

Code Review

This pull request introduces several improvements to the application, including the removal of redundant page meta configurations, the simplification of user-facing toast messages, and the cleanup of theme store actions. It also introduces a new errorMessage utility to sanitize technical errors and a safeNavigateBack helper to prevent navigation issues when the history stack is empty. Additionally, modern Taro APIs like getWindowInfo and getAppBaseInfo are adopted. Feedback on these changes suggests passing the original error message to expireToken() in request.js to preserve user-friendly server messages, and wrapping Taro.getWindowInfo() in a try-catch block with a fallback to ensure compatibility with older WeChat clients.

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]

Calling expireToken() without any arguments discards finalError?.message entirely. This means the user will always see the default '请重新登录' toast, even if the server returned a specific, user-friendly message (e.g., '您的账号在其他设备登录').

By passing finalError?.message to expireToken(), we allow normalizeExpireTokenTitle to sanitize and display the specific message if it is not a technical error, while still falling back to '请重新登录' if it is technical or empty.

Suggested change

	useAuthStore().expireToken()
	useAuthStore().expireToken(finalError?.message)

[gemini-code-assist]

Calling Taro.getWindowInfo() directly without a try-catch block or a fallback check can cause runtime crashes on older WeChat clients or non-WeChat platforms where this API is not supported.

To ensure maximum compatibility and robustness, wrap the call in a try-catch block and fall back to Taro.getSystemInfoSync() or a default value if Taro.getWindowInfo is unavailable.

    let windowWidth = 375
    try {
      if (typeof Taro.getWindowInfo === 'function') {
        windowWidth = Taro.getWindowInfo().windowWidth || 375
      } else if (typeof Taro.getSystemInfoSync === 'function') {
        windowWidth = Taro.getSystemInfoSync().windowWidth || 375
      }
    } catch (error) {
      console.warn('Failed to get window width:', error)
    }
    chartWidth.value = Math.max(280, Math.floor(windowWidth - 56))