KATT's blueprint format is a strict subset of Apiary's legacy blueprint format.
Beyond that, there are few similarities. KATT's purpose is to test if the server's response conforms with the blueprint response.
Regardless, thanks for the mention :)
Yes, it's bit stalled, but is not dead as it looks like. I have big set of patches for "actions", MUC, xmppflask-as-lib support, need just to found some time to make tests right and push them to the upstream. I'd planned to get them on this month, so stay tuned - April is not over (;
This is pretty exciting, I was thinking of creating an HTTP UI for controlling some stuff at home, but XMPP would be much better. Now I can talk to my house!