feat(stage-pages): add model selection navigation after provider validation

[Minnzen]

Description

After configuring an LLM provider (entering API key/base URL) and seeing validation success, users have no clear path to select a model — making chat unusable until they manually find the consciousness module settings page.

This adds a "Select Model →" button inside the validation success alert that:

1. Sets the validated provider as activeProvider in the consciousness store
2. Navigates to the consciousness module page where models auto-load

Minimal change — no new components, just wiring existing stores (useConsciousnessStore) and a router push.

Changes

• packages/stage-pages/src/pages/settings/providers/chat/[providerId].vue — Import consciousness store, add goToModelSelection() function and button in success alert
• packages/i18n/src/locales/*/settings.yaml (9 locales) — Add goToModelSelection i18n key

Linked Issues

Related to the provider onboarding flow (#1058, #1144)

Additional Context

• The consciousness page already has watch(activeProvider, ..., { immediate: true }) that auto-loads models, so setting activeProvider + navigating is all that's needed
• markProviderAdded() is already called in useProviderValidation on success (PR fix(stage-ui): auto-mark provider as added after successful validation on settings page #1144), so the provider appears in the consciousness provider list
• Button uses :class array pattern with dark mode variants per project conventions (AGENTS.md)
• Tested on both web (pnpm dev:web) and iOS Capacitor (pnpm dev:pocket:ios)

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly improves the user experience for LLM provider onboarding by streamlining the post-validation process. Instead of requiring manual navigation, users are now guided directly from a successful provider setup to the model selection interface, ensuring a smoother and more intuitive workflow for configuring chat functionalities.

Highlights

• Enhanced Provider Validation Flow: After successfully validating an LLM provider, users are now presented with a "Select Model →" button within the success alert, providing a direct path to model selection.
• Automated Model Selection Setup: Clicking the new button automatically sets the validated provider as the "activeProvider" in the consciousness store and navigates the user to the consciousness module settings page, where models are then auto-loaded.
• Internationalization Support: A new internationalization key, "goToModelSelection", has been added across nine locales to support the text for the new navigation button.

Changelog

• packages/i18n/src/locales/*/settings.yaml
  • Added the "goToModelSelection" internationalization key to support the text for the new button across all supported languages.
• packages/stage-pages/src/pages/settings/providers/chat/[providerId].vue
  • Imported "useConsciousnessStore" to manage active LLM providers.
  • Initialized "consciousnessStore" and extracted "activeProvider" for state management.
  • Implemented "goToModelSelection" function to set the active provider and navigate to the consciousness module page.
  • Integrated a new "Select Model →" button into the provider validation success alert, which triggers the "goToModelSelection" function.
  • Applied styling to the new button using project conventions for dark mode variants.

Ignored Files

• Ignored by pattern: packages/i18n/src/** (9)
  • packages/i18n/src/locales/en/settings.yaml
  • packages/i18n/src/locales/es/settings.yaml
  • packages/i18n/src/locales/fr/settings.yaml
  • packages/i18n/src/locales/ja/settings.yaml
  • packages/i18n/src/locales/ko/settings.yaml
  • packages/i18n/src/locales/ru/settings.yaml
  • packages/i18n/src/locales/vi/settings.yaml
  • packages/i18n/src/locales/zh-Hans/settings.yaml
  • packages/i18n/src/locales/zh-Hant/settings.yaml

Activity

• No human activity has been recorded on this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a helpful navigation button to guide users to model selection after successfully validating a provider. The implementation is clean and follows existing project patterns. I've added one suggestion to make the navigation logic more robust by handling potential errors during routing.

[github-actions]

⏳ Approval required for deploying to Cloudflare Workers (Preview) for stage-web.

Name	Link
🔭 Waiting for approval	For maintainers, approve here

Hey, @nekomeowww, @sumimakito, @luoling8192, @LemonNekoGH, kindly take some time to review and approve this deployment when you are available. Thank you! 🙏