MAJOR_HF_ORGS: "minimaxai" casing bug — HF API returns empty for lowercase slug

[SovereignSignal]

Found during the 2026-06-22 supervisor audit. Same class of bug as #24 (inclusionai → inclusionAI).

Bug

MAJOR_HF_ORGS lists the org as "minimaxai" (all-lowercase), but the HuggingFace models API is case-sensitive for the author parameter. Verified live:

GET https://huggingface.co/api/models?author=minimaxai  → []  (empty)
GET https://huggingface.co/api/models?author=MiniMaxAI  → 5 models returned

Models returned with correct casing (MiniMaxAI):

• MiniMaxAI/MiniMax-M3 — active as of 2026-06-22 (frontier-scale 428B/23B MoE)
• MiniMaxAI/MiniMax-M3-MXFP8 — 2026-06-15
• MiniMaxAI/MiniMax-M2.7 — 2026-04-20
• MiniMaxAI/MiniMax-M2.5 — 2026-03-10
• MiniMaxAI/MiniMax-M2.1 — 2026-02-13

fetch_org_models("minimaxai") currently returns nothing, so fetch_major_orgs() silently skips MiniMax on every fallback run.

Workaround applied this run

The supervisor added "MiniMaxAI" as a pure addition (commit 6052d73) alongside the broken lowercase entry. This restores the fetch path. The duplicate "minimaxai" entry is now harmless (returns 0 from API) but should be cleaned up.

Fix required

In MAJOR_HF_ORGS, remove the incorrect lowercase entry:

"minimaxai",   # ← delete this (returns 0 from HF API)

The correct slug "MiniMaxAI" was added in the workaround commit.

Note: KNOWN_ORGS and PROVIDER_NAMES use lowercase keys because is_noise_model and _resolve_provider both call .lower() before lookup, so those entries are correct as-is.

See also

• MAJOR_HF_ORGS: "inclusionai" casing bug — HF API returns empty for lowercase slug #24 — same bug for inclusionai / inclusionAI (still open)
• Once both are fixed, the MAJOR_HF_ORGS list should be audited for any remaining case mismatches (audit scope listed in MAJOR_HF_ORGS: "inclusionai" casing bug — HF API returns empty for lowercase slug #24).