v0.2.0-beta - fix VS Code --max-thinking-tokens + process-wrapper

Fixes empty thinking summaries on the official Claude Code VS Code extension (2.1.16x).

The extension changed the VS Code launch path: it now signals a real run with
--max-thinking-tokens (not --thinking adaptive) and launches a configured
claudeCode.claudeProcessWrapper with the real CLI as a leading argument. The
previous launcher recognized neither, so the Thinking section rendered empty again.

This build of claudemax.exe:

• Injects --thinking-display summarized when it sees --max-thinking-tokens
  (nonzero), --thinking adaptive/enabled, or -p/--print.
• Consumes the leading real-binary path the official extension passes
  (process-wrapper convention).

Setup: set claudeCode.claudeProcessWrapper (official "Claude Code" extension) or
claudeCodeChat.executable.path (third-party "Claude Code Chat") to the full path
of claudemax.exe, then reload the VS Code window. In a multi-root .code-workspace,
put claudeCode.claudeProcessWrapper in the workspace settings block or User
settings, not a folder's .vscode/settings.json.

Confirmed on extension 2.1.169 (native-binary CLI) on Windows 11 and Ubuntu.