fix: Refresh model catalog from OpenAPI 0.32.3

[emmy-devop]

Requested by @wagnercosta

🔴 Review tier: HIGH — human review required

• Contract: refresh the public CLI model catalog from the deployed production OpenAPI schema; additive only.
• Release: merging this fix: PR updates the release-please Release PR; a human merging that Release PR publishes the npm CLI. No version bump, tag, release, or publishing performed here.
• Size: 38 files, predominantly generated schema/manifest/reference pages, plus focused regression tests.

What / why

Refresh the production schema from 0.32.1 to 0.32.3 using ASKNEWS_SCHEMA_URL=https://api.asknews.app/openapi.json pnpm sync:openapi.

• Add claude-sonnet-5-5 and gpt-6.1-sol from the authoritative model enum; the latest production schema also adds kimi-k3.
• Retain all 48 previous model IDs, including claude-opus-5-5 and gpt-6-sol (51 IDs total).
• Regenerate the CLI-owned command docs and embedded skill references without hand-editing generated files.
• Add schema-to-help/choices parity coverage for the full model catalog and mocked request-forwarding tests for the three additions and two specifically retained models, on both curated research and generated DeepNews commands.

PR #8 was already merged and v0.3.0 released; there were no open CLI PRs at inspection. This is based on current main 8d311678cfcde12a775d4767041f070ea3aed624, not the historical PR branch.

Source and complete contract delta

Source: https://api.asknews.app/openapi.json — first fetched 2026-10-05T23:03:12Z, version 0.32.3.

• Raw response SHA-256: 4d7eeec4435f4cfaf8bce613994a9ab9c201695fdc15df74133aeb76a46a430e
• Generated formatted snapshot SHA-256: 94bc7c87bbbb386e687787a73816f587073543c24c5394679c640a4b7ab7e8ec
• Parsed raw response and generated snapshot are deeply equal. The different byte hashes reflect JSON formatting/numeric serialization, not production drift.

The full semantic schema diff has exactly two changed paths: info.version and components.schemas.DeepNewsModel.enum (the three additive IDs above). All 43 HTTP operations and all 32 customer-facing generated commands remain unchanged: no added/removed/renamed operations, parameter or response changes, default/format/range changes, scope/auth changes, or safety classification changes. All generated operation definitions equal their previous values after removing only the three new model enum entries.

No fresh breaking removals are bundled. The September command removals are already on main and are not repeated here. search_news and live_web_search parameters are unchanged, so curated news/X include-lists, flags, MCP descriptions, and task recipes require no changes. All handwritten runtime commands, defaults, flags, dependencies, and workflows are untouched.

How tested

• Frozen-lockfile dependency install.
• Production pnpm sync:openapi and explicit OpenAPI/help/action contract tests: 32 passed.
• pnpm check: lint + strict typecheck + full coverage suite, 124 passed / 3 skipped (two guarded live tests and the opt-in 305-second local timeout wall-clock proof).
• pnpm build and pnpm package:tarball.
• Local tarball install with no PATH or agent-skill modifications; installed --version, root help, research help, generated DeepNews help, and local operation catalog smoke checks. Both help surfaces contain all five explicitly checked models. No paid/live API calls.
• npm pack --dry-run --json: package allowlist verified (only dist, skills, package metadata, README, LICENSE, and postinstall).
• npm publish --dry-run --json was attempted but npm 12.0.2 rejects the unchanged, already-published 0.3.0 version. No version bump or publish was attempted to work around this; the actual tarball install and pack checks pass.
• Committed-checkout pnpm sync:openapi:check, clean worktree, whitespace check, and whole-branch public-environment leak scrub.
• Head CI run passed both Node 22 lint/typecheck/test/build and Node 24 compatibility on c3d08871539a3286394bcb97aaf972642fad901f (completed 2026-10-05T23:07:26Z).

Risk / rollback / downstream dependency

Additive generated contract refresh; no source deployment blocker: both requested IDs are already in production OpenAPI. This verifies accepted model IDs, not account-specific availability or paid inference. Revert this PR to restore the previous pinned catalog.

Keep the fix: subject when squash-merging (repository is squash-only, configured for commit/PR title) so release-please ships the change. Human review/merge and the subsequent Release PR remain required; no automatic merge enabled. No CI/workflow changes.

Frontend documentation synchronization is intentionally deferred until this CLI change and its Release PR are merged and the npm release is published. It must be generated from that merged/released CLI main in a separate follow-up; no frontend MR was opened and no future execution is scheduled. SDK repositories are outside this PR's scope and were not touched.