[prestoncabe]

Summary

Changes to AGENTS.md from a retro on #586:

 ## Setup and common commands
 - All tests: `devbox run test` (… e.g. `devbox run test -- builder-frontend` …)
+
+Project tools (`mvn`, `npm`, `bru`) come from Devbox and are not on `PATH`. Run the
+commands below inside `devbox shell`, or wrap one as `devbox run -- bash -c "<command>"`;
+`devbox run` starts at the repository root.
+
-  … then `(cd library-api/test/bdt && bru run)`
+  … then `(cd library-api/test/bdt && bru run)`. To run one folder, pass `-r` …
-- End-to-end tests: `bin/run-e2e-tests`
+- End-to-end tests: `bin/run-e2e-tests [spec ...]`, e.g. `bin/run-e2e-tests tests/screener.spec.ts` …

 ## Repository map
-- `builder-frontend/`: Solid.js and Vite screener editor.
+- `builder-frontend/`: … Read `builder-frontend/README.md` before changing its form-js extensions or tests that render a form.

 ## Working conventions
-- Preserve unrelated work in the working tree and keep changes scoped to the request.
-- Follow existing patterns in the component being edited; consult its README …

Evidence

• Before: outside Devbox, mvn and bru are not on PATH, so (cd builder-api && mvn test) as written fails. npm may resolve to a host install instead (here, mise's Node 26.7.0, while Devbox provides 22.23.2). Agents have only got this right from a per-user memory note.
  After: the devbox run -- bash -c "…" form runs the builder-frontend suite (54 files, 389 tests, on Share one screening session between Preview and published screeners #586).
• bin/run-e2e-tests tests/screener.spec.ts tests/crmIntegration.spec.ts … ran just those specs (21 passed) inside devbox run. The runner exits unless DEVBOX_SHELL_ENABLED=1.
• From the collection root, bru run ran all 176 requests (the count of request files) during the e2e run, so -r matters only for single-folder runs.

Merge Danger

Door: two-way

Documentation only.

Blast Radius: agents

Only changes what agents read when they work in this repo.

🤖 Generated with Claude Code