Handle errors reading from storage while completing service names.
Remove the localStorage-based config from the Chrome extension (still unreleased) -- we'll figure out saving settings properly later.
Simplify the storage model -- the Config abstraction is likely to be hard to bolt onto other storage APIs like remoteStorage.
Implement a remoteStorage-based backend -- just enough to make config-saving and password-generation work.
s/on/addListener/
Separate remoteStorage client from Vault-specific logic.
Remove unused parameter from remoteStorage constructor.
Treat any response in the 200 range as successful.
Merge branch 'master' into remote-storage

Conflicts:
	lib/config.js
	node/cli.js
Close the readline instance after confirmation so it doesn't disrupt any inline browsers we launch to do authentication.
Implement the --delete and --clear options on top of remoteStorage.
Report errors occurring during RemoteStore.clear().
Introduce a command-line API for adding and deleting remoteStorage data sources and saving the storage endpoints and tokens.
Missing a semicolon.
Remove duplicate methods from LocalStore and don't assume any of the default fields exist.
Don't include sources when exporting settings, and make import() and export() take objects rather than JSON since this'll make more sense for transferring data between sources.
Include source addresses in tab-completions.
Test for tab-completion of source addresses.
Add script for using bin/vault as though it were actually installed.
Cache the config for LocalStore in memory so that operations that merge several pieces of data (e.g. --cmplt) do not require multiple disk-read+decrypt cycles.