Copilot instructions

1---
2applyTo: "homeassistant/components/**, tests/components/**"
3excludeAgent: "cloud-agent"
4---
5 
6<!-- Automatically generated by gen_copilot_instructions.py, do not edit -->
7 
8 
9## File Locations
10- **Integration code**: `./homeassistant/components/<integration_domain>/`
11- **Integration tests**: `./tests/components/<integration_domain>/`
12 
13## General guidelines
14 
15- When looking for examples, prefer integrations with the platinum or gold quality scale level first.
16- Polling intervals are NOT user-configurable. Never add scan_interval, update_interval, or polling frequency options to config flows or config entries.
17- Do NOT allow users to set config entry names in config flows. Names are automatically generated or can be customized later in UI. Exception: helper integrations may allow custom names.
18- For entity actions and entity services, avoid requesting redundant defensive checks for fields already enforced by Home Assistant validation schemas and entity filters; only request extra guards when values bypass validation or are transformed unsafely.
19- When validation guarantees a key is present, prefer direct dictionary indexing (`data["key"]`) over `.get("key")` so invalid assumptions fail fast.
20- Integrations should be thin wrappers. Protocol parsing, device state machines, or other domain logic belong in a separate PyPI library, not in the integration itself. If unsure, ask before inlining.
21- Integrations should not implement fixes or workarounds for limitations in libraries. Instead, the library should be updated to fix the issue.
22 
23The following platforms have extra guidelines:
24- **Diagnostics**: [`platform-diagnostics.md`](platform-diagnostics.md) for diagnostic data collection
25- **Repairs**: [`platform-repairs.md`](platform-repairs.md) for user-actionable repair issues
26 
27## Entity platforms
28 
29- Ensure `async_added_to_hass()` and `async_will_remove_from_hass()` have symmetrical behavior. For example, if a subscription is created in `async_added_to_hass()`, it should be unsubscribed in `async_will_remove_from_hass()`. Also, if something is torn down in `async_will_remove_from_hass()`, it should be set up in `async_added_to_hass()`.
30- Entity base class (e.g. `SensorEntity`, `TrackerEntity`) provide a stable API for child classes to inherit from. Do not suggest redeclaring or duplicating attributes, properties, or methods the base class already provides, and do not add guards against the parent's behavior changing — rely on the base class instead.
31 
32## Integration Quality Scale
33 
34- When validating the quality scale rules, check them at https://developers.home-assistant.io/docs/core/integration-quality-scale/rules
35- When implementing or reviewing an integration, always consider the quality scale rules, since they promote best practices.
36 
37Template scale file: `./script/scaffold/templates/integration/integration/quality_scale.yaml`
38 
39### How Rules Apply
401. **Check `manifest.json`**: Look for `"quality_scale"` key to determine integration level
412. **Bronze Rules**: Always required for any integration with quality scale
423. **Higher Tier Rules**: Only apply if integration targets that tier or higher
434. **Rule Status**: Check `quality_scale.yaml` in integration folder for:
44   - `done`: Rule implemented
45   - `exempt`: Rule doesn't apply (with reason in comment)
46   - `todo`: Rule needs implementation
47 
48 
49## Testing Requirements
50 
51- Tests should avoid interacting or mocking internal integration details. For more info, see https://developers.home-assistant.io/docs/development_testing/#writing-tests-for-integrations
52