Q CLI telemetry not working since 9/22 and activity dashboard login issues since 10/20

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

macOS 15.7.1 (24G231)

### Expected behaviour

1. Q CLI telemetry should be collected and sent when telemetry.enabled is true
2. Amazon Q activity dashboard should correctly show login status and usage data
3. Telemetry data should appear in the dashboard consistently

### Actual behaviour

1. Q CLI telemetry has not been working since 9/22/2025
2. Amazon Q activity dashboard reports incorrect login status as of 10/20/2025
3. Dashboard shows user as "not logged in correctly" despite successful Q CLI usage
4. Previous 2 attempts to submit this issue resulted in non-responsive Q sessions (>180 seconds)

```
[chat-transcript]
No zombie processes found. If you're experiencing a hung "diag" process, here are a few options to resolve it:

**If it's a specific diagnostic tool that's hung:**

1. **Force kill any hung diagnostic processes:**
\```bash
sudo pkill -f diag
\```

2. **If you know the specific process name or PID, kill it directly:**
\```bash
kill -9
\```

3. **Restart the Q CLI session cleanly:**
- Press `Ctrl+C` to interrupt any running command
- Type `/quit` to exit cleanly
- Restart with `q chat`

**If it's a system diagnostic service:**
\```bash
sudo launchctl stop com.apple.diagnosticd
sudo launchctl start com.apple.diagnosticd
\```

[Tool uses: execute_bash]

[Tool uses: execute_bash]

[Tool uses: execute_bash]

[Tool uses: execute_bash]

Great! The logdump was created successfully. Now let me check your telemetry settings and gather more diagnostic information:
[Tool uses: execute_bash]

[Tool uses: execute_bash]

[Tool uses: execute_bash]

[Tool uses: fs_read]

Now let me check your AWS and Q CLI configuration directories:
[Tool uses: fs_read]

[Tool uses: fs_read]

Let me check your active user state and create a comprehensive bug report with the information we've gathered:
[Tool uses: fs_read]

[Tool uses: execute_bash]

Now let me help you create a comprehensive bug report. Based on the information gathered, here's what I found:

## Bug Report Summary

**Issue**: Q CLI telemetry not working since 9/22 and Amazon Q activity dashboard showing incorrect login status since 10/20

**Environment**:
- Q CLI Version: 1.18.1
- OS: macOS
- Telemetry enabled: `true`
- Log dump created: `q-logs-2025-10-20T16-37-01Z.zip`

**Key Findings**:
1. Telemetry is enabled (`telemetry.enabled = true`)
2. No `telemetryClientId` setting found (returns error when queried)
3. Active user state shows multiple client IDs with recent timestamps
4. MCP servers loading successfully (5/5 initialized)

**Troubleshooting Data Collected**:
- Log dump: `q-logs-2025-10-20T16-37-01Z.zip` (created successfully)
- Active user state: Shows 2 client IDs with recent activity
- Configuration appears intact in `~/.aws/amazonq/`

Let me help you submit this as a GitHub issue:
[Tool uses: report_issue]

(...truncated)
```

### Steps to reproduce

1. Use Q CLI with telemetry.enabled = true
2. Check Amazon Q activity dashboard
3. Observe missing telemetry data since 9/22
4. Observe incorrect login status since 10/20

Environment Details:
- Q CLI Version: 1.18.1
- OS: macOS
- Telemetry setting: enabled (true)
- telemetryClientId: not set (returns error)
- Active user state: 2 client IDs present
- Log dump: q-logs-2025-10-20T16-37-01Z.zip created successfully
- MCP servers: 5/5 loading successfully

### Environment

```yaml

[q-details]
version = "1.18.1"
hash = "5610605baef17b76ef41448f2e943f021c2b2273"
date = "2025-10-13T22:31:07.064465Z (7d ago)"

[system-info]
os = "macOS 15.7.1 (24G231)"
chip = "Apple M2 Pro"
total-cores = 10
memory = "16.00 GB"

[environment]
cwd = "/Users/USER"
cli-path = "/Users/USER"
install-method = "unknown"

[env-vars]
PATH = "/opt/homebrew/opt/ruby/bin:/Users/USER/.local/bin:/Users/USER/.local/bin:/Users/USER/.toolbox/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Users/USER/.local/bin:/Users/USER/Library/Application Support/JetBrains/Toolbox/scripts:/Applications/Visual Studio Code.app/Contents/Resources/app/bin"
QTERM_SESSION_ID = "523d097b4ebb45c1b18ac18f458fea7e"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.18.1"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "org.tabby"

[chat-settings]

[chat-trusted_tools]
execute_bash=trusted

[chat-failed_request_ids]
none

[chat-context]
current_profile=default
profile_context=none

files=none
```