Copilot Instructions

# Copilot Instructions

## Project scope
- This workspace is for ESP32 reliability experiments using PlatformIO + Arduino.
- Prefer small, readable changes over broad refactors.
- Keep each file focused on one test scenario.

## Coding rules
- Keep logic simple and explicit; avoid clever patterns.
- Use clear variable names and short functions.
- Do not add external dependencies unless explicitly requested.
- Keep serial logs concise and useful for diagnostics.
- Guard long-running input paths (timeouts, max lengths, reset paths).

## Bluetooth test conventions
- Treat CR/LF differences explicitly.
- Bound all message buffers to avoid memory growth.
- Preserve behavior under disconnect/reconnect.
- Include basic counters for long-run reliability checks.

## Hardware interaction
- Use GPIO 2 LED for quick visual status when practical.
- LED behavior should be obvious and documented in setup comments or logs.
- Avoid blocking delays in `loop()`; keep response timing steady.

## Edit discipline
- Make minimal diffs and do not touch unrelated files.
- Keep formatting and style consistent with existing code.
- If behavior changes, summarize what changed and why.
- Run a compile check after modifications when possible.

## Communication expectations
- Ask before adding "nice to have" features.
- If a requirement is ambiguous, choose the simplest interpretation.
- Prefer practical reliability over feature completeness in test files.