[gamebody]

Summary

The MiniMax-H3 API accepts resolution values 768P and 2K, but the CLI and SDK only allowed 2K. This adds a --resolution flag to mmx video generate and accepts 768P in the SDK.

mmx video generate --model MiniMax-H3 --prompt "..." --resolution 768P

API docs: platform.minimax.io, platform.minimax.cn

Behavior

Input	Result
--resolution 768P or 2K	Sent in the request body
Flag omitted	Still sends 2K, so existing usage is unchanged
Any other value, including lowercase 768p	Usage error (exit 2), no generation request sent
Used with a legacy model	Usage error (exit 2)

Both SDK request forms (prompt and content) accept 768P. Help text, README.md, README_CN.md, and the H3 skill are updated.

Scope

• Only MiniMax-H3 changes. Other H3 variants and legacy models are not touched.
• Validation still runs after region detection in src/main.ts, as it does for --ratio and --duration. With no cached region and a failed detection, an invalid value reports the network error instead of the usage error. No generation request is sent in that case.

Testing

• bun run typecheck passes.
• bun run lint reports 0 errors. Its one warning is in test/sdk/speech.test.ts, which this PR does not touch.
• bun test: 618 pass, 1 fail. The failure is test/agent/zed.test.ts (honors XDG_CONFIG_HOME), which also fails on main locally.
• Checked src/main.ts with --dry-run for 768P, the default, an invalid value, and a legacy model.
• Not tested against the live API: no real 768P video has been generated.

🤖 Generated with Claude Code

---

^{Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.}