everr-use-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. # Use Telemetry With Everr Use Everr telemetry before guessing when real traces, logs, metrics, or captured command output can explain behavior. Always check whether telemetry can help before continuing with code-only debugging. ## Critical: Only Raw SQL The ONLY query command is `everr cloud query "<SQL>"` or `everr local query "<SQL>"`. The only optional flag is `--format` (values: `table`, `json`, `ndjson`). ## Choose The Source | Question | Use | | --- | --- | | Production, deployed services, customer reports, cloud CI history | `everr cloud query "<SQL>"` | | Local app, dev server, local tests, wrapped command output | `everr local query "<SQL>"` | | Current CI run, branch status, failed jobs, workflow logs | Use the `everr-working-with-ci` skill | | Missing or stale local telemetry | Use the `everr-setup-telemetry` skill | If an Everr command fails, investigate why: collector s