This is a difficult problem, but I think that if a few of work on it together we can discover the cause and remove it, or at least discover how to detect this state automatically, and try to correct it automatically.
I am currently working on two projects.
One involves learning how to assess the state of the wireless network, using the wl command.
The other, called FAILSAFE, involves having the router check on its condition periodically, and to reset some major services, such as the wireless network, it it looks like it has gotten into a bad state.
We cannot expect the developers to "fix" this sort of problem. This is a research project, not a development project.
When we have a "stuck state", such as "can ping but no wifi and no telnet/ssh/http/https" from LAN nor WAN, we can't look inside the system.
Two basic questions — how can we get information from the router?
How can we exert influence over the router?
Do we have WAN access?
Can we use try to communicate with a suitably prepared USB stick?
Can we communicate router status via LEDs?
So, one way is to get the system to look at itself.
Of course, sending status messages off-site will help, initially, but knowing what to measure and how to measure it is most important. This is an iterative process where we improve our tools based on what we have learned with our tools.
Suppose we had a set of measurements about the system that lets us assess the condition of the system automatically, and to determine that X has gone wrong, and Y is needed to correct it.
I'll be glad to work with others, but it certainly involves work, discipline, determinatio, and imagination, rather than "which button do I push to fix this". :-)