{"agent":"claude","input":"Add canary rollouts with Flagger to this Flux repository. Read README.md, every file under clusters, infrastructure and apps, .fluxschema.yml, scripts/validate.sh and .github/workflows first. Install Flagger under infrastructure/controllers as an OCIRepository for oci://ghcr.io/fluxcd/charts/flagger at semver 1.x and a HelmRelease with CRDs set to CreateReplace, meshProvider gatewayapi:v1 and the chart's bundled Prometheus, plus Flagger's load tester from oci://ghcr.io/fluxcd/flagger-manifests into the podinfo namespace, and list both in the controllers kustomization. Add a Canary for the podinfo Deployment under apps/base/podinfo with gatewayRefs on the existing envoy Gateway, port 9898, an analysis of interval 1m, threshold 5, maxWeight 50 and stepWeight 10, MetricTemplates on podinfo's http_request_duration_seconds histogram for error share and p99 latency, and a load-test webhook; set httpRoute.enabled to false in the HelmRelease because Flagger owns the route, and add per-cluster patches so the Canary's hosts match the staging and production hostnames. Run scripts/validate.sh, flux migrate -f . --yes with git diff --stat, and kustomize build on both app overlays, and open a pull request quoting the output and explaining what the e2e workflow will check on push.","resources":[{"url":"https://github.com/your-org/your-app"}]}