AGENTS.md

1- Prioritize stability, then simplicity, then measurement overhead.
2- Use Playwright for scenario control, isolation, and completion checks.
3- Use Chrome Performance traces for generic browser profiling.
4- Use Electron `contentTracing` for packaged multi-process profiling.
5- Keep custom probes only for product-specific measurements.
6- Do not duplicate measurements across the harness, probes, and traces.
7- Run benchmarks serially to avoid cross-test contention.
8- Run benchmarks against production builds.
9- Keep detailed profiling opt-in when it changes workload behavior.
10- Preserve raw diagnostic data or use lossless representations.
11- Do not enforce machine-dependent performance thresholds.
12- Assert scenario completion and metric collection only.
13- Keep normal test discovery free of manual benchmarks.
14