As of yesterday, there is a new experimental, higher-level framework in the developers version of EWF. The idea is that a developer of an Eiffel web server should not need to know anything about the HTTP/1.1 specification (), and yet still write unconditionally compliant (all MUSTs and SHOULDs of the specification are met) code.
The single hardest problem with observing CQS is knowing which "functions"  you intend to call are themselves observing CQS. Ideally, the compiler would flag an error when encountering them, so you don't have to. Since this isn't happening yet, I propose to write a (conservative) CQS checker, to warn the author of a function.