My Discord bot signs in to X through a custom API, keeps the session alive, and then proceeds with its usual commands. The Python side prepares the credentials and writes them to a secure store; the Node.js side calls the custom endpoint, receives the token set, and injects it back into Discord. Somewhere between those two pieces the login fails and the whole signup flow stalls. I need reproducible testing of the current codebase, clear identification of the breaking point, and—if the fix is straightforward—an implemented patch. You will have direct access to the Git repository, a staging Discord server, and the current API documentation for the custom X endpoint. Please trace both language layers so we know whether the fault is in the Python token generator, the Node.js request wrapper, or the handshake between them. Deliverables • concise report pinpointing the exact failure • working code (or pull-request) that completes login and preserves the session for at least 60 minutes • brief outline of the changes so I can maintain them going forward Acceptance is simple: run “npm run start” followed by “python auth.py”; the bot must appear online in Discord and successfully fetch its X timeline without throwing an error.