fix(windows): use absolute path with shell:false for Claude spawn

[tw23]

On Windows, spawning Claude with shell: true causes the process to exit immediately with code 1. This happens because shell: true invokes cmd.exe /c claude , and cmd.exe's PATH resolution differs from direct process creation, leading to environment inconsistencies.

This fix:

• Adds findWindowsClaudePath() to locate claude.exe absolute path
• Changes spawn to use absolute path with shell: false on Windows
• Maintains Unix behavior (command name works fine with shell: false)
• Adds HAPI_CLAUDE_PATH env var for user override

Tested on Windows 11 with Claude Code v2.1.29 and hapi v0.15.0.

[github-actions]

[MINOR] [CLEANUP] MCP config cleanup can be skipped on early failure

Why this is a problem: getDefaultClaudeCodePath() can throw before the try/finally, so cleanupMcpConfig never runs. On Windows this can leave a mcp-config-*.json file with server config in the project dir.

Suggested fix:

try {
    const claudeCommand = getDefaultClaudeCodePath()
    logger.debug(`[ClaudeLocal] Using claude executable: ${claudeCommand}`)
    await spawnWithAbort({ command: claudeCommand, args, /* existing options */ })
} finally {
    cleanupMcpConfig?.()
    process.stdin.resume()
    restoreTerminalState()
}

[github-actions]

Findings

• [Minor] MCP config cleanup can be skipped if Claude path resolution fails before the try/finally in cli/src/claude/claudeLocal.ts:89. Suggested fix: move getDefaultClaudeCodePath() into the try block so cleanup always runs.

Testing

• Not run (automation)