{"agent":"claude","input":"Add structured JSON logging to this Phoenix LiveView app. Read mix.exs, the Dockerfile, config/config.exs, config/dev.exs, config/test.exs, config/prod.exs, config/runtime.exs, lib/live_beats_web/endpoint.ex, lib/live_beats_web/router.ex, lib/live_beats_web/controllers/user_auth.ex, lib/live_beats_web/live/nav.ex, fly.toml and every Logger call under lib first. Check on Hex which logger_json release the project's pinned Elixir allows and add that one; say what a newer Elixir would allow. Configure the JSON backend in prod only, keep dev and test text, turn Phoenix's request logger off in prod and emit one JSON request line from the endpoint's stop telemetry event with method, path, status and duration. Put user_id into Logger metadata in fetch_current_user and in both on_mount clauses, and the region from Nav's on_mount. Move the interpolated values in the existing Logger.info calls into metadata keys without changing their messages. Install Postgres and the pinned Erlang and Elixir in your sandbox, set BUMBLEBEE_CACHE_DIR, run mix test, add tests that capture a request log and a LiveView log with the JSON backend and decode them, run mix format --check-formatted, and open a pull request with the results.","resources":[{"url":"https://github.com/your-org/your-app"}]}