fix(ci): remove duplicate docker.sock mount in act-runner options

act_runner automatically passes /var/run/docker.sock from its own mounts
to job containers. Explicitly adding it in container.options caused
"Duplicate mount point" error, preventing all job containers from starting.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

AINative_OKR_CASAN5/.gitea/act-runner-config.yaml

@@ -28,9 +28,9 @@ container:
   network: bridge
 
   # --memory 512m: prevent OOM on 1 GB VPS (build runs in HOST daemon, not job container)
-  # -v socket: Docker-outside-of-Docker for the deploy job; lets docker CLI in the job
-  #            container talk to the HOST daemon to build + run OKR images.
-  options: "--memory 512m --cpus 1.5 -v /var/run/docker.sock:/var/run/docker.sock"
+  # NOTE: act_runner already passes /var/run/docker.sock from its own mounts to job
+  # containers; do NOT add it here or Docker will reject the duplicate bind mount.
+  options: "--memory 512m --cpus 1.5"
 
   valid_volumes:
     - "**"