fix(ci): pin selftest Playwright image to v1.61.1 matching lockfile

npm ci was resolving @playwright/test@1.61.1 against a v1.52.0 container,
so Chromium binary paths mismatched and browser specs failed.

.gitea/workflows/ci.yml

@@ -52,7 +52,7 @@ jobs:
     if: needs.skip-ci-check.outputs.should-skip != '1'
     runs-on: [homelab, self-hosted, linux]
     container:
-      image: mcr.microsoft.com/playwright:v1.52.0-jammy
+      image: mcr.microsoft.com/playwright:v1.61.1-jammy
     steps:
       - uses: actions/checkout@v4
       - name: Install

docs/SELFTEST.md

@@ -37,6 +37,8 @@ public e2e must keep the default forbid-private behavior.
 
 ## CI
 
-`.gitea/workflows/ci.yml` job `selftest` installs Chromium deps and runs
-`npm run selftest` after unit tests. Failures there mean a regression in kit
-browser/API helpers *before* a consumer pins a broken tag.
+`.gitea/workflows/ci.yml` job `selftest` runs in
+`mcr.microsoft.com/playwright:v1.61.1-jammy` (must match the pinned
+`@playwright/test` version) and executes `npm run selftest` after unit tests.
+Failures there mean a regression in kit browser/API helpers *before* a consumer
+pins a broken tag.

package.json

@@ -59,7 +59,7 @@
     }
   },
   "devDependencies": {
-    "@playwright/test": "^1.52.0",
+    "@playwright/test": "1.61.1",
     "@types/node": "^22.15.0",
     "tsup": "^8.4.0",
     "tsx": "^4.19.0",