Drop ticket references from e2e comments and note the retry hardening in the changelog

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: lelia <2418071+lelia@users.noreply.github.com>

Author: lelia

.github/workflows/e2e-test.yml

@@ -47,9 +47,9 @@ jobs:
             validate: tests/e2e/validate-reachability.sh
             setup-node: "true"
             # The tier-1 reachability backend intermittently returns empty
-            # results while the CLI reports success (ENG-5093). The probe
-            # exits 0 when the facts file has alerted components; anything
-            # else is retried before validation fails the job.
+            # results while the CLI reports success. The probe exits 0 when
+            # the facts file has alerted components; anything else is
+            # retried before validation fails the job.
             retry-probe: bash tests/e2e/reach-facts-probe.sh tests/e2e/fixtures/simple-npm
 
           - name: gitlab
@@ -123,7 +123,7 @@ jobs:
               echo "::warning title=e2e-${{ matrix.name }} incomplete results::output still fails the completeness probe after ${max_attempts} attempts; letting validation fail the job"
               break
             fi
-            echo "::warning title=e2e-${{ matrix.name }} transient retry::attempt ${attempt} failed the completeness probe (suspected backend transient, see ENG-5093); retrying"
+            echo "::warning title=e2e-${{ matrix.name }} transient retry::attempt ${attempt} failed the completeness probe (suspected backend transient); retrying"
             echo "e2e-${{ matrix.name }}: retry after attempt ${attempt} — completeness probe failed (suspected transient)" >> "$GITHUB_STEP_SUMMARY"
             attempt=$((attempt+1))
             sleep 30

CHANGELOG.md

@@ -12,6 +12,12 @@
   (e.g. `generic`) and skips individual unparseable artifacts in the stream
   instead of failing the whole response.
 
+### Changed: e2e reachability jobs retry transient empty results
+
+- The e2e workflow now detects reachability runs that report success with no
+  alerted components in the facts file — a transient backend condition — and
+  retries the scan up to three times, uploading run artifacts on failure.
+
 ## 2.5.9
 
 ### Changed: bump pinned @coana-tech/cli to 15.10.3

tests/e2e/reach-facts-probe.sh

@@ -3,8 +3,8 @@
 #
 # Used by the e2e workflow's retry-probe hook: a --reach run against the
 # known-vulnerable fixture that reports success but yields no alerted
-# components is the signature of a transient tier-1 backend failure
-# (ENG-5093), so the run is worth repeating before validation fails the job.
+# components is the signature of a transient tier-1 backend failure,
+# so the run is worth repeating before validation fails the job.
 set -euo pipefail
 
 TARGET="${1:?usage: reach-facts-probe.sh <target-path>}"