Allow "max" option for "reasoningEffort" field in config schema

[Arcadi4]

Listing "max" as a valid value for "reasoningEffort" as many providers are accepting this value (e.g., DeepSeek-V4 and Claude Opus).

---

^{Need help on this PR? Tag @codesmith with what you need.}

• Let Codesmith autofix CI failures and bot reviews

[github-actions]

All contributors have signed the CLA. Thank you! ✅
_{Posted by the CLA Assistant Lite bot.}

[Arcadi4]

I have read the CLA Document and I hereby sign the CLA

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4c6fd2e5a8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[cubic-dev-ai]

1 issue found across 1 file

Confidence score: 3/5

• There is a concrete compatibility risk: assets/oh-my-opencode.schema.json now allows reasoningEffort: "max", but runtime mapping still tops out at xhigh, so valid-by-schema configs may fail or be ignored during resolution.
• Given the 5/10 severity with high confidence (9/10), this is a moderate regression risk that can affect users supplying the new value, so this is not fully low-risk yet.
• Pay close attention to assets/oh-my-opencode.schema.json - keep schema and runtime reasoning-effort mapping aligned so max is handled consistently.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="assets/oh-my-opencode.schema.json">

<violation number="1" location="assets/oh-my-opencode.schema.json:132">
P2: Schema accepts `reasoningEffort: "max"` but runtime compatibility/mapping still only supports up to `xhigh`, so configs using `max` will be dropped or rejected during resolution.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

0 issues found across 5 files (changes from recent commits).

_{Auto-approved: Additive change to reasoningEffort enum and compatibility ladder; no existing logic is modified in a way that could cause regressions.}