{"agent":"claude","input":"Add tenant isolation to this Flux repository. Read every file under clusters, apps, infrastructure, .sourceignore, .fluxschema.yml, scripts/validate.sh and both GitHub workflows first, and list which team each namespace label names and which Kustomizations run with the controller's cluster-admin rights. In each cluster's flux-system kustomization.yaml extend the existing controller patch with the no-cross-namespace-refs flag on every controller that supports it including source-watcher, no-remote-bases on the kustomize controller, and the default service account flag on the kustomize, helm and source-watcher controllers, and patch the flux-system Kustomization's serviceAccountName to kustomize-controller. Give the infrastructure Kustomizations the same account explicitly. Create a tenants directory with a ServiceAccount per tenant namespace bound to the admin role in that namespace only, move the tenant namespace there, and replace the apps Kustomization with a platform-owned tenants Kustomization plus a tenant-owned one in the tenant namespace running as the tenant account from its own artifact, keeping every sourceRef and dependsOn in-namespace. Update .sourceignore. Run scripts/validate.sh and flux migrate as the test workflow does, then install Docker and kind in the sandbox, bootstrap the staging cluster from the working copy as the e2e workflow does, wait for the Kustomizations and the podinfo HelmRelease, and prove the lockdown with one cross-namespace sourceRef and one HelmRelease without a service account, quoting both denials. Open a pull request.","resources":[{"url":"https://github.com/your-org/your-app"}]}