[BUG] Plugin installer still resolves wrong home directory on macOS (regression/unresolved)

Description

Plugin installation fails on macOS because the installer resolves the home directory as /home/node/ instead of the actual $HOME (/Users/<user>/).

This was previously reported and closed, but the bug is still present on the latest version.

Steps to Reproduce

1. Open Claude Code on macOS
2. Run /plugin
3. Select frontend-design from claude-plugins-official
4. Attempt to install

Expected Behavior

Plugin installs successfully using the correct path:

/Users/<user>/.claude/plugins/marketplaces/claude-plugins-official/plugins/frontend-design/

Actual Behavior

Error: Failed to install: Source path does not exist: /home/node/.claude/plugins/marketplaces/claude-plugins-official/plugins/frontend-design

The plugin files exist on disk at the correct macOS path. The installer is resolving to /home/node/ — likely leaked from the build environment — instead of the actual home directory.

Environment

• OS: macOS Darwin 24.6.0 (arm64)
• Claude Code: v2.1.69, installed via Homebrew (/opt/homebrew/bin/claude)
• Shell: zsh
• Note: I have a non-default CLAUDE_CONFIG_DIR configured (set via shell alias). The plugin marketplace is cloned under the default ~/.claude/plugins/ path, which may be relevant if the installer is resolving paths relative to CLAUDE_CONFIG_DIR or the build-time home rather than the actual $HOME.

Previous Reports

This is a re-report of the same underlying bug:

• #16844 (root issue, now closed and locked)
• #24851 (duplicate, closed)
• #26463 (duplicate, closed)
• #18459 (duplicate, closed)

Note that the incorrect path prefix varies across reports (/home/claude/, /home/node/), suggesting it is being pulled from the build environment rather than a single hardcoded value.