Brings Claude Code to parity with the Codex CLI integration.
- `omniroute launch` is now remote-aware: --remote <url>, --profile <name>,
--api-key. Resolves base URL + auth from the active context (so
`omniroute connect <vps>` then `omniroute launch` just works), accepts a bare
port OR a full base URL, health-checks the (possibly remote) server, and sets
CLAUDE_CONFIG_DIR for the chosen profile.
- `omniroute setup-claude` (new): fetches the live /v1/models catalog and writes
~/.claude/profiles/<name>/settings.json per model. Claude Code has no native
profile files, so CLAUDE_CONFIG_DIR is the idiomatic mechanism. Reuses the SAME
profile names as setup-codex (glm52, kimi-k27, …) via the shared categoriseModel
(now exported). The auth token is NEVER written to disk — launch injects it.
- Docs: docs/guides/CLAUDE-CODE-CONFIGURATION.md + README index. i18n (en + pt-BR).
- Tests: setup-claude profile generation (incl. "no token on disk"), buildClaudeEnv
(port + URL + CLAUDE_CONFIG_DIR), resolveLaunchTarget.
check:cli-i18n + check-docs-sync green; 13 unit tests pass.
3e6be47012