[FEATURE] Surface the token counter independently of viewMode: "verbose"

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

The running token counter in the notification area is currently only visible when viewMode is set to verbose (see settings docs and the statusline docs, which notes that verbose mode adds a token counter to the notification area).

Verbose mode is a heavy switch — it also turns on full turn-by-turn output, raw tool results, and other detail that many users explicitly don't want. The token counter, by contrast, is a tiny single-line readout that's broadly useful regardless of how chatty the rest of the UI is. Coupling the two means users who want the counter have to accept a noisier session, and users who like the default compact view never discover the counter exists.

Proposed Solution

Add an independent setting that controls the notification-area token counter on its own, e.g.:

{
  "showTokenCounter": true
}

…defaulting to true. It would apply regardless of viewMode. An auto | always | never enum would also work if a tri-state is preferred (e.g., auto could show it once usage crosses some threshold).

Why default-on: the counter is low-information-density, doesn't compete with other UI, and is exactly the kind of ambient context that's useful to have without asking for it. Hiding it behind verbose mode means most users never learn it's available.

Alternative Solutions

• Leaving it as-is and documenting the verbose-mode behavior more prominently — but this doesn't help users who want the counter without the rest of verbose mode.
• A custom statusline script via #11535 — but that's a different scope (data piping for users who want to build their own statusline), and shouldn't be the only way to get a built-in feature back.

Priority

Low - Nice to have

Feature Category

Interactive mode (TUI)

Use Case Example

1. I run Claude Code with the default viewMode because I prefer the compact, summarized output.
2. I'm in a long session and want to keep an eye on context usage so I can /compact or /clear at a sensible point.
3. Today I have to either flip on viewMode: "verbose" (and get a noisier session) or write a custom statusline script.
4. With showTokenCounter: true as the default, the counter would just be there — same as it already is for verbose users — without the rest of verbose mode's behavior.

Additional Context

Related issues (mentioned for context, not as duplicates):

• #10593 (closed) — Real-time Token Usage Indicator in CLI — appears to have been addressed by adding the counter to verbose mode; this request is specifically about decoupling it.
• #11535 (open) — Expose token usage data to statusline scripts — different scope (data piping for custom statuslines).
• #33978 (open) — Built-in Usage Analytics Command (claude usage) — broader usage-tooling meta-issue.

I searched existing enhancement issues and didn't find one specifically requesting that the verbose-mode token counter be made available independently of viewMode.