Allows deploy-test to run on pull_request events too

So PR pushes deploy straight to the test environment, without a manual
workflow_dispatch each time. Only one test environment exists, so this
means concurrent PRs would overwrite each other's deploy - acceptable
with a single active PR, worth revisiting once that's no longer true.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015FffvxxJp5wG34Ru48GBig

.gitea/workflows/continuous_integration.yaml

@@ -318,10 +318,15 @@ jobs:
           path: ${{ env.ARTIFACT_NAME_PRODUCTION }}
           retention-days: 1
 
-  # Automatic test deploy on push to master, or on any workflow_dispatch run (FR-03, D-01, D-09).
+  # Automatic test deploy on push to master, any workflow_dispatch run, or a pull_request event
+  # (FR-03, D-01, D-09 — pull_request added as a deliberate extension beyond the original scope, so
+  # PR pushes can be verified against the real test environment without a manual workflow_dispatch
+  # each time). There is only one shared test environment: with more than one PR open at once, each
+  # push to any of them will redeploy and overwrite it — fine for a single active PR, revisit
+  # (e.g. gate behind a label, or restrict to one branch) before that becomes a real scenario.
   deploy-test:
     needs: [publish-test, config]
-    if: github.event_name == 'workflow_dispatch' || (github.event_name == 'push' && github.ref == 'refs/heads/master')
+    if: github.event_name == 'workflow_dispatch' || github.event_name == 'pull_request' || (github.event_name == 'push' && github.ref == 'refs/heads/master')
     uses: ./.gitea/workflows/deploy-scp.yaml
     secrets: inherit
     with: