claude-code: chown ~/.cache after upstream installer run (3.0.1)

The official install.sh runs as root with HOME=$USER_HOME and writes into
$HOME/.cache (its own state dir, plus $HOME/.cache/node-gyp when native
modules compile). Those paths were left root-owned because the chown only
covered .claude and .local — which is how downstream tools like web-shell
hit EACCES on mkdir ~/.cache/<anything>/.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: chapterjason

src/claude-code/devcontainer-feature.json

@@ -1,6 +1,6 @@
 {
   "id": "claude-code",
-  "version": "3.0.0",
+  "version": "3.0.1",
   "name": "claude-code",
   "description": "Installs the latest Claude Code CLI via the official native installer into the remote user's home (~/.claude/local + ~/.local/bin), the layout the auto-updater expects. Declares ~/.claude and ~/.claude.json as persistence targets via the home-persist manifest, so credentials, sessions, and plugins survive rebuilds when home-persist is installed.",
   "documentationURL": "https://github.com/SoureCode/devcontainer-features/tree/master/src/claude-code",

src/claude-code/install.sh

@@ -18,7 +18,15 @@ if [ ! -x "$USER_HOME/.local/bin/claude" ]; then
   exit 1
 fi
 
+# The upstream installer runs as root with HOME=$USER_HOME and writes into
+# $HOME/.claude, $HOME/.local AND $HOME/.cache (its own state dir plus
+# node-gyp from any native-module compile). Chown all three so nothing is
+# left root-owned on the remote user's home. .cache is guarded because it
+# may not exist on minimal installs.
 chown -R "$USER_NAME:$USER_GROUP" "$USER_HOME/.claude" "$USER_HOME/.local"
+if [ -d "$USER_HOME/.cache" ]; then
+  chown -R "$USER_NAME:$USER_GROUP" "$USER_HOME/.cache"
+fi
 
 # Declare the HOME paths Claude Code needs persisted. The home-persist feature
 # reads every /etc/devcontainer-persist.d/*.json at create time and symlinks