{"agent":"claude","input":"Convert the blue-green Argo Rollout in this Argo CD repository to a canary rollout with analysis. Read the blue-green chart first: Chart.yaml, values.yaml, every file under templates, the README, and apps/values.yaml and apps/templates/applications.yaml to see how the Application is synced. Replace strategy.blueGreen with strategy.canary, keep both Services and rename the preview one to a canary Service, drive the steps from values with weights of 20 and 50, a one-minute pause after each, and an analysis step. Add an AnalysisTemplate whose default metric is a job provider that curls the canary Service and fails on a non-2xx answer, with an optional prometheus block in values that is off by default. Raise the default replica count so pod-based weights mean something, and say in the README why traffic routing is the next step. Replace the README's promotion instructions with the kubectl argo rollouts commands, since the Application self-heals. Run helm lint and helm template, validate the output with kubeconform using the Argo Rollouts CRD schemas, run kubectl argo rollouts lint on the rendered Rollout, bump the chart version, and open a pull request that lists exactly what was verified.","resources":[{"url":"https://github.com/your-org/your-app"}]}