I think you missed the part where the issue was closed by the bot for the user not having starred the repo, in which case - especially on high-traffic repos - the likelihood of actually seeing it is reduced.
Maintainers not auditing issues closed by their bots are irresponsible, but this problem is not related to the nature of the close-triggering condition.