What is running says which release it is

[ExtraToast]

Parent

#1289

What to build

Neither service names its version at runtime. The api exposes an info endpoint with no contributor data and generates no build info; the frontend embeds nothing at all.

Generate build info, embed the version in the frontend bundle, and have a post-rollout check assert that the version being served is the version that was released — which catches the silent failure where everything reports Ready but the image never actually changed.

Acceptance criteria

• The api reports its release version at runtime
• The frontend exposes its release version to a request that asks for it
• A post-rollout check fails when the served version is not the released one, demonstrated
• Support can answer "what is running" without reading the cluster

Blocked by

• api and frontend promote as a pair, or not at all #1294 — needs the Canaries