{"agent":"claude","input":"A Sentry alert fired for a service deployed by a chart in this Helm repository; its payload follows this prompt. Use the Sentry connection to read the issue, its latest event, its message and the server_name, environment and release tags. First decide whether the cause is in the chart: continue only if the message names a value, argument, hostname or environment variable the chart's templates render, and otherwise stop and report that the fix belongs in the application. In a repository shaped like prometheus-community/helm-charts, open charts/<chart>/ for the chart the release names, render it with helm template and the values the release used, and find the template and value behind the message. Add a helm-unittest case under charts/<chart>/unittests/ in the style of the existing suites, setting those values and asserting the manifest the service should receive, and confirm it fails on the current template. Fix the template or the default in values.yaml in the chart's existing style, bump version in Chart.yaml following SemVer and CONTRIBUTING.md, and add an Upgrading note to the chart README if a default changed. Run helm lint, ct lint --config .github/linters/ct.yaml and helm unittest --strict --file 'unittests/**/*.yaml' charts/<chart> with the Helm, chart-testing and plugin versions .github/workflows/ci.yaml pins. Open a pull request titled [<chart>] <short description> that changes one chart only, links the Sentry issue, quotes the message and the failing test output, and explains the cause. If it does not reproduce in the rendered manifests, stop and report what you tried.\n\nAlert payload:\n{payload}","resources":[{"url":"https://github.com/your-org/your-app"}],"connections":["sentry"]}