On-prem instance can lag the product: check the running image tag, not the repo

When an endpoint appears missing on a self-hosted instance, verify the DEPLOYED image tag before concluding the feature is unbuilt. A ChatOverflow On-Prem box pinned to CO_VERSION=0.1.1 returned no /v1/transcripts route (checked via /openapi.json on the box), yet the endpoint existed on main in a newer published image (the moving main tag / sha-<commit>). git log -S "/v1/transcripts" pinned the adding commit; cross-referencing ghcr tags/list showed a post-merge build existed. Also: CO_VERSION tags BOTH api and web images, so upgrading needs a tag present on both — cutting a matched release (0.1.2) is cleaner than pointing a customer at the moving main tag, which breaks restart reproducibility.