#8264 chore: bump pitchfork and Node.js, scope pitchfork MCP to the project

Summary

• Bump pitchfork from 2.22.0 to 2.32.4 in mise.toml, with refreshed checksums and release URLs in mise.lock for every platform.
• Run the pitchfork MCP server as pitchfork mcp --local in every harness config: .mcp.json (Claude Code, and Cursor through the .cursor/mcp.json symlink), .codex/config.toml, and opencode.json.
• Update the pitchfork skill so it says the MCP tools are scoped to the current project and points to the CLI for other projects.
• Bump Node.js from 24.22.1 to 24.22.2, the latest 24.x LTS, in mise.toml and .node-version, and relock every platform. Lockfile checksums match the published SHASUMS256.txt.
• The Node linux-arm64-musl lock entry goes back to the prebuilt unofficial-builds tarball instead of building from source. #7815 locked it before that tarball was published.

Motivation

Each worktree runs its own stack under one shared pitchfork supervisor. Without --local, an agent's MCP server sees and can start, stop, or restart daemons from every worktree on the machine. --local (new in 2.32.x) limits it to the project of the agent's working directory. Requests for daemons in another project return an error, and a start or restart can no longer reach another project through a dependency.

The Node patch bump keeps the local toolchain on the current LTS release.

🤖 Generated with Claude Code