bug: pathToClaudeCodeExecutable setting causes validation error in Claude Code configuration

[jujax]

Description

Fixed with #1172

The pathToClaudeCodeExecutable setting in Claude Code configuration is not included in the validation schema, causing legitimate configurations to be rejected with validation errors. This setting is a valid
Claude Code configuration option that allows users to specify a custom path to the Claude Code executable, but the current validation schema in config-manager.js doesn't recognize it.

Steps to Reproduce

1. Create a Claude Code configuration that includes pathToClaudeCodeExecutable, eg :

{
...
"claudeCode": {
      "pathToClaudeCodeExecutable": "/usr/local/bin/claude"
      }
...
}

3. Run Task Master with Claude Code integration enabled (e.g., task-master-ai - parse_prd)
4. The configuration validation will fail and reject the setting

Expected Behavior

The pathToClaudeCodeExecutable setting should be accepted as a valid configuration option without throwing validation errors, allowing users to specify custom paths to the Claude Code executable.

Actual Behavior

The configuration validation fails and rejects the pathToClaudeCodeExecutable setting because it's not defined in the BaseSettingsSchema in scripts/modules/config-manager.js:324.

Screenshots or Logs

  task-master-ai - parse_prd (MCP)(projectRoot: "/root/stellar-nights", input: ".taskmaster/docs/prd.txt", numTasks: "10",
                                    research: true)
    ⎿  Error: Claude Code API error during object generation: Claude Code executable not found at 
       /root/.npm/_npx/0726791833487271/node_modules/@anthropic-ai/entrypoints/cli.js. Is options.pathToClaudeCodeExecutable set?
       Version: 0.25.1
       Name: task-master-ai
       Current Tag: master

Environment

• Task Master version: 0.25.1
• Node.js version: 22.19.0
• Operating system: Linux 6.12.34+rpt-rpi-2712 chore(config): fix typos #1 SMP PREEMPT Debian 1:6.12.34-1+rpt1~bookworm (2025-06-26) aarch64 GNU/Linux
• IDE (if applicable): Claude Code

Additional Context

The fix is straightforward - adding pathToClaudeCodeExecutable: z.string().optional() to the BaseSettingsSchema object in the validateClaudeCodeSettings function. This aligns the validation schema with the
actual available Claude Code configuration options.