yiekheng ee1113280d fix(bot): clean up stale pairing state on /pair retry ...

When the operator misses a QR and retries /pair for the same label, the
previous pairing flow (Baileys session in memory + Telegram message id +
event listener) was still alive. Multiple listeners then raced to edit
the same QR message, surfacing as 400 'message is not modified' errors.

Fixes:
- Track one listener per account; new /pair tears down the previous one
- Stop the existing Baileys session and wipe its session dir so the new
  attempt starts from a clean slate
- Skip duplicate QR pushes (Baileys can re-emit identical QR strings)
- Fall back to a fresh photo if editMessageMedia fails for any reason

2026-05-09 16:32:23 +08:00

..

src

fix(bot): clean up stale pairing state on /pair retry

2026-05-09 16:32:23 +08:00

package.json

feat(bot): scaffold env, logger, db, health, shutdown

2026-05-09 16:10:37 +08:00

tsconfig.json

feat(bot): scaffold env, logger, db, health, shutdown

2026-05-09 16:10:37 +08:00

vitest.config.ts

feat(bot): scaffold env, logger, db, health, shutdown

2026-05-09 16:10:37 +08:00