Updated agents and db

AGENTS.md

@@ -22,8 +22,12 @@ These tool paths should be used instead of any entry in the PATH environment var
 - If there's documnentation present, always keep it updated.
 - After every iteration, evaluate if the test coverage would fall below 100%, and write tests if necessary.
 - After every iteration, run `jb cleanupcode --build=False '$file1' '$file2' ...` for every file you touched.
-- After every frontend change, verify the results with `npx playwright test`.
-
+- After every frontend change, verify the results using an ephemeral Playwright run.
+  - For ad hoc verification in this repo, do not default to `npx playwright test` with a temp spec outside the repo.
+  - Prefer a repo-local ephemeral Node script under `artifacts_verify/` that imports `playwright` with `require('playwright')` and drives the browser directly.
+  - If using the Playwright test runner, use the repo-local CLI at `node_modules\.bin\playwright.cmd` and keep the spec inside the repo so local `node_modules` resolution works.
+  - Do not mix the global Playwright CLI with the repo-local `@playwright/test` package.
+  - When browser verification needs the app running, launch the app against a temporary copy of `src\RolemasterDb.App\rolemaster.db` so verification does not mutate the canonical DB.
 ### Git
 
 - Never change the .gitignore file without consent.
@@ -48,3 +52,4 @@ These tool paths should be used instead of any entry in the PATH environment var
   - Consider using `$env:DOTNET_SKIP_FIRST_TIME_EXPERIENCE = '1'`
   - Consider using `$env:NUGET_PACKAGES = Join-Path $env:USERPROFILE '.nuget\packages'`
 - If you need a separate output directory, use a subfolder under `artifacts`, and clean it up afterwards.
+- Avoid running `dotnet build` and `dotnet test` in parallel in this repo; that can cause file-lock failures in `obj\Debug\net10.0`.