docs: update stale vitest-CI-failure comment now that it's confirmed fixed

Root cause traced: package-lock.json was missing per-platform optional
dependency entries for Rollup/esbuild's Linux native binaries
(npm/cli#4828) since it had only ever been regenerated on darwin-arm64.
npm ci on the Linux runner silently skipped them, Vite's synchronous
require() at vitest startup threw before any test loaded. Fixed as a
side effect of the full package-lock.json regeneration in a0ad052.
Confirmed via Gitea Actions run history: failure before, 2 consecutive
successes after.

.github/workflows/build-verify.yml

@@ -80,18 +80,11 @@ jobs:
 
       - name: vitest
         run: npm test
-        # KNOWN OPEN ISSUE (2026-07-16): this step fails in 0-1s on this specific
+        # Fixed 2026-07-17: the 0-1s pre-test-load crash on this runner was
-        # Gitea Actions runner for a reason not diagnosable from a local machine --
+        # package-lock.json missing per-platform optional-dependency entries
-        # tried forcing a small fixed forks pool (--pool=forks, min/maxForks) as a
+        # for Rollup/esbuild's native Linux binaries (npm/cli#4828) -- the
-        # guess (common fix for CI-only vitest worker-pool crashes), made no
+        # lockfile had only been regenerated on darwin-arm64, so `npm ci` on
-        # difference. The actual test suite passes 215/215 reliably every way
+        # the Linux runner silently skipped @rollup/rollup-linux-x64-gnu and
-        # tested locally: plain `npm test`, with CI=true set, and after a fully
+        # @esbuild/linux-x64, and Vite's synchronous require() of them at
-        # fresh `rm -rf node_modules && npm ci`. The job's "Complete job" step
+        # startup threw before any test file ran. Resolved as a side effect
-        # also shows failure/canRerun:false, which may indicate a runner-level
+        # of regenerating package-lock.json in commit a0ad052.
-        # issue rather than a test-code issue. Needs someone with actual
-        # logged-in dashboard access to this Gitea instance to read the real
-        # step log -- not accessible via this session's tooling (Gitea Actions
-        # log API returned 404 for every endpoint pattern tried; the web log
-        # viewer requires an authenticated session to stream content).
-        # Every OTHER step in this workflow (syntax, require() check, typecheck,
-        # build) is confirmed working and already caught 2 real bugs today.