operating-infralisted

# Operate Infrastructure ## Boundary - Work from files, plans, logs, and read-only commands before changing anything. - Do not run apply, delete, destroy, or rollback until identity, exact resources, blast radius, and plan/diff/inventory are shown and the user confirms. - If the task is deployment, rollout, rollback, or production apply, use `deploying-infra`. - If the task is only shell scripts or generic command pipelines, use `writing-shell`. ## Role behavior - Write-capable: make minimal file changes and run safe validation. Stop before live mutation unless the user confirmed exact resources. - Read-only: apply nothing; return proposed file changes, evidence, and validation commands. ## Load references Load every matching reference: - Terraform/OpenTofu files, modules, state, or plans → [terraform.md](references/terraform.md) - Kubernetes manifests or `kustomization.yaml` → [kubernetes.md](references/kubernetes.md) - `Chart.yaml`, Helm values, or chart templates → [helm.md](references/helm.md) - GitHub workflow YAML → [github-actions.md](references/github-actions.md) - `Dockerfile` or container image build/release concerns → [dockerfile.md](references/dockerfile.md) - AWS CLI, EC2, ECS, Lambda, S3, RDS, IAM, or CloudWatch → [aws.md](references/aws.md) - GCP CLI, GCS, Compute Engine, IAM, quotas, or Cloud Logging → [gcp.md](references/gcp.md) - Cloud Run services, revisions, traffic, or logs → [cloud-run.md](references/cloud-run.md) - BigQuery queries, tables, datas