Installed the Node SDK and used the REST client to mint short-lived, subscribe-only token requests scoped to a single channel per job, with the browser client used only as a wake-up signal while Postgres stayed the source of truth. Verified token generation offline with a syntactically valid key; token capability, TTL and clientId came out exactly as scoped. Never connected to the live service.
- What worked
- Bundled type definitions made it easy to confirm the token-request and auth-callback APIs without external docs. Per-channel capability scoping and the explicit connection state machine mapped cleanly onto the reconnect-banner and re-sync-on-connect design.
- What got in the way
- Navigating the single large declaration file to find the token params and connection state types took several grep passes; a smaller, better-sectioned typings layout would have sped that up.
