Harden shell scripts and fix stale docs from CodeRabbit review

- Replace eval tilde expansion with getent passwd lookup in all
  PR-scoped scripts (setup-auth, setup-migrate, ccstatusline,
  mcp-qdrant install + poststart hook) to prevent shell injection
  via SUDO_USER/USER environment variables
- JSON-escape auth token value before writing .credentials.json
- Create credential directory with umask 077 (was default 755)
- Fix mcp-qdrant chown to use resolved _USERNAME instead of
  hardcoded vscode or $(id -un)
- Update ccstatusline README verification commands to respect
  CLAUDE_CONFIG_DIR environment variable
- Sync docs site changelog with devcontainer CHANGELOG fixes
  (~/. claude path, remove "(leading dot)" aside)

Author: AnExiledDev

.devcontainer/CHANGELOG.md

@@ -16,14 +16,19 @@
 
 #### Security
 - Protected-files-guard now blocks modifications to `.credentials.json`
+- Replaced `eval` tilde expansion with `getent passwd` lookup across all scripts (prevents shell injection via `SUDO_USER`/`USER`)
+- Auth token value is now JSON-escaped before writing to `.credentials.json`
+- Credential directory created with restrictive umask (700) matching credential file permissions (600)
 
 #### Scripts
 - Replaced `setup-symlink-claude.sh` with `setup-migrate-claude.sh` (one-time migration)
 - Auto-migrates from `/workspaces/.claude/` if `.credentials.json` present
+- `chown` in mcp-qdrant poststart hooks now uses resolved `_USERNAME` instead of hardcoded `vscode` or `$(id -un)`
 
 #### Documentation
 - All docs now reference `~/.claude` as default config path
 - Added `CLAUDE_AUTH_TOKEN` setup flow to README, configuration reference, and troubleshooting
+- ccstatusline README verification commands now respect `CLAUDE_CONFIG_DIR`
 
 ### Removed
 

.devcontainer/features/ccstatusline/README.md

@@ -106,7 +106,7 @@ You should see formatted output with powerline styling.
 
 **3. Check Claude Code integration:**
 ```bash
-cat ~/.claude/settings.json | jq '.statusLine'
+cat "${CLAUDE_CONFIG_DIR:-$HOME/.claude}/settings.json" | jq '.statusLine'
 ```
 
 Should show:
@@ -205,7 +205,7 @@ cat ~/.config/ccstatusline/settings.json | jq .
 echo '{"model":{"display_name":"Test"}}' | npx -y ccstatusline@latest
 
 # 3. Check Claude Code settings
-cat ~/.claude/settings.json | jq '.statusLine'
+cat "${CLAUDE_CONFIG_DIR:-$HOME/.claude}/settings.json" | jq '.statusLine'
 
 # 4. Manually run auto-config if needed
 configure-ccstatusline-auto
@@ -259,7 +259,7 @@ configure-ccstatusline-auto
 npm install -g ccstatusline@latest
 ```
 
-Then update `~/.claude/settings.json`:
+Then update `${CLAUDE_CONFIG_DIR:-~/.claude}/settings.json`:
 ```json
 {
   "statusLine": {

.devcontainer/features/ccstatusline/install.sh

@@ -192,7 +192,8 @@ fi
 
 # Use SUDO_USER since _REMOTE_USER isn't set in post-start hooks
 USERNAME="${SUDO_USER:-vscode}"
-_USER_HOME=$(eval echo "~${USERNAME}")
+_USER_HOME=$(getent passwd "$USERNAME" 2>/dev/null | cut -d: -f6)
+_USER_HOME="${_USER_HOME:-/home/$USERNAME}"
 SETTINGS_FILE="${CLAUDE_CONFIG_DIR:-${_USER_HOME}/.claude}/settings.json"
 
 # Ensure directory exists

.devcontainer/features/mcp-qdrant/install.sh

@@ -190,7 +190,8 @@ fi
 
 # Resolve target user's home (guards against $HOME=/root during feature install)
 _USERNAME="${SUDO_USER:-${USER:-vscode}}"
-_USER_HOME=$(eval echo "~${_USERNAME}")
+_USER_HOME=$(getent passwd "$_USERNAME" 2>/dev/null | cut -d: -f6)
+_USER_HOME="${_USER_HOME:-/home/$_USERNAME}"
 
 # Ensure settings.json exists
 SETTINGS_FILE="${CLAUDE_CONFIG_DIR:-${_USER_HOME}/.claude}/settings.json"
@@ -261,7 +262,7 @@ fi
 
 # Set proper permissions
 chmod 644 "$SETTINGS_FILE"
-chown "$(id -un):$(id -gn)" "$SETTINGS_FILE" 2>/dev/null || true
+chown "${_USERNAME}:${_USERNAME}" "$SETTINGS_FILE" 2>/dev/null || true
 
 echo "[mcp-qdrant] ✓ Configuration complete"
 HOOK_EOF

.devcontainer/features/mcp-qdrant/poststart-hook.sh

@@ -58,7 +58,8 @@ fi
 
 # Resolve target user's home (guards against $HOME=/root when hook runs as root)
 _USERNAME="${SUDO_USER:-${USER:-vscode}}"
-_USER_HOME=$(eval echo "~${_USERNAME}")
+_USER_HOME=$(getent passwd "$_USERNAME" 2>/dev/null | cut -d: -f6)
+_USER_HOME="${_USER_HOME:-/home/$_USERNAME}"
 
 # Ensure settings.json exists
 SETTINGS_FILE="${CLAUDE_CONFIG_DIR:-${_USER_HOME}/.claude}/settings.json"
@@ -129,6 +130,6 @@ fi
 
 # Set proper permissions
 chmod 644 "$SETTINGS_FILE"
-chown vscode:vscode "$SETTINGS_FILE" 2>/dev/null || true
+chown "${_USERNAME}:${_USERNAME}" "$SETTINGS_FILE" 2>/dev/null || true
 
 echo "[mcp-qdrant] ✓ Configuration complete"

.devcontainer/scripts/setup-auth.sh

@@ -70,7 +70,8 @@ fi
 # Note: After unset, the token remains visible in /proc/<pid>/environ for the
 # lifetime of this process. This is a platform limitation of environment variables.
 _USERNAME="${SUDO_USER:-${USER:-vscode}}"
-_USER_HOME=$(eval echo "~${_USERNAME}")
+_USER_HOME=$(getent passwd "$_USERNAME" 2>/dev/null | cut -d: -f6)
+_USER_HOME="${_USER_HOME:-/home/$_USERNAME}"
 CLAUDE_CRED_DIR="${CLAUDE_CONFIG_DIR:-${_USER_HOME}/.claude}"
 CLAUDE_CRED_FILE="$CLAUDE_CRED_DIR/.credentials.json"
 if [ -n "$CLAUDE_AUTH_TOKEN" ]; then
@@ -88,11 +89,15 @@ if [ -n "$CLAUDE_AUTH_TOKEN" ]; then
         AUTH_CONFIGURED=true
     else
         echo "[setup-auth] Creating .credentials.json from CLAUDE_AUTH_TOKEN..."
-        mkdir -p "$CLAUDE_CRED_DIR"
+        # Create directory with restrictive permissions (matches credential file at 600)
+        ( umask 077; mkdir -p "$CLAUDE_CRED_DIR" )
+        # Escape JSON-special characters in token value (defense against malformed JSON
+        # if a token ever contains " or \ — unlikely with sk-ant-* but closes the gap)
+        ESCAPED_TOKEN=$(printf '%s' "$CLAUDE_AUTH_TOKEN" | sed 's/\\/\\\\/g; s/"/\\"/g')
         # Write credentials with restrictive permissions from the start (no race window).
         # Uses printf '%s' to avoid shell expansion of token value (defense against
         # metacharacters in the token string — backticks, $(), quotes).
-        if ( umask 077; printf '{\n  "claudeAiOauth": {\n    "accessToken": "%s",\n    "refreshToken": "%s",\n    "expiresAt": 9999999999999,\n    "scopes": ["user:inference", "user:profile"]\n  }\n}\n' "$CLAUDE_AUTH_TOKEN" "$CLAUDE_AUTH_TOKEN" > "$CLAUDE_CRED_FILE" ); then
+        if ( umask 077; printf '{\n  "claudeAiOauth": {\n    "accessToken": "%s",\n    "refreshToken": "%s",\n    "expiresAt": 9999999999999,\n    "scopes": ["user:inference", "user:profile"]\n  }\n}\n' "$ESCAPED_TOKEN" "$ESCAPED_TOKEN" > "$CLAUDE_CRED_FILE" ); then
             echo "[setup-auth] Claude auth token configured"
             AUTH_CONFIGURED=true
         else

.devcontainer/scripts/setup-migrate-claude.sh

@@ -8,7 +8,8 @@
 
 OLD_DIR="/workspaces/.claude"
 _USERNAME="${SUDO_USER:-${USER:-vscode}}"
-_USER_HOME=$(eval echo "~${_USERNAME}")
+_USER_HOME=$(getent passwd "$_USERNAME" 2>/dev/null | cut -d: -f6)
+_USER_HOME="${_USER_HOME:-/home/$_USERNAME}"
 NEW_DIR="${CLAUDE_CONFIG_DIR:-${_USER_HOME}/.claude}"
 
 # Nothing to migrate if old directory doesn't exist

docs/src/content/docs/reference/changelog.md

@@ -54,23 +54,28 @@ For minor and patch updates, you can usually just rebuild the container. Check t
 #### Configuration
 - Moved `.claude` directory from `/workspaces/.claude` to `~/.claude` (home directory)
 - Added Docker named volume for persistence across rebuilds (per-instance isolation via `${devcontainerId}`)
-- `CLAUDE_CONFIG_DIR` now defaults to `/home/vscode/.claude`
+- `CLAUDE_CONFIG_DIR` now defaults to `~/.claude`
 
 #### Authentication
 - Added `CLAUDE_AUTH_TOKEN` support in `.secrets` for long-lived tokens from `claude setup-token`
 - Auto-creates `.credentials.json` from token on container start (skips if already exists)
 - Added `CLAUDE_AUTH_TOKEN` to devcontainer.json secrets declaration
 
 #### Security
-- Protected-files-guard now covers `.credentials.json` (leading dot)
+- Protected-files-guard now blocks modifications to `.credentials.json`
+- Replaced `eval` tilde expansion with `getent passwd` lookup across all scripts (prevents shell injection via `SUDO_USER`/`USER`)
+- Auth token value is now JSON-escaped before writing to `.credentials.json`
+- Credential directory created with restrictive umask (700) matching credential file permissions (600)
 
 #### Scripts
 - Replaced `setup-symlink-claude.sh` with `setup-migrate-claude.sh` (one-time migration)
 - Auto-migrates from `/workspaces/.claude/` if `.credentials.json` present
+- `chown` in mcp-qdrant poststart hooks now uses resolved `_USERNAME` instead of hardcoded `vscode` or `$(id -un)`
 
 #### Documentation
 - All docs now reference `~/.claude` as default config path
 - Added `CLAUDE_AUTH_TOKEN` setup flow to README, configuration reference, and troubleshooting
+- ccstatusline README verification commands now respect `CLAUDE_CONFIG_DIR`
 
 ### Removed