* 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>
Correct the regex in the Docker deployment workflow to properly validate environment variable placeholders. Additionally, update the staging environment configuration by adding specific keys and values for Tencent Cloud services, ensuring proper setup for deployment.
Add retries for ssh-keyscan and fall back to non-strict host checking for transient network failures so reruns do not fail early before deployment steps.
Co-authored-by: Cursor <cursoragent@cursor.com>
- Allow life_echo_20260313_182756.sql under api/backups via .gitignore exception
- Legacy migrate workflow: checkout, verify file, scp to server before migrate
- Point docker-build-deploy readers to one-shot legacy workflow
Made-with: Cursor
* fix/ 0:00 audio ui
* fix/ persist memoir image state and collapse voice history
Keep generated chapter images from staying in processing after successful uploads, and restore segmented voice recordings as a single audio message when reopening conversations.
Made-with: Cursor
* fix/ persist local conversation state and stabilize voice UI
Keep CreateMemory conversations driven by Room so recent text and audio survive page exits, and prevent stale 0:00 voice bubbles while list ordering follows the latest local message time.
Made-with: Cursor
* fix/ server-side root cause for conversation list time and message timestamps
- Add Conversation.last_message_at column with migration and index
- Update last_message_at on text message, audio segment, and AI response
- Sort conversation list by COALESCE(last_message_at, started_at) DESC
- Return real per-message timestamps from Redis history instead of now()
- Pass user_message_timestamp through agent pipeline to avoid LLM delay skew
- Remove all debug logging from server, client, and CI workflow
- Restore import json in conversation_agent (was broken by debug removal)
- Client: remove DebugRuntimeLogger, stop sending transcript as text message
Made-with: Cursor
---------
Co-authored-by: Kevin <kevin@brighteng.org>
