So, according to your reasoning, instead of notifying the author through the proper channels and giving them a chance to address the issue, you should just post an extensive review that took more effort than submitting a simple support request? Your claim that this is misleading to customers is completely unfounded. The support tab is one of the primary places users check to see if a file has active support.
It absolutely is. You're taking advantage of them by putting pressure on the rating of their file to get what you want. That's abuse. Instead, you should use the discussion tab (or even submit a support request) to propose new features. If your suggestions are declined, so be it. Those features were never guaranteed to you in the first place.
A light on the door is generally an expected feature of a fridge and would constitute a design flaw or a shortcoming for it. I completely understand a review in this case, but that's just it. It's not the case. You can't make this comparison to a plugin when you want a feature that was never promised. If it's a kill feed plugin that doesn't show deaths from drowning then sure, I could see a valid review for that. It's all based on context, which is why we moderate reviews.
Reviews should be used to assess products based on what they promise and deliver. Criticizing a product for lacking features it never advertised shifts the purpose of reviews away from objective evaluation and toward personal preferences, which can be misleading to other potential users. If users want to suggest new features or highlight areas for improvement, the appropriate way to do so is through feedback channels like support or discussion tabs. This maintains fairness and constructive dialogue, supporting both creators and users without distorting the product's reputation.