point the probe at the fork

The first round answered what it was for: a step cannot set GITHUB_SERVER_URL
and v4 fails on the check either way, while v3 uploads. The three upload
steps are down to one, on the fork, and it is no longer allowed to fail
quietly — the run is now a straight yes or no on going back to v4.

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

.gitea/workflows/probe-artifacts.yml

@@ -1,11 +1,14 @@
-# A throwaway workflow: it answers, in one run, what the release cannot ask
+# A throwaway workflow: it answers, in seconds, what the release cannot ask
 # without building for four minutes first.
 #
-# Three questions. Whether a step-level env reaches a JS action at all or the
-# runner overwrites the GITHUB_ names with its own; whether this Gitea speaks
-# the v4 artifact protocol (ACTIONS_RESULTS_URL is the giveaway); and whether
-# the v3 action still gets its artifact through. Every upload is allowed to
-# fail, so a single run reports on all three rather than stopping at the first.
+# The first round of it settled the question it was written for. The runner sets
+# the GITHUB_ names over the env of a step, so GITHUB_SERVER_URL cannot be
+# corrected from a workflow and the host check inside upload-artifact v4 cannot
+# be talked out of its verdict; v3 uploaded and v4 did not, either way.
+#
+# What is left to see is whether the fork works — the same v4 action taken from
+# this Gitea with that one check removed. Nothing here is allowed to fail
+# quietly: a green run means the release can go back to v4.
 #
 # Delete this file once the release works
 name: Probe the artifacts
@@ -30,41 +33,17 @@ jobs:
           New-Item -ItemType Directory -Force probe | Out-Null
           'probe' | Out-File probe/probe.txt -Encoding utf8
 
-      # What the runner hands out on its own
-      - name: Show the environment as it comes
+      # Kept for the record: ACTIONS_RESULTS_URL is the v4 backend the check
+      # never let the action reach
+      - name: Show the environment
         run: |
           "server = [$env:GITHUB_SERVER_URL]"
           "api    = [$env:GITHUB_API_URL]"
           "results= [$env:ACTIONS_RESULTS_URL]"
-          "runtime= [$env:ACTIONS_RUNTIME_URL]"
 
-      # The same, with the substitution the release step makes. A run step is
-      # not a JS action, but if the name is overwritten even here, the answer is
-      # settled and nothing in the workflow can set it
-      - name: Show the environment with the substitution
-        env:
-          GITHUB_SERVER_URL: https://github.com
-        run: '"server = [$env:GITHUB_SERVER_URL]"'
-
-      - name: Upload with v4, plain
-        continue-on-error: true
-        uses: actions/upload-artifact@v4
+      - name: Upload with the fork
+        uses: https://git.alrakis.kz/actions/upload-artifact@v4-gitea
         with:
-          name: probe-v4-plain
-          path: probe/
-
-      - name: Upload with v4 and the substitution
-        continue-on-error: true
-        uses: actions/upload-artifact@v4
-        env:
-          GITHUB_SERVER_URL: https://github.com
-        with:
-          name: probe-v4-substituted
-          path: probe/
-
-      - name: Upload with v3
-        continue-on-error: true
-        uses: actions/upload-artifact@v3
-        with:
-          name: probe-v3
+          name: probe-fork
           path: probe/
+          if-no-files-found: error