Add automated CI/CD deployment pipeline for Kubernetes

[oyster]

Summary

• Add reusable ea-build-push GitHub Action for building and pushing Docker images to a configurable registry
• Add ea-deploy.yml workflow that automates the full build → push → deploy pipeline:
  • Triggers on push to ea_main (auto-detects changed services) or manual dispatch
  • Builds only affected Docker images in parallel
  • Runs DB migrations when migration files change
  • Restarts affected K8s deployments in ea-tracker namespace
  • Verifies pod status after rollout
• Update deployment docs with EA CI/CD flow, required GitHub secrets, service mapping, and manual fallback

Required Setup

Before this workflow can run, these GitHub secrets must be configured:

Secret	Description
EA_DOCKER_REGISTRY	Registry hostname (e.g., docker.io)
EA_DOCKER_REGISTRY_OWNER	Image namespace (e.g., rememberizer)
EA_DOCKER_USERNAME	Registry login
EA_DOCKER_PASSWORD	Registry password/token
EA_KUBECONFIG	Full kubeconfig for the K8s cluster

Test plan

• Verify workflow YAML is valid (Actions tab should show it without syntax errors)
• Configure required secrets in repo settings
• Test with manual dispatch targeting a single service (e.g., services: web)
• Test automatic trigger by merging a change to ea_main

🤖 Generated with Claude Code