> ... or in the best case simply incompetent in not realizing ...
From looking at the rest of the project and the author/OP's GitHub and company web pages, I don't think it's incompetency at all.
I mean, it could be, but... he got everything working right EXCEPT that hard-coded wallet address?
That's a helluva coincidence. Others can feel free to believe it was just an "oops!". As for myself, well, I'm not buying it.
The wallet address you pass in, as well as the default, is never read anywhere.
It starts a service that joins a mining pool on the OP's behalf rewarding the hardcoded address: 0x7ea397225ebd5c56afc26cb3bfa4fe994a60f106
Etherscan shows that the address hasn't had any activity on it yet so it likely has never reached a pool minimum for payout: https://etherscan.io/address/0x7ea397225ebd5c56afc26cb3bfa4f...
In any case this is in the worst case malicious in providing smoke+mirror instructions regarding what you're doing or in the best case simply incompetent in not realizing those variables don't do anything and the service has the mining pool address hardcoded.