A dev build's popup footer and chrome://extensions row showed the bare version, so a reloaded unpacked install could not be told from a stale one. The dev channel now writes version_name — "1.4.0+2e9cb0e", with "-dirty" when the tree has uncommitted changes, which for a local build is the normal case — and the popup prefers it over version. The sha cannot go in `version` itself: Chrome accepts only up to four dot-separated integers there and refuses to load anything else. Production builds emit no version_name and are unchanged. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>