[backryun]

Summary

• refresh the built-in maritalk catalog to the current general model lineup
• add sabia-4-thinking
• remove the discontinued sabia-3.1 and sabiazinho-3 entries
• intentionally exclude the regional *-br-sp variants
• add a focused registry regression test that locks the exact public catalog

Why

Maritaca's platform now lists the Sabiá 4 family and reports that sabia-3,
sabia-3.1, and sabiazinho-3 were discontinued on July 16, 2026. OmniRoute's
static catalog still exposed two of those retired models and did not expose
sabia-4-thinking.

This left the provider model picker and other registry consumers out of sync
with the provider's current lineup.

User and developer impact

The built-in maritalk catalog now exposes exactly:

• sabia-4
• sabia-4-thinking
• sabiazinho-4

This is a catalog-only update. It does not change Maritalk authentication,
request translation, executor selection, base URLs, endpoint construction,
provider IDs, schemas, or persisted connection data.

The removed entries were already discontinued upstream. The regional
sabia-4-br-sp, sabia-4-thinking-br-sp, and sabiazinho-4-br-sp variants
remain intentionally unadvertised.

Validation

• node --import tsx/esm --test tests/unit/maritalk-model-catalog.test.ts
• node --import tsx/esm --test tests/unit/provider-validation-specialty.test.ts
  • 122 tests passed
• npm run check:provider-consistency
• npm run lint
• npm run typecheck:core
• npm run check:file-size
• commit hooks, including Prettier, ESLint, documentation sync, explicit-any
  budget, and tracked-artifact checks

[diegosouzapw]

Validated in local merge-train /tmp/train1d-20260727-090022-suite.log on .113 @ 029cdf4215cf465f0e1716ac9f84a84692b1e881 (full unit suite green on CI-equivalent host)