Point contributors at the scoped test command

A bare `bun test` also scans vendor/, inflating pass/fail counts by
hundreds and making the count meaningless to compare across
branches.

Author: TheGreatAxios

AGENTS.md

@@ -39,11 +39,15 @@ When refactoring replaces an old path, delete the old one. No back-compat shims,
 ```bash
 bun run typecheck
 bun run build
-bun test
+bun run test
 ```
 
 Run the full suite before declaring any task complete. Do not substitute individual targets. If a failure is pre-existing and unrelated to your change, say so explicitly.
 
+`bun run test` runs `bun test ./src ./tests ./evals`. A bare `bun test` also
+scans `vendor/`, adding hundreds of unrelated results and making pass/fail
+counts meaningless to compare across branches — always use `bun run test`.
+
 ## Commits
 
 Follow the `style` skill's message format: plain-English summary, no `feat:`/`fix:` prefixes, no filename in the summary. Separate refactors from feature additions. Commit with the user's local git identity.