Has anyone else struggled with ArgoCD and Crossplane’s misleading health checks?

I'm going crazy here! After a week of debugging, I'm facing a weird issue with ArgoCD and Crossplane. ArgoCD shows resources as 'Healthy' and 'Synced', yet Crossplane is failing to provision AWS resources—like Lambda functions and RDS instances. AWS error codes are flying everywhere, but ArgoCD remains blissfully unaware, proclaiming 'Everything's fine!'

I've been searching for help online but found no one else talking about this issue. It seems that the health check Lua logic in ArgoCD evaluates status conditions in a way that lets anything labeled 'Ready: True' dominate the checks, ignoring critical failures.

It baffles me that nobody else has hit this problem due to the default health checks everyone seems to be using! Am I just in an alternative universe where I'm the only one who noticed this? Are people ignoring ArgoCD's status altogether? I've fixed it by reordering the condition checks, but I want to know if anyone else has experienced the same thing or if I'm just extraordinarily unlucky.

I've documented the tech details and solution in a Medium article, hoping to shed light on what seems to be an unrecognized DevOps issue. **Am I alone in this?**