[roomote-community]

​Opened on behalf of @mrubens. Follow up by mentioning @roomote, in the web UI, or in Discord.

Related issue

Scheduled daily documentation accuracy audit; no linked issue.

Why this PR exists

• A maintainer explicitly invited this PR in the linked issue or discussion
• I am a maintainer / this is internal Roomote work

What changed

Qualify GPT-6.1 Terra and Kimi K3.1 Pro/Highspeed guidance as starting in Roomote 1.19.4. The provider routes and usage instructions already match the integration implementation.

Why this change was made

The exact audit window, 2026-10-26T03:00:36.611Z through 2026-10-27T03:00:36.611Z, contains three develop squash integrations: #3595 (7c70e13c, Terra), #3596 (62112eb0, Kimi), and #3597 (eb9dc4b4, 1.19.4 preparation and provider-icon docs repairs). Fresh non-shallow history, first-parent and all reachable develop/main history, and fully paginated GitHub closed-PR records corroborate this coverage. No main promotion occurred in the window.

At audit time, main and the latest published v1.19.3 release remain b532d7eb7e8cc672c7e0ea7527f8de67809462d6; develop and the frozen 1.19.4 candidate are eb9dc4b46d9deae3df13946eb4f873f86f4056af, with promotion #3598 still open. The unqualified availability statements could mislead operators on 1.19.3. A durable version boundary remains accurate after promotion.

Impact

Documentation-only clarification in apps/docs/models.mdx. Audited recommended/provider model catalogs, Kimi runtime definitions, ChatGPT allowlist/Fast mode, Terra role-only runtime registration, unchanged defaults, provider pages, and #3597's docs asset changes. Existing pending docs PRs were checked; the models-page edits in #3594 and #3515 address different paragraphs and do not supply these version qualifiers. Their pending fixes were not copied.

How it was tested

• mise exec -- pnpm --filter @roomote/docs check: passed pinned Mintlify 4.2.650 validation and internal broken-link checking.
• mise exec -- pnpm --filter @roomote/docs check-cookbook-index: passed; seven recipes, no generated drift.
• git diff --check: passed.
• Genuine local Mintlify preview: both revised passages rendered and both exact final screenshots were opened and visually inspected; independent proof review confirmed the claims and byte-identical proof/delivery diffs. Preview required one restart after validation disturbed generated build files.
• Normal pre-push hooks passed: oxlint, residual web/worker ESLint, all 27 typecheck tasks, and Knip. Commit-time Judgement returned incomplete for two prose rules because no supported Jev provider was configured; commit and push were allowed. This is not a successful automated prose judgment and a full judgment remains required before merge.
• Full Vitest and formatting-inclusive pnpm lint / pnpm check-types were not run for this two-statement docs change. No paid inference, production rollout, or public-doc publication revision was independently exercised. This audit covers the exact merge window, not a fresh certification of the entire docs corpus.

Checklist

• The PR title follows the repo convention: [Fix], [Feat], [Improve], [Refactor], [Docs], or [Chore] followed by a user-facing description
• This PR is small and scoped to one change
• pnpm lint and pnpm check-types pass locally
• I added tests or included a clear manual validation note above
• I removed secrets, tokens, private keys, and customer data from code, logs, and screenshots
• If this change should appear in the changelog, I ran pnpm changeset

No changeset needed for this documentation-only clarification.

Screenshots

Genuine local Mintlify desktop rendering without mocks or simulated state. These show both version qualifiers, not live provider access or deployed-release availability; mobile and dark theme are not pictured.

[roomote-community]

No code issues found. Reviewed both version qualifiers in apps/docs/models.mdx against the model additions, release history, and 1.19.4 changelog; the stated boundary is consistent. Current-head docs validation, lint, typecheck, and tests passed in CI; Docker build and JavaScript/TypeScript CodeQL analysis were still running when checked. See session

_{Reviewed 6e3add9}