fix: keep the plan-usage chip across a degraded-to-connected upgrade

A server that comes up mid-run was upgrading the header's hostname and
version but not its chip, which then stayed blank until the next telemetry
event. Also swaps a typographic apostrophe out of a preview error, which is
not renderable on the ASCII glyph tier.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

src/tui/tui-app.ts

@@ -842,6 +842,7 @@ class TuiApp {
       ...(server.hostname ? { hostname: server.hostname } : {}),
       ...(server.instance ? { instance: server.instance } : {}),
       ...(server.version ? { version: server.version } : {}),
+      ...(server.planUsage ? { planUsage: this.planUsageChip(server.planUsage) } : {}),
     });
     await this.refresh();
     this.subscribe();
@@ -910,7 +911,7 @@ class TuiApp {
       // A tail that cannot be read is a pane-level fact, not a connection one:
       // the list stays exactly as it is and only this pane says so.
       if (this.previewSessionId !== sessionId) return;
-      this.applyPreview({ sessionId, lines: [], error: 'could not read this session’s terminal' });
+      this.applyPreview({ sessionId, lines: [], error: "could not read that session's terminal" });
     } finally {
       this.previewFetching = false;
     }