fix(workflow): map gemini-3-pro and sonnet-4-1 to their page rows

The registry prices both models from rows shared with siblings, but the
mapping only listed one key per row, so the monitor flagged them
MISSING_FROM_PAGE every run:

- 'Gemini 3.0 Pro, 3.1 Pro' also prices databricks-gemini-3-pro
- 'Claude Sonnet 4' also prices databricks-claude-sonnet-4-1

Verified against upstream/staging values: all four entries match the
page list rates (35.714/214.286/3.571 and 42.857/214.286/4.286 DBU).
This commit is contained in:
leecoder 2026-09-08 14:27:15 +09:00
parent d7317b9d7d
commit a0f5dda44e

View file

@ -116,9 +116,9 @@ LABEL_TO_KEYS: Dict[str, List[str]] = {
"databricks-claude-sonnet-4-5",
"databricks-claude-sonnet-4-6",
],
"claude sonnet 4": ["databricks-claude-sonnet-4"],
"claude sonnet 4": ["databricks-claude-sonnet-4", "databricks-claude-sonnet-4-1"],
"claude haiku 4.5": ["databricks-claude-haiku-4-5"],
"gemini 3.0 pro, 3.1 pro": ["databricks-gemini-3-1-pro"],
"gemini 3.0 pro, 3.1 pro": ["databricks-gemini-3-1-pro", "databricks-gemini-3-pro"],
"gemini 2.5 pro": ["databricks-gemini-2-5-pro"],
"gemini 3.7 flash, 3.8 flash": [
"databricks-gemini-3-7-flash",