genesis-cicd

Adds one .github/workflows/ci.yml to a genesis monorepo. Railway and Overwatcher templates live in reference.md; Kubernetes uses kubernetes.md with the external lwlee2608/release-manifest actions.

• Kubernetes: after changes -> resolve, independent server -> build-server-image and web -> build-web-image paths join at publish -> deploy.
• Overwatcher: after changes, independent server -> build-server-image and web -> build-web-image paths; external deployment requires both builds to succeed.
• Railway: changes -> server/web.

Question flow

1. Read the arguments first. railway/kubernetes/overwatcher is the CD target; main-prod/release-prod is the branch model; sticky-disk opts into Blacksmith's paid Docker cache. Ask only what is missing.
2. Ask the rest in ONE AskUserQuestion call:
   • CD target: railway (Recommended) | kubernetes | overwatcher (VM running Docker Compose, deployed by the Overwatcher GitHub App)
   • Branch model: main = production (Recommended) | main = staging, release = production
   • Docker layer cache, only for kubernetes/overwatcher: GitHub Actions cache (Recommended) — free | Blacksmith sticky disk — $0.50/GB/month, also persists RUN --mount=type=cache
3. Resolve target prerequisites before writing. For Kubernetes, inspect the chart and collect missing GCP project, cluster locations, namespaces, release names, and environment values paths. Require chart support for complete digest references, not tag-only image construction. The canonical scaffold has no Helm chart: if one is missing, stop and ask whether to create it as a separate prerequisite or choose another target. Verify a published commit of lwlee2608/release-manifest and pin both actions to it; until available, report the dependency blocker rather than invent a version. Do not leave deployment placeholders in a generated workflow.
4. Confirm in one sentence, then write. Example: "kubernetes, main→staging / release→prod, GCR, GHA cache — proceed?"

Rules