Skip to content

Conversation

@ILindsley
Copy link
Collaborator

Please include the language instructions in the PR body. Follow the rules in the instructions.

Allow GPT classification + preferences to keep arbitrary ISO 639-1 language
codes by relaxing the core language models, removing the whitelist gates
across intents, and updating downstream helpers/tests.

- Added normalization + friendly-name helpers so ResponseLanguage and
  TranslatedPassage accept any ISO code while keeping 'other' sentinel support
- Refreshed translation/settings/passage/FIA handlers, response pipeline, and
  passage follow-ups to use the helpers instead of the 10-language list
- Extended tests to cover the unrestricted flow (including Turkish) and
  stubbed translations where needed to avoid real API calls

Test Plan:
- scripts/check_repo.sh
Introduce a `clear-response-language` intent so users can revert to the
message-language fallback while keeping the existing set intent for explicit
preferences.

- Added normalization-friendly request/handler wiring plus a TinyDB adapter
  helper/port method to persist clearing and exposed a new LangGraph node that
  shares the translation pipeline edge
- Updated intent classification prompts, follow-up questions, continuation
  prompts, capability docs, performance tracing map, and priority/node
  mappings to recognize the new intent
- Extended tests across adapters, follow-up plumbing, and new settings-specific
  unit coverage to validate clearing behavior and keep the test stubs aligned

Test Plan:
- scripts/check_repo.sh
Highlight the assistant's multilingual support inside the help context so
system-info responses can explicitly address "Which languages do you support?"
type prompts.

- Embedded a language-capabilities block into the help agent instructions so
  RETRIEVE_SYSTEM_INFORMATION responses mention broad language coverage and
  proficiency caveats

Test Plan:
- scripts/check_repo.sh
Raise the package version constant for the next release.

Test Plan:
- Not run (version bump only)
@IanLindsley IanLindsley merged commit 1896ddf into main Nov 14, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants