Python Discord bot hosting, without keep_alive hacks

Three things make a discord.py repository deploy cleanly anywhere:

1. requirements.txt at the root, versions pinned. Major bumps of discord.py have broken login flows before, and "it worked yesterday" is almost always an unpinned dependency.
2. The token from the environment, never in code: client.run(os.environ["DISCORD_TOKEN"]). Request only the intents you use; message_content, members and presence are privileged.
3. A clear entrypoint: main.py or bot.py at the root. That is what the host runs; a missing start command is found for you.

PrivilegedIntentsRequired: the intent is enabled in code but not in the Developer Portal under Bot, Privileged Gateway Intents. Flip the toggle there; the code alone is not enough.

LoginFailure: Improper token: a regenerated token, or an environment variable with a trailing space or quote. Copy it again exactly. The crash doctor reads the traceback and names both of these within a minute.

1. Host a bot, connect GitHub, pick the repository. Python is detected from requirements.txt.
2. Add DISCORD_TOKEN and any API keys as environment variables.
3. Deploy. The console streams your print() and logging output live.
4. Every push to the default branch redeploys the bot. A bad deploy rolls back to the previous one in one click.

The Flask plus uptime-pinger pattern exists to trick sleeping platforms into staying awake. It wastes RAM, adds an attack surface and still fails when the pinger has an outage. Here the process simply runs, restarts if it crashes and comes back after node maintenance. Delete keep_alive.py; the bot gets lighter and more reliable at once.