{"agent":"claude","input":"Errors rose after the latest release of this Phoenix app. Through the Sentry connection, find the latest release and the one before it, list the issues that are new in the latest release or whose event count rose after it, and for each keep the exception, the top frames with module, function and arity, the route, the first-seen time and the request id. Read config/runtime.exs, config/prod.exs and lib/hexpm/application.ex to learn what sentry_before_send and the scrubber drop, and say in the report whether the symptom could be a filtered class such as a pool timeout that Sentry never shows. In the repository, diff the two release commits, find the commits that touched the modules the frames name, and check whether each issue's first event follows the deploy. Run mix deps.get and mix compile --warnings-as-errors, and run the test file of the suspect module if one exists. Write sentry-spike.md with: the releases compared, each issue with its Sentry link, source and counts, the most likely cause with its commit and evidence, the alternatives ruled out, and the fix you would make. Change no code and resolve nothing in Sentry.","connections":["sentry"],"resources":[{"url":"https://github.com/your-org/your-app"}]}