Add Kubernetes migration plan documentation (#24)

## Summary
- Comprehensive phased plan for migrating blumeops services to minikube
- Technical decisions documented: Zot registry, Podman driver, CloudNativePG, Tailscale Operator
- 9 migration phases with verification and rollback procedures
- LaunchAgent absolute path requirements documented
- Observability requirements (zk docs, logging, metrics, dashboards) for new services

## Deployment and Testing
- [x] Plan document created at `docs/k8s-migration.md`
- [ ] Review plan phases for completeness
- [ ] Validate technical decisions align with requirements

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Reviewed-on: https://forge.tail8d86e.ts.net/eblume/blumeops/pulls/24

CLAUDE.md

@@ -53,6 +53,16 @@ Some important places you can look:
 ~/code/work  # FORBIDDEN, never go here, avoid searching it
 ```
 
+## Third-Party Projects
+
+When a task requires cloning or using a third-party git repository (e.g., for building from source), **ask the user to mirror it on forge first**, then clone from the mirror:
+- Mirror location: `https://forge.tail8d86e.ts.net/eblume/<project>.git`
+- Clone to: `~/code/3rd/<project>/`
+
+This avoids external dependencies and ensures the project is available even if the upstream is unreachable. Example mirrors:
+- `https://forge.tail8d86e.ts.net/eblume/zot.git` (container registry)
+- `https://forge.tail8d86e.ts.net/eblume/devpi.git` (PyPI proxy)
+
 ## Task Discovery
 
 To discover pending blumeops tasks, run: