everr-setup-telemetrylisted

## Startup Access Before using the everr CLI, request for the smallest sandbox access that lets Everr commands work: - Filesystem read: `~/Library/Application Support/everr/session.json`, `~/Library/Application Support/everr/session-dev.json`, and their parent directory. - Local network: `127.0.0.1`, `localhost`, and the ports 54318, 54320, 54418, 54420. - Production network: `https://app.everr.dev` If the current tool cannot ask for a blanket permission grant, request scoped command approvals before the first Everr command instead of trying a sandboxed command that is expected to fail. # Setup Telemetry With Everr Use this skill when an app, service, test, script, or command needs to emit telemetry into Everr. For alerting rules on that telemetry (and dashboards or runbooks), use the `everr-setup-resources` skill. Local telemetry lets development match production behavior closely, and debug telemetry lets the agent collect extra evidence locally without guessing from the code. ## Rule Loading Always read the relevant rule files before editing instrumentation. Use the table below to load the minimum guidance for the code path being changed. | Use case / rule | Description | | --- | --- | | `resolve-values` | Resolve configuration values from the codebase before hardcoding or asking | | `resources` | Resource attributes: service identity, version, environment, instance | | `spans` | Spans: naming, kind, status, attributes, and hygiene | | `logs` | Logs: structured log