showdar-opslisted

# Showdar Ops ## Purpose - Analyze and perform tightly scoped operational engineering across CI/CD, containers, environments, runtime configuration, deployment, observability, rollback, and release operations. - Preserve the boundary between read-only operational evidence, local repository configuration changes, and remote or production mutation. - Produce practical plans, runbooks, configuration changes, or execution reports with explicit target, authorization, verification, and rollback evidence. - Use `data/ops-patterns.csv` as a searchable prompt and load `references/deployment.md` for rollout or execution planning. ## When to use - Inspecting existing GitHub Actions, CI/CD, Dockerfiles, compose files, package scripts, deployment manifests, health checks, or runtime topology. - Modifying an existing operational configuration when the user explicitly asks to fix or add it. - Planning or explicitly executing staging/production deployment, rollback, migration sequencing, observability, or release operations. - Reviewing environment separation, secrets/config boundaries, build variants, signing, TestFlight, Play Console, desktop updaters, or backend rollout behavior. - Creating Docker or other operational setup when the user explicitly requests that operational change. ## When not to use - Do not use this for application feature implementation; use `showdar-build`. - Do not use this for delivery/readiness assessment; use `showdar-ship`. - Do not use this for local commi