OK, thanks, that all seems to make sense now, I was confused by the persistent state in the browser (cache) and maybe in Fiddler also: not sure...
There is an Online status indicator in the UI, just to confirm: that's not exposed in your API right? If it was then I could automate the whole thing without having to worry about selecting a menu item...
Regarding your RulesOption attribute: yes, of course I was referring to the examples in the chapter you mentioned, but, what is the genealogy of that "scripted specifier" syntax? I guess I can understand why you did it like that but, I would have thought a global rulesOptions object would be more idiomatic? Either way, for me anyway, it would be good to have that explained in the book. You second standard terms like "annotate" and "attribute" in non-standard ways and that's very confusing and the different syntax used in the book c.f. the default script file adds to the confusion.