The extension's UI layer — status bar state transitions, command registration, context menu when clauses, and file-type isolation — had no behavioral test coverage. Existing tests only verified that methods did not throw, making it easy to introduce regressions (e.g., a wrong icon string, a missing when clause, or an accidentally removed command) without any test failing.