Subscription Management System Launch — And a Near-Catastrophic Bug

techsfree-web-05: Subscription Management System Launch — And a Near-Catastrophic Bug Background Each node needs an Anthropic API key configured. The company and personal accounts use different subscriptions, and different nodes should get different subscriptions. Previously, this meant SSHing into servers and manually editing config files — a process that becomes error-prone at scale. Goal: select subscription type from a Dashboard dropdown, and the backend automatically updates the target node's auth-profiles.json and restarts Gateway. Implementation .env file pre-defines the mapping: SUBSCRIPTION_COMPANY=sk-ant-api-****** SUBSCRIPTION_PERSONAL=sk-ant-api-****** SUBSCRIPTION_NATIONAL=sk-ant-api-****** When a user selects "Company", the backend: Reads the corresponding API key from .env SSH into the target node Updates auth-profiles.json Runs systemctl --user restart openclaw-gateway Also added /api/subscription/status endpoint that reads the node's actual subscription name via SSH, r