ci(functions-e2e): keep suite on workflow_dispatch while error-fidelity gaps remain

Revert the pull_request trigger added in 2982f34 (keeping that commit's build-order
fix and file:-linking comment updates). The consolidated gRPC path still has 11
known error-text/status fidelity gaps in the ported specs -- not-found message
wording, activity-failure prefixes, and terminal-op 400-vs-200 semantics -- which
would make an automatic pull_request run red. Those gaps are tracked separately;
until they are addressed the suite runs on manual dispatch only and does not gate
PRs.

Also quote the "Build ... for file: linking" step name so the workflow is valid
YAML: an unquoted plain scalar containing ": " is rejected by spec-compliant
parsers, which would otherwise block workflow_dispatch as well.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 6e5be22b-b727-4ccf-8668-60397bb403a0

Author: YunchuWang

.github/workflows/functions-e2e-tests.yaml

@@ -12,21 +12,19 @@ name: 🧪 Functions Host E2E Tests
 # below we install and start both, so the suite runs for real; the self-skip is
 # the safety net that keeps the job green if a prerequisite fails to come up.
 #
-# Triggering: this suite runs automatically on pull requests that touch the
-# Functions surface (`test/e2e-functions/**`, `packages/azure-functions-durable/**`,
-# or this workflow file), and can also be started ad hoc from the Actions tab via
-# "Run workflow" (workflow_dispatch). It is intentionally scoped to the Functions
-# surface and does NOT gate core-only PRs, which have their own suites. NOTE:
+# Triggering: this suite is run ad hoc (manual dispatch) only for now. The ported
+# specs still have 11 known error-text/status fidelity gaps on the consolidated
+# gRPC path, which would make an automatic `pull_request` run red, so it does not
+# gate PRs yet; those gaps are tracked separately and the trigger will be
+# re-enabled once they are addressed. Start it from the Actions tab via "Run
+# workflow" (workflow_dispatch). To re-enable automatic runs later, add a
+# `pull_request` trigger scoped to `test/e2e-functions/**`,
+# `packages/azure-functions-durable/**`, and this workflow file. NOTE:
 # workflow_dispatch only appears in the Actions UI once this file exists on the
 # repository's default branch.
 
 on:
   workflow_dispatch:
-  pull_request:
-    paths:
-      - "test/e2e-functions/**"
-      - "packages/azure-functions-durable/**"
-      - ".github/workflows/functions-e2e-tests.yaml"
 
 permissions:
   contents: read
@@ -59,7 +57,7 @@ jobs:
       # Build the in-repo compat package (`durable-functions`); its build script
       # runs `build:core` first, so this also builds `packages/durabletask-js` into
       # dist/. Both must exist before the test-app's `file:`-linked install below.
-      - name: 🏗️ Build in-repo durable-functions (+ core) for file: linking
+      - name: "🏗️ Build in-repo durable-functions (+ core) for file: linking"
         run: npm run build -w durable-functions
 
       - name: 🔧 Install Azurite and Azure Functions Core Tools

test/e2e-functions/README.md

@@ -39,8 +39,8 @@ so it is safe to leave wired into CI and to run locally without setup:
   **not** part of the default `npm test` / workspaces test run, nor of
   `test:e2e:internal` (which is scoped to `tests/e2e`).
 - **CI** — `.github/workflows/functions-e2e-tests.yaml` installs `func` + Azurite,
-  installs/builds the test-app, and runs the suite on PRs that touch
-  `test/e2e-functions/**`. The self-skip is the safety net if a prerequisite fails
+  installs/builds the test-app, and runs the suite on manual dispatch
+  (`workflow_dispatch`). The self-skip is the safety net if a prerequisite fails
   to come up.
 
 ## What it covers