Leo’s life was a loop of bug reports and instant noodles. His latest assignment was a free-to-play fighting game called Rival Clash , a soulless cash grab where a single "Bk" (short for "Break," the game’s premium currency) cost a dollar. A full combo—a string of ten hits—would cost you fifty Bk to auto-execute. Leo’s job was to test the "Auto Combo" feature, which was designed to prey on impatient players.

Leo selected Kage’s opponent, a generic karateka. He pressed a single punch button. Kage didn’t throw a jab. Instead, he erupted into a tornado of limbs—a sixty-hit combo that sent the karateka flying through the screen, out of the game world, and into the black void of the emulator’s debug console. The game didn’t crash. It just sat there, waiting.

Then Leo’s phone buzzed. A push notification from Rival Clash :

Leo’s boss called him, screaming. "What did you do? The backend logs show a single command from your QA device. It executed an infinite loop that drained every premium wallet. And the servers are now running a ghost process called 'Caleb’s Revenge.'"

The second buzz was a direct message from an unknown user: