Allow Claude Code plugin to use a remote PowerMem server

[wayyoungboy]

Summary

• Add remote initialization for the Claude Code plugin via POWERMEM_INIT_REMOTE_BASE_URL.
• Support hook, mcp, and both connection modes with optional POWERMEM_INIT_REMOTE_API_KEY.
• Keep local initialization unchanged by default while documenting the remote setup path.

Details

• Remote mode writes runtime.env and/or .mcp.json without generating a local backend .env, starting uvx, or managing a local PID.
• runtime.env values are shell-quoted so API keys and URLs with shell-sensitive characters can be sourced safely.
• Re-running init from an existing remote runtime remains in remote mode and preserves the configured mode/API key.
• Status output now distinguishes local and remote connection modes and marks Python/uv as not required for remote mode.

Closes #1103

Validation

• sh -n apps/claude-code-plugin/scripts/common.sh && sh -n apps/claude-code-plugin/scripts/init.sh && sh -n apps/claude-code-plugin/scripts/status.sh && sh -n apps/claude-code-plugin/hooks/run-hook.sh
• python -m pytest tests/unit/test_claude_plugin_uv_install.py tests/regression/test_claude_hook_privacy_e2e.py::test_windows_launcher_imports_runtime_env_files_with_quoted_values
• Temp-dir script E2E with a live local health endpoint covering remote both init, .mcp.json, shell-safe runtime.env, status, hook invocation, mcp-only hook skip, and no local uvx startup.

[wayyoungboy]

Closing this focused draft in favor of #1101, which now carries the broader remote-init work. The remaining review should continue there.