The tab bar says which build this is

Running several builds side by side means constantly answering "which one is this?". A hint in the tab bar names the build, and its tooltip carries the commit, the branch, how old the build is and the paths it is running from — kept inside the window rather than opening off the edge of the screen. The version beside them is compiled in rather than read back at runtime, because a source build and a packaged build of the same commit used to answer that question differently.

Running a source build, a slot and the installed app side by side means constantly answering "which one is this?" — and getting it wrong means testing in the window holding your real work.

A hint in the tab bar names the build. Its tooltip carries the commit, the branch, how old the build is in relative terms, and the paths the instance is actually running from — which is the question the version number cannot answer.

• The tooltip is kept inside the window rather than opening off the edge of the screen.
• The build constants can only be read from inside a running instance, which is exactly why the Builds page — which describes builds sitting on disk — reads a sidecar file instead.

• The source catalogue records no separate caveats for this entry. The implementation and evidence above define its scope.