Auralogger troubleshooting — env, imports, get-logs filters

Fix wrong cwd, missing AURALOGGER_PROJECT_TOKEN or AURALOGGER_USER_SECRET, server-only code in browser bundles (use auralogger-cli/client), and invalid JSON in get-logs filters.

Troubleshooting checklist
- Run CLI from folder containing .env / .env.local.
- Get values from /projects -> your project -> Setup guide.
- Confirm AURALOGGER_PROJECT_TOKEN is set.
- For encrypted mode, confirm AURALOGGER_USER_SECRET is set server-side.
- In browser code, import from auralogger-cli/client and avoid server-only deps.
- For get-logs filters, pass valid JSON values on the command line.

Common fixes
- Wrong cwd:
  - move to app directory before running init/check/get-logs.
- Missing credentials:
  - run init or set token/secret/session explicitly.
- Browser bundling failures:
  - switch imports away from server entrypoints.
- Filter parsing failures:
  - use array syntax such as -type '["error"]' even for one value.

Troubleshooting

Most issues are environment loading (wrong directory), missing credentials, or importing server-only code into a browser bundle.

Get env values from the project setup guide:

  1. Go to Projects (/projects).
  2. Click your project.
  3. Click the Setup guide button.
  4. Copy the env keys from the guide.
Checklist
- Run CLI from the folder that contains .env / .env.local
- Get env values: /projects → your project → Setup guide → copy env keys
- Confirm AURALOGGER_PROJECT_TOKEN is set
- For encrypted mode, confirm AURALOGGER_USER_SECRET is set (server only)
- If filters fail: values must be valid JSON on the command line