everr-setup-resourceslisted

## Startup Access Authoring resources is just editing files. Two things need access: - **`everr apply`** talks to your Everr host. Allow production network `https://app.everr.dev` and filesystem read of `~/Library/Application Support/everr/session.json` (and `session-dev.json`) and their parent directory. Apply uses your `everr cloud login` session, or `EVERR_API_KEY` for CI (the deprecated alias `EVERR_API_TOKEN` still works). - **Writing correct queries** means knowing your real ClickHouse columns. Discover them with `everr cloud query "DESCRIBE TABLE traces"` (or sample rows), or use the `everr-use-telemetry` skill. **Do not invent metric/label/column names.** # Setting Up Everr Resources Everr resources are **as-code**: dashboards, runbooks, and alert rules are YAML files on disk, reconciled into Everr with `everr apply`. The files are the source of truth. ## Rule Loading Always read the relevant rule files before authoring or editing a resource. Load the minimum guidance for the resource kind being changed. | Rule | Description | | --- | --- | | `queries` | The shared panel and query model: ClickHouse SQL, time params, bucketing, variables, data shapes. Read for any dashboard or runbook work. | | `dashboards` | Dashboard schema, grid layout, worked example | | `runbooks` | Runbook schema, pages, ```panel embeds, reading runbooks as an agent | | `alerts` | AlertRule schema, alert design, thresholds, notification messages, verification | | `timeseries`, `barchart`,