Version bump. Revision to "control panel" (a concept I would like to do away with entirely in favor of nested window manager instances) and some additional tweaks to the app cache monitor that seek to address observed false OBSOLETE handling in Firefox. I expectation was that should the browser fail to respond within the first two-second click interval (or whatever it's set to) and the exit state was OBSOLETE that the cache was OBSOLETE. However, this case tripped in Firefox as from the Schema debug console I can clearly see that Firefox has dispatched quite a large number of PROGRESS events. Yet, when I same the browser's cache state I see the state still marked as OBSOLETE. It should be marking DOWNLOADING, or UPDATING, or IDLE. The revision tests the app cache monitor's status against "downloading" and proceeds as above if not downloading. Otherwise, the watchdog continue to watch.