## Summary Since the Docker build optimization in !TODO (`feat(docker): optimize build for better layer caching`), all GKG components report version `0.1.0` instead of the actual release version. ## Root cause The optimization removed `ARG GKG_VERSION` and `ENV GKG_VERSION` from the Dockerfile to avoid invalidating the expensive `cargo build` layer cache. However, this also removed the mechanism that baked the version into the container image. The runtime code falls back to `CARGO_PKG_VERSION` (hardcoded `0.1.0` in `Cargo.toml`) when `GKG_VERSION` env var is not set. ## Impact - Health endpoints (`/live`, `/ready`) report `"version": "0.1.0"` - Cluster health gRPC responses report wrong version - Version-based observability and debugging is broken