boot.sh has printed `profile=… image=…` since the day a pod reported a
dependency missing that had already been published under its tag. It prints it
before the app exists, though -- to the container's stdout and the pod's own
boot log -- and the orchestrator collects a pod's log FROM THE APP, so the file
an operator reads begins at "lifespan start" and the build identity is not in
it. A pod serving a cached `:latest` could not be told from one serving a fresh
image using the log we actually have, which is the question those variables
were baked in to answer.

Tonight that cost a direct answer: an FP8 KV cache proved the pod was on the
new image only by inference -- FP8 cannot initialise without the precompiled
kernels the old image lacks -- which is sound but is not the same as reading the
tag.

The app says it itself now, in its first lines, and stays silent on an install
where nothing was baked.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S8LAP3ueNzQJtwzhgVbq66