{"agent":"claude","input":"Make session data in this grammY Telegram bot survive restarts by storing it in Redis. Read package.json, src/config.ts, src/main.ts, src/bot/index.ts, src/bot/context.ts, src/bot/middlewares/session.ts, src/bot/i18n.ts, src/bot/features/language.ts, .env.example, the environment variable table in README.md, eslint.config.js and .github/workflows/main.yml first, and say what is stored in the session today. Add @grammyjs/storage-redis and ioredis. Add an optional REDIS_URL to the valibot config schema. Pass the session storage into createBot through its dependencies; in src/main.ts use a RedisAdapter when REDIS_URL is set and MemorySessionStorage otherwise, logging which one is in use, for both polling and webhook start-up, and close the Redis connection in the existing shutdown handlers. Read the adapter's source for how it names keys and whether they expire; set a key prefix on the session middleware and leave expiry off. Do not change when sequentialize is applied, but explain in the pull request what concurrent updates in webhook mode mean for a shared store. There is no Docker here: install redis-server from the system packages and start it. Add the test runner the ESLint config expects and tests that use the real bot with fake updates and no Telegram access: a language chosen on one bot instance is still used by a second instance on the same Redis, and is lost with memory storage; the stored key has the prefix. Run the tests, npm run lint and npm run typecheck, document REDIS_URL, add a redis service to the workflow, and open a pull request.","resources":[{"url":"https://github.com/your-org/your-app"}]}