Feature request: render the custom statusLine in the VS Code extension panel (parity with spinnerVerbs)

Summary

The custom statusLine (configured via statusLine.command in ~/.claude/settings.json) is not rendered anywhere in the native VS Code extension panel (sidebar webview, claudeCode.useTerminal: false). The command is honored functionally, but its output has no surface in the panel UI — it only appears in terminal mode.

Context / prior art

#22588 shipped custom spinnerVerbs rendering in the extension UI via a claudeCode.spinnerVerbs VS Code setting, giving panel users parity with the terminal for that surface. The statusLine is the other terminal-bottom surface with no panel equivalent: the config is read, but the webview never paints the result.

Ask

Render the configured statusLine output in the extension panel (e.g. a row at the bottom of the chat view), honoring the existing statusLine.command. Ideally expose a claudeCode.statusLine VS Code setting for parity with how spinnerVerbs was exposed, so panel users can configure it the same way.

Multi-line statusLine output should be supported (or at least documented as clipped), since scripts commonly emit several rows (cwd, model, plus custom widgets).

Use case

A custom statusLine is a primary way to surface at-a-glance context (cwd, model, git state, and user-defined widgets). Panel-only users currently lose all of it, which is a real gap for anyone who's moved off the integrated terminal to the sidebar UI.

Environment

• Claude Code for VS Code: 2.1.210
• Mode: claudeCode.useTerminal: false (sidebar panel)
• OS: macOS (Darwin 25.4.0)