mirror of
https://github.com/openclaw/openclaw.git
synced 2026-08-02 13:01:34 +00:00
The previous commit patched me.id into 13 contexts in one suite. That treated the symptom: the harness itself never passes botInfo, so resolveBotUserId has no fallback when a test ctx carries only a username. Fix the harness instead. Production always builds the bot from getMe(), so botInfo is present in every real path; supplying telegramBotInfoForTest matches that and drops the per-context ids. Also revives bot.media.stickers-and-fragments.e2e.test.ts, which shares the harness and failed 3/6 for the same reason and was not covered before. The other ~84 bare me literals across 8 Telegram suites are fine: those tests supply botInfo through their own harnesses. Verified, 371 pass, so no sweep.