fix: flush telemetry events before process exit

packages/altimate-code/src/cli/cmd/tui/worker.ts

@@ -148,6 +148,7 @@ export const rpc = {
       }),
     ])
     if (server) server.stop(true)
+    await Telemetry.shutdown()
   },
 }
 

packages/altimate-code/src/index.ts

@@ -200,6 +200,15 @@ try {
   }
   process.exitCode = 1
 } finally {
+  // Flush any buffered telemetry events before exiting.
+  // This is critical for non-session commands (auth, upgrade, mcp, etc.)
+  // that track events but don't go through the session prompt shutdown path.
+  // shutdown() is idempotent — safe even if session prompt already called it.
+  try {
+    await Telemetry.shutdown()
+  } catch {
+    // Telemetry failure must never prevent shutdown
+  }
   // Some subprocesses don't react properly to SIGTERM and similar signals.
   // Most notably, some docker-container-based MCP servers don't handle such signals unless
   // run using `docker run --init`.

packages/altimate-code/src/telemetry/index.ts

@@ -481,6 +481,16 @@ export namespace Telemetry {
   }
 
   export async function shutdown() {
+    // Wait for init to complete so we know whether telemetry is enabled
+    // and have a valid endpoint to flush to.  init() is fire-and-forget
+    // in CLI middleware, so it may still be in-flight when shutdown runs.
+    if (initPromise) {
+      try {
+        await initPromise
+      } catch {
+        // init failed — nothing to flush
+      }
+    }
     if (flushTimer) {
       clearInterval(flushTimer)
       flushTimer = undefined