[Feature Request] Improve documentation adherence and consistency in extended reasoning mode

Bug Description
Not sure if you're able to see this converation in it's entirety, but Opus 4.6 with high thinking mode is producing awful results in trying to debug this Voron 3d printer right now. In general, it's not using and relying on documentation enough (even when explicitly told to do so), making assumptions and homebrew tests that don't actually make sense, and it's now just contradicting itself from turn to turn. I really feel like I'm just burning tokens for no reason with this convo, and I don't say this often about Claude Code.

Environment Info

• Platform: win32
• Terminal: windows-terminal
• Version: 2.1.80
• Feedback ID: e2aeb663-dad9-440e-9443-536e031873df

Errors

[{"error":"ZodError\n    at qe8 (B:/~BUN/root/src/entrypoints/cli.js:4311:253)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-03-20T03:37:53.200Z"},{"error":"AxiosError: Request failed with status code 404\n    at yx (B:/~BUN/root/src/entrypoints/cli.js:74:1194)\n    at <anonymous> (B:/~BUN/root/src/entrypoints/cli.js:79:12775)\n    at emit (node:events:92:22)\n    at endReadableNT (internal:streams/readable:861:50)\n    at processTicksAndRejections (native:7:39)\n    at request (B:/~BUN/root/src/entrypoints/cli.js:81:2467)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-03-20T17:32:46.564Z"}]