I'm glad this is getting some further consideration.
As I said in my original post, there will be legitimate differences on which technology to use. Those are implementation discussions. By explicitly declaiming that that was under consideration ("why use a Ruby versus / Python- / NodeJS- etc.") I hoped to keep the discussion, at least preliminarily, focused on the feature per se. A Ruby toolchain is not without its headaches, nor is an NPM-based toolchain.
$PROGRAM $COMMAND and violà: a test server is up and running. The test harness ships with the library. This seems like a good thing. Should work be put toward making that happen or is it impossible or is there no desire? I'm in the "for" column. That's all this request is after.
➜ $PROGRAM $COMMAND
[2012-12-13 08:51:22] INFO JqueryUI Test Server
[2012-12-13 08:51:22] INFO Some Programming Language Version blah
[2012-12-13 08:51:22] INFO WEBrick::HTTPServer#start: pid=37910 port=9292
[2012-12-13 08:51:22] Jquery UI Test Framework is up and running: visit http://localhost:8066
( optional browser launch to that URL )
The portability of the code to *also* be the web site is a really nice feature and I wouldn't want to see that get broken, but again, for this request, that's not point I'm attempting to put forward for consideration.