jason/polaris-task-force
1
0
Fork 0
Code Issues Wiki Activity

docs: add dev server testing protocol to AGENTS.md

Browse source
This commit is contained in:
Jason Fraley 2026-08-02 14:32:55 -04:00
parent 6b2778751b
commit d50f114a75
1 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
AGENTS.md
View file

@ -41,6 +41,13 @@ Known pre-existing errors, don't chase them: `src/utils/access-control/hasLogist
- Run a single integration test: `bun run vitest run tests/int/api.int.spec.ts` - Run a single integration test: `bun run vitest run tests/int/api.int.spec.ts`
- Run a single e2e test: `bun run playwright test tests/e2e/frontend.e2e.spec.ts` - Run a single e2e test: `bun run playwright test tests/e2e/frontend.e2e.spec.ts`
### Dev server & testing protocol
- If a dev server is **already running** when you want to test (port 3000 in use, or Next reports "Another next dev server is already running"), **ask the user whether you should kill the existing server and start a fresh one** before doing anything. A stale `.next/dev/devserver.lock` can also block startup — offer to clear it as part of the same question.
- If the user says **no**, do **not** start a dev server and do **not** attempt to verify via E2E or Playwright — the user will run the app and test themselves, then report back.
- Stale dev processes: killing the process is not always enough; remove `.next/dev/devserver.lock` before restarting.
## Generated files — never edit manually ## Generated files — never edit manually
- `src/payload-types.ts` — regenerated by `bun run generate:types` - `src/payload-types.ts` — regenerated by `bun run generate:types`