105b50a277
* feat(api): implement Google OAuth login and user management - Added Google OpenID Connect login functionality, allowing users to authenticate using their Google accounts. - Created new endpoints for Google login, including user registration and linking existing accounts. - Introduced Google token verification logic and error handling for authentication failures. - Updated environment configuration to include Google OAuth client IDs and verification settings. - Enhanced user model to support OpenID and linked Google accounts. This feature improves user experience by enabling seamless sign-in with Google, while maintaining security and integrity of user data. * fix(auth): wire staging Google token verifier * chore(deps): update expo to version 55.0.6 and adjust @expo/env dependency in pnpm-lock.yaml * chore(deps): update Babel dependencies to version 7.29.7 in package-lock.json * feat(auth): enhance phone login for China users - Updated phone login functionality to support only mainland China (+86) mobile numbers. - Added user prompts and descriptions for phone login, including confirmation and cancellation options. - Adjusted translations for both English and Chinese to reflect the new phone login requirements. - Updated Google OAuth client IDs in configuration files for production and staging environments. * chore(deps): add peer flag to use-sync-external-store in package-lock.json * chore(deps): add @emnapi/core and @emnapi/runtime to package-lock.json * fix(app-expo): align Android native dependencies * fix(app-expo): normalize lockfile for npm 10 * fix(config): update environment variable handling to use static access - Introduced a static mapping for public environment variables to ensure proper access during the release bundle. - Updated the `requirePublicEnv` and `optionalPublicEnv` functions to reference the new `PUBLIC_ENV` object instead of directly accessing `process.env`. - Added comments to clarify the necessity of static access for certain environment variables. * feat(app-expo): dark mode, FAQ i18n, eval ASR, and theme cleanup (#34) * feat(app-expo): dark mode, FAQ i18n, version CI, and theme cleanup Implement light/dark scene colors across chat, reading, and headers; remove default/brand theme picker and ThemeVariablesProvider. Localize FAQ in-app, fix dark-mode text visibility, and remove the unused /api/faqs endpoint. Align About/version with Expo config and inject APP_VERSION in CI builds. Also includes phone E164 auth/SMS updates, eval ASR page, and related API work. * revert: remove phone E.164 changes from dark-mode branch These auth/SMS internationalization updates were accidentally bundled into the dark-mode commit; restore 11-digit CN phone flow and drop related API, migration, and Expo UI work from this branch. * fix: address PR review issues for dark mode and eval ASR Use light foreground colors for sepia reading in dark mode, fix chat send button contrast, stream-limit eval ASR uploads, restore LiveTester phone validation, and remove unused AudioSegmenter code. * fix(app-expo): improve chat send button contrast in light and dark mode Add dedicated send button colors (accent fill in dark, primary fill in light), use RNText to avoid NativeWind overrides, and restore dark labels in light mode for readable composer actions. --------- Co-authored-by: Kevin <kevin@brighteng.org> --------- Co-authored-by: penghanyuan <penghanyuan@gmail.com> Co-authored-by: Kevin <kevin@brighteng.org>
内部评测 Web（Life Echo）
独立 Vite + React 控制台，对接 app.internal_main:internal_app。路由含 Playground（分步测评）、Memoir、Memoir · Stories、实机联调（#live，主站 JWT + WS）。
部署范围（重要）
本目录 仅用于本地开发：在开发者机器上 npm run dev，依赖 Vite 将 /internal、/api、/ws 代理到本机后端。不提供生产或预发环境的 Docker 镜像，不随 api/docker-compose.yml 部署到 Staging/Production；切勿将 dist/ 或自建镜像发布到线上。
环境变量
VITE_EVAL_API_BASE— 内部评测 API 根（可选；开发留空则走 Vite 代理，默认:7999）VITE_EVAL_API_KEY— 与后端INTERNAL_EVAL_API_KEY相同VITE_MAIN_API_BASE/VITE_MAIN_API_PROXY_TARGET— 实机联调用主站 API（见api/docs/internal-eval.md）
开发
npm install
VITE_EVAL_API_BASE=http://127.0.0.1:7999 VITE_EVAL_API_KEY=your-secret npm run dev
浏览器打开提示的端口（默认 5174）。仓库根目录亦可：npm run eval-web。
生产构建（仅限本地检查，非部署产物）
npm run build 仅可用于本地验证 TypeScript/打包是否通过；不作为预发/生产发布步骤。正式联调请始终使用 npm run dev（以便代理与热更新）。
对话流式评审使用带 X-Internal-Eval-Key 的 fetch（见 api/docs/internal-eval.md）。