Fix Azure auth + retire Gemini defaults
Auth
- Backend pinned the v2.0 issuer but the Entra API app was still on v1
tokens (accessTokenAcceptedVersion=null), so every real MSAL token
failed jwtVerify with 'Invalid or expired token'. The API app has now
been flipped to v2 in Azure (Graph PATCH api.requestedAccessTokenVersion).
Models
- Default main/title/tabular models switched from Gemini to OpenAI
equivalents that work with the Azure-managed OPENAI_API_KEY:
main -> gpt-5.5
title -> gpt-5.4-nano
tabular -> gpt-5.4-mini
- user_profiles.tabular_model column default updated in both schema files
(azure_postgres_schema.sql, 000_one_shot_schema.sql) and ALTERed in the
live database.
- Frontend fallbacks in ModelToggle, UserProfileContext, account/models
page, TRChatPanel, and TabularReviewView updated accordingly.
- Gemini stripped from the assistant + tabular model dropdowns and from
the API Keys section of the account/models page; ModelOption.group
type tightened to 'OpenAI' | 'Anthropic'.
- resolveTitleModel now prefers the server-managed OpenAI key, then a
user Claude key, then a user Gemini key (was Gemini-first).
| Repository | Cpodlaskilegal/mike |
|---|---|
| Author | Cpodlaskilegal <christopher@podlaskilegal.com> |
| Authored | |
| Parents | 6b1b4a53 |
| Stats | 10 files changed , +28 , -111 |
| Part of | OpenAI model provider and default-model switch |
Capture this commit into my fork
Download a Markdown prompt that tells Claude how to port this
exact commit into your working tree. Run it via
claude -p < capture-commit-2d0a0e10.md
from inside the repo you want the change in.