pezkuwichain 2ed7ae3cf9 fix(bot): collapse the three-bot router down to the one bot we run ...

@pezkuwichainBot answers nothing today, for two independent reasons.

Its webhook points at vbhftvdayqfmcgmzdxfv.supabase.co — the old Supabase Cloud
project — which now returns 500, so /start never reaches this function at all.
And even once that is repointed, routing picked the bot from a ?bot= query
param and defaulted to `main`, whose mini app URL is telegram.pezkuwichain.io:
the testnet domain whose DNS record was removed on 2026-07-12. An unqualified
webhook call would have answered /start with a link that cannot resolve.

The other two slots were both dead. `krd` held the real mainnet bot and the
correct six-language welcome, but TELEGRAM_BOT_TOKEN_KRD was never set. `dks`
was @DKSKurdistanBot, whose token was revoked on 2026-07-19.

So: one token, one mini app URL (telegram.pezkiwi.app), one welcome — the
six-language one that was written for this bot and never ran. Removes the AI
chat path with it, which only the dks bot used; the same knowledge base lives on
in the `ask` function, which is the assistant still being served.

Adds the PEX.network link to that welcome and to /help. The button existed only
in the dks welcome, so it has never actually been shown to anyone.

805 -> 292 lines.

2026-07-30 01:50:30 -07:00

..

functions

fix(bot): collapse the three-bot router down to the one bot we run

2026-07-30 01:50:30 -07:00

migrations

feat(db): add ai_chat_log so the ask endpoint is actually rate limited

2026-07-29 22:36:06 -07:00

seed-admin-post.sql

Initial commit - PezkuwiChain Telegram MiniApp

2026-02-05 10:53:13 +03:00