ci(replay-ui): name the run directory for what it fuzzes

runs/dogfood and the '### replay-ui dogfood' heading carried the same
naming error as the job name: dogfooding is why the run exists, not what
it fuzzes.

.github/scripts/replay-ui-summary-test.sh

@@ -3,7 +3,7 @@
 # summary it renders. Run under the flags GitHub Actions uses for a `run:`
 # block, because that is where a swallowed failure hides.
 #
-# testdata/replay-ui-real-run.jsonl is the first 10 steps of the dogfood run in
+# testdata/replay-ui-real-run.jsonl is the first 10 steps of the replay-ui run in
 # actions run 31873049857 on master, with the per-step `hierarchy` dumps and the
 # rowElements/tabElements extractors removed so the file stays readable. Nothing
 # else was touched. That run was green, and badgeCountMatchesThePanel judged

.github/scripts/replay-ui-summary.sh

@@ -1,9 +1,9 @@
 #!/usr/bin/env bash
-# Reads the replay-ui dogfood trace and reports, per property, how many steps
+# Reads the replay-ui fuzzing trace and reports, per property, how many steps
 # that property actually judged. Kept out of the workflow YAML so it can be run
 # by hand against a local run:
 #
-#   GITHUB_STEP_SUMMARY=/dev/stdout .github/scripts/replay-ui-summary.sh runs/dogfood
+#   GITHUB_STEP_SUMMARY=/dev/stdout .github/scripts/replay-ui-summary.sh runs/replay-ui
 #
 # `sanderling test` exiting 0 says only that no property returned false. Every
 # property in replay-ui/sanderling/spec.ts declines to judge when a reading it
@@ -14,7 +14,7 @@
 set -euo pipefail
 
 root="$(cd "$(dirname "${BASH_SOURCE[0]}")/../.." && pwd)"
-output="${1:-runs/dogfood}"
+output="${1:-runs/replay-ui}"
 spec="${SPEC:-$root/replay-ui/sanderling/spec.ts}"
 summary="${GITHUB_STEP_SUMMARY:-/dev/null}"
 
@@ -23,7 +23,7 @@ run_dirs=("$output"/*/)
 shopt -u nullglob
 
 {
-  echo "### replay-ui dogfood"
+  echo "### the replay ui"
   echo
   echo "- seed \`${SEED:-unset}\`, budget ${MAX_STEPS:-unset} steps"
 } >> "$summary"