fix: resolve TDZ race on getClient/getClientUser during ready event

[SpackledJim]

Bot crashes on ready: getClientUser accessed before initialization

Commit: 5a6e4c5 — fix: resolve TDZ race on getClient/getClientUser during ready event

Symptom

After login, the bot exits on the ready event:

error: Uncaught ReferenceError: Cannot access 'getClientUser' before initialization
    at setTVDBLoadingActivity (src/lib/discordActivities.ts:53:22)
    at Client.<anonymous> (src/app.ts:34:3)

Reproduced consistently on 4.1.2 and 4.2.0 (Deno 2.5.6, Docker).

Cause

app.ts exports its client accessors on the last lines of the module, after await discordClient.login(token). The ready handler can run while that await is pending, so discordActivities.ts calls the accessor before its binding is initialized. The circular import between the two modules is why this surfaces as a TDZ error.

Fix

• app.ts: move export const getClient to directly after the client is constructed, before handlers are registered and login() is called. Remove the trailing getClientUser export.
• discordActivities.ts: import getClient and derive the user locally:

function getClientUser() {
  const user = getClient().user
  if (user == null) throw new Error("Fatal: Client user is null")
  return user
}

[cbackas]

You encounter this every time you run the container? Not to say this bug isn't real but I've never seen this issue and have had this connection logic in 'prod' for years

[SpackledJim]

I did, yeah.

This is timing-dependent (gateway/network latency), which likely explains why it doesn't reproduce for everyone every time, but reproduces consistently in a fast local Docker setup.