AGENTS.md git:20261106.9786578A

Immutable. This exact content never changes and is served at /api/v1/blob/b8579c1d3d6eed10.

# strobe

- Read `SPEC.md` before any work. It is the source of truth. If a change conflicts with it, stop and ask. When the user agrees to a design change, update `SPEC.md` in the same change.
- Rule #1 is "valid or nothing" and rule #2 is "measure the app, not strobe" (SPEC §1). A feature that prints a number strobe cannot defend is a bug.
- Respect the module boundaries in SPEC §4.3: only `engine/` runs trace_processor, only `store/` writes `experiments/` and `recordings/`, backends return `model` types.
- NEVER write automated tests: no unit, integration, e2e, or any other tests, no test files, no test dependencies, no CI test steps. Verify with the calibration page and A/A runs on real devices (SPEC §10.3, §10.4).
- Iteration speed first. Smallest change that works.
- Never experiment on the user's real app data or config. Attach to a running app only to read.
- Strobe is generic (SPEC rule 15). Never put a product's names, paths, env vars or quirks in strobe's code or docs: they belong in that product's own `strobe.json` (`apps`, `build`, `serve`) and bench files. The only product-specific code is registering strobe with the agent harness that uses it (`up`/`leave`). `bun scripts/generic.ts` checks it (the Check workflow runs it).
- NEVER launch a desktop app the user also runs (for example their own installs of the app under test) by hand, or through strobe without an app profile whose `guard` covers the user's own state (SPEC §13.2). An app-specific test-root variable alone once replaced the user's live background service of that app. Check the guarded state before and after.
- Never run two benches on one device, and never bench while something heavy (a build, a test suite) runs on it.
- Rust stable. Well-known crates are fine; give each one a one-line reason in `Cargo.toml` and keep the budgets in SPEC §19.

## Dev environment (adais, Windows)

- Repo lives on the Dev Drive: `D:\Hona\strobe`. Sibling: `D:\Hona\mesh`.
- The shell PATH may be stale. Absolute paths: cargo `%USERPROFILE%\.cargo\bin`, gh `C:\Program Files\GitHub CLI`, git `C:\Program Files\Git\cmd`. opencode: the desktop install (mesh SPEC §6.4), not on PATH.
- A consumer to verify against: the OpenCode repo at `D:\anomalyco` (worktrees under `D:\anomalyco\worktrees`); its `strobe.json` and `packages/app/perf/*.bench.ts` live there, not here.

## Devices for manual verification

Reach them with `mesh exec <device> …`.

| Mesh name | OS | Notes |
|---|---|---|
| adais | Windows | this machine: Ryzen 9 9950X3D (two CCDs, one with V-Cache), RTX 5070 Ti |
| blade | Windows | |
| air | macOS | often offline |
| vps | Linux | no display: only non-display metrics |