test infra reply: drop UID 1000, run as root

Dockerfile

@@ -1,31 +1,14 @@
-# Follows https://huggingface.co/docs/hub/spaces-sdks-docker#permissions exactly.
-# The ONLY change from the official example is the final CMD.
+# 2026-04-08 update: HF infra confirmed Docker Spaces no longer need to drop to
+# UID 1000 — buckets are mounted to be writable by root, which is now the
+# intended default for Docker SDK Spaces (policy not yet publicly documented).
+# This Dockerfile is the "follow-up test": same probe code, same bucket, but
+# we stay as root for the runtime. Expectation: all probes that failed under
+# UID 1000 should now pass.
 FROM python:3.12-slim
 
-# Set up a new user named "user" with user ID 1000
-RUN useradd -m -u 1000 user
+WORKDIR /app
 
-# Switch to the "user" user
-USER user
-
-# Set home to the user's home directory
-ENV HOME=/home/user \
-    PATH=/home/user/.local/bin:$PATH
-
-# Set the working directory to the user's home directory
-WORKDIR $HOME/app
-
-# Copy the current directory contents into the container at $HOME/app
-# setting the owner to the user
-COPY --chown=user . $HOME/app
-
-# Try and chown /data so it's writable by the user. This is EXACTLY what
-# the docs suggest for writable runtime directories. It will be overridden
-# at runtime when the bucket mount lands on top — that's the bug we're
-# demonstrating.
-USER root
-RUN mkdir -p /data && chown -R user:user /data && chmod -R 777 /data
-USER user
+COPY . /app
 
 EXPOSE 7860
 CMD ["python", "-u", "app.py"]