CI: the release gate still calls ci.yml (workflow_call)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

.github/workflows/ci.yml

@@ -31,6 +31,8 @@
 # `ci` job still runs and reports the commit's real result (see the `ci` job): the merge queue
 # reads `ci` from the newest run of a commit, so a run without it would block a PR that passed.
 # Cross-compilation is opt-in through Run workflow; release builds remain in release.yml.
+# The release gate (release-gate.yml) calls this workflow (workflow_call) as a Run workflow with
+# cross-compilation on.
 # Every Linux job runs on Blacksmith's Ubuntu 24.04 runners (blacksmith-<N>vcpu-ubuntu-2404), sized
 # per job: 32 vCPU for the tests, 16 for Clippy, the GPU path tests, the archive build (nightly) and the merge queue's, 8 for compiles, doc and reference tests, 4 for the light checks, 2 for Select checks and ci.
 # The Windows shader job runs on Blacksmith's Windows Server 2025 runners (blacksmith-8vcpu-windows-2025);
@@ -64,6 +66,14 @@ on:
         description: "Also check WebAssembly and RISC-V (before a release)"
         type: boolean
         default: false
+  # The release gate (release-gate.yml): the event stays the caller's (workflow_dispatch), so a
+  # call runs exactly what Run workflow runs.
+  workflow_call:
+    inputs:
+      cross_compile:
+        description: "Also check WebAssembly and RISC-V (before a release)"
+        type: boolean
+        default: false
 
 permissions:
   contents: read