Bug Description

openclaw gateway restart displays a warning about token mismatch even when the config and service file tokens are identical:

⚠️ Config token differs from service token. The daemon will use the old token after restart.
Run `openclaw gateway install --force` to sync the token.

Reproduction

1. Run openclaw gateway install --force
2. Run systemctl --user daemon-reload
3. Run openclaw gateway restart

The warning appears despite tokens matching.

Evidence

Config file (~/.openclaw/openclaw.json):

"gateway": {
  "auth": {
    "mode": "token",
    "token": "35779c1924decbaa78d57ce8eff43fdef3dc3225de6126c9"
  }
}

Service file (~/.config/systemd/user/openclaw-gateway.service):

Environment=OPENCLAW_GATEWAY_TOKEN=35779c1924decbaa78d57ce8eff43fdef3dc3225de6126c9

Both tokens are identical (35779c1924decbaa78d57ce8eff43fdef3dc3225de6126c9), but the CLI check incorrectly reports a mismatch.

Environment

• OpenClaw version: 2026.2.24 (df9a474)
• OS: Linux (systemd user services)
• Install method: npm

Impact

Cosmetic issue. The gateway functions correctly despite the warning, but it's confusing and suggests a broken state when everything is actually fine.