Indicate failure of test
Test fg debug option combos
Rename variable

- since it can also be called directly from bg code when dispatching to
  an Fcommand with 'bg' context, it doesn't make sense to call the
  parameter 'response'
Test FactotumBg.runBgCode
Remove unneeded comment

- already implemented
Remove unneeded code

- leftover from prior implementation where the Fcommand code was run in
  the content-script context instead of within the page
Reflect Fcommand extracted data refactor

- help markup was moved into the extractedData member
Remove comment

- initial implementation is done and the comment reflected old thinking for
  an approach I didn't go with
Correct doc
Update TODO

- Fcommand.js refactor implemented this
Move browser page check into dispatch

- this means you can enter any Fcommand while a browser page is active and
  have a bg Fcommand work
- notify of inability to run page-Fcommand from a browser page
- stop looping over Fcommands as soon as a single Fcommand was dispatched
Update TODO

- distinction between internal and external pages is done
Update TODO

- no popup page showing last N Fcommands.  Popup will likely be a simple
  menu with a link to a full app settings-type page
- commands are now page/bg context
- no option to toggle error notifications.  They'll be collected and
  available via some settings page
- no current plans to support simple notification content passed back from
  the Fcommand code.
- might be useful to have a method that can log a message in the bg
  page so that it appears in the collected log (kind of like console.*
  methods).
Move popup.html in html/
Remove crud
Initial support for storing Fcommands

- backed by IndexedDB, using Dexie.js as storage interface
- add 'order' and 'enabled' fields to Fcommands
- FcommandManager updated to handle CRUD operations on Fcommands
- FcommandManager tests disabled for now, so DB setup and teardown can be
  propertly managed during testing