wtf is kiro-pro-batch?

This Chinese-language repository is a Python automation tool for signing up large numbers of subscriptions to Kiro Pro and Pro+, which are paid tiers of a product called Kiro. The author's stated goal is to script the full pipeline: log into accounts, attach a virtual credit card, and complete payment through Stripe, all in batches. The README opens with a personal vent from the author. They write that their cards have been canceled repeatedly within four hours of being issued, that they have already lost about 1100 in some currency, that they are tired of working on it, and that they are publishing the code as is with many bugs and gaps in logic. They ask users not to ask how to use it and invite pull requests from anyone willing to clean it up. They also acknowledge that the code was carved out of a larger main program, which is why it is rough. The feature list covers three login methods: a pure HTTP GitHub OAuth flow, a browser-automation flow for Google login, and a registration path for an AWS Builder ID. Payments are described as automated Stripe checkout filled in by BitBrowser, a fingerprint browser designed to make each session look like a different real user, with YesCaptcha plugged in to solve hCaptcha challenges. There is a Flask web dashboard for live status, a thread pool for running many accounts at once, and retry logic that rotates the IP when a card is rejected. The project structure section lists a file per concern: separate modules for each login method, a BitBrowser controller, a card API client supporting three virtual-card providers, a Kiro subscription module using the CBOR and Smithy protocols, a SOCKS5 proxy manager that checks for a US IP, persistence for successful and failed accounts, and the Stripe payment module. Dependencies include requests, cbor2, pyotp, DrissionPage, flask, and urllib3. External requirements include a running BitBrowser instance, a SOCKS5 proxy that exits in the United States, a virtual card API account, and the YesCaptcha browser extension. The README closes with a disclaimer saying the project is for learning and research only and tells users to obey the relevant terms of service.