CI: stage users.txt before mining loop, not after

The 'Final deploy' step only runs once at the end. With the staging
step there, interim deploys during the mining loop wouldn't have
users.txt available, so the dynamic / handler wouldn't see queued
users until the run finished. Move the cp into 'Determine target
users' (right after pre-staging pirate.html) so every interim deploy
publishes a fresh users.txt.

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

Author: pirate

.github/workflows/mine-and-deploy.yml

@@ -135,6 +135,11 @@ jobs:
           if [ -f stats.html ]; then
             cp stats.html cloudflare/public/pirate.html
           fi
+          # Stage users.txt as a public asset so the Worker's dynamic /
+          # handler can read it for the queued/mining list. Doing it here
+          # (before the mining loop) means every interim deploy also has
+          # a fresh users.txt available to the homepage.
+          cp cloudflare/users.txt cloudflare/public/users.txt
           echo "Targets:"
           cat /tmp/targets.txt
 
@@ -215,11 +220,6 @@ jobs:
           git diff --staged --quiet || git commit -m "Add ${{ inputs.user }} to users.txt [skip ci]"
           git push || echo "::warning::push failed (no commit permission?)"
 
-      # Deploy users.txt as a static asset so the Worker's dynamic /
-      # handler can read it to build the queued/mining list.
-      - name: Stage users.txt as a public asset
-        run: cp cloudflare/users.txt cloudflare/public/users.txt
-
       - name: Final deploy
         working-directory: cloudflare
         run: npx --yes wrangler@latest deploy