everr-working-with-cilisted

## 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. # Working With CI Using Everr Use Everr from the repository root for CI state, workflow logs, test results, and pipeline timing. Start with Everr's structured GitHub Actions data before `gh`, the GitHub UI, memory, or pasted logs. If Everr fails, capture the exact command and error, then investigate wrong repo context, missing auth, missing import, no matching run, stale data, or CLI bugs. Use `gh` only after Everr cannot answer, or as a cross-check. ## Workflow 1. Identify the target: current branch/commit, PR branch, run id, workflow, job, or time range. 2. Check status or runs before logs: current commit with `everr ci status`, known commit with `everr ci status --commit <sha>`, known run with `everr ci status --run-id <id>`, or branch with `everr ci runs --current-branch`. 3. Drill down: run -> `everr ci show <trace_id> --failed` -> `everr ci logs <trace_id> --job-name <job> --log-