docs(test): rename Playwright build-test script and tighten README

scripts/test only runs the frontend Playwright suite against a
production build, not the full test set, so the bare name overstates
its scope. Rename it to scripts/test-frontend-built.sh to match the
test:frontend-built task and the scripts/ .sh convention, update the
three call sites (Taskfile, README command, .claude/settings.json),
and shorten the README description. No behavior change.

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

Author: turegjorup

.claude/settings.json

@@ -12,7 +12,7 @@
       "Bash(docker compose:*)",
       "WebFetch(domain:api-platform.com)",
       "Bash(grep:*)",
-      "Bash(./scripts/test *)",
+      "Bash(./scripts/test-frontend-built.sh *)",
       "Bash(git add:*)",
       "Bash(git fetch*)",
       "Bash(git pull*)",

README.md

@@ -453,9 +453,9 @@ See the `docker-compose.yml` playwright entry and the version imported in packag
 
 #### Testing on the built files
 
-This project includes a test script that handles building assets, running
-Playwright tests, and stops and starts the node container. This script tests the
-*built* files. This is the approach the GitHub Action uses.
+Runs the Playwright end-to-end suite against a production build: it stops the
+`node` (Vite dev) container, builds the assets, runs the tests, then restarts
+`node` — the same flow the CI Playwright job uses.
 
 ```shell
 task test:frontend-built
@@ -464,7 +464,7 @@ task test:frontend-built
 or
 
 ```shell
-./scripts/test {TEST-PATH}
+./scripts/test-frontend-built.sh {TEST-PATH}
 ```
 
 TEST-PATH is optional, and is the specific test file or directory to run like

Taskfile.yml

@@ -236,7 +236,7 @@ tasks:
   test:frontend-built:
     desc: "Runs frontend tests (Playwright) on the built files. This temporarily stops the node container."
     cmds:
-      - ./scripts/test
+      - ./scripts/test-frontend-built.sh
 
   test:frontend-local:
     desc: "Runs frontend tests from the local machine."