fixup! docs: document running tests without sharding in AGENTS.md

Author: alan-agius4

AGENTS.md

@@ -22,6 +22,15 @@ This is the source code for the Angular CLI and related build tooling. This guid
   pnpm build --local
   ```
 
+## Coding Practices
+
+- **Imports:**
+  - Always use the `node:` protocol for Node.js built-in imports (e.g., `node:fs`, `node:path`, `node:assert`).
+  - Prefer named imports (e.g., `import { mkdtemp } from 'node:fs'`) or default imports (`import fs from 'node:fs'`) instead of namespace imports (`import * as fs`).
+  - Use type-only imports (`import type { ... }`) when importing types to avoid runtime side-effects.
+- **Classes:**
+  - Prefer ECMAScript private fields (`#field`) over TypeScript `private` keywords for encapsulated state.
+
 ## Testing
 
 - **Temporary Directories (`TEST_TMPDIR`):**
@@ -42,9 +51,6 @@ This is the source code for the Angular CLI and related build tooling. This guid
     });
     ```
   - **NEVER** use or fallback to `os.tmpdir()`. Bazel executes tests in hermetic sandboxes and sets `TEST_TMPDIR` to an isolated, sandboxed directory. Using `os.tmpdir()` can cause sandboxing failures, permission errors, or file leakage outside the Bazel sandbox.
-- **Imports:**
-  - Always use the `node:` protocol for Node.js built-in imports (e.g., `node:fs`, `node:path`, `node:assert`).
-  - Prefer named imports (e.g., `import { mkdtemp } from 'node:fs'`) or default imports (`import fs from 'node:fs'`) instead of namespace imports (`import * as fs`).
 - **Unit Tests:**
   - Run all unit tests: `pnpm bazel test //packages/...`
   - Run a specific test target: `pnpm bazel test //packages/angular/build:test`