use important in a few places I missed, to be consistent.
Don't show a trailing slash in vomnibar history results. It makes the display cleaner.
Add a developer flag to render the relevancy scores of the vomnibox
Hide results below a certain relevancy threshold.
Ignore any matches between the query and the target which are 2 characters are less.
In css, emphasize fuzzy matches in the title.
Don't render fuzzy matches less than 3 characters in the ui

They're aleady being discarded for ranking purposes.
Rename class to searchArea
Rename the force parameter
Update to the latest shoulda
Move shoulda.js checkout to tests/ folder.
better explain what we're getting from the background page
Remove maxresults option, which isn't currently used.
Css changes to accomodate a 2-lined suggestions UI.
Have Function.curry take varargs instead of an array.
Use a less wasteful escapeHtml function
make utils.js work in a commonjs format.
A cakefile for autobuilding coffeescript and running tests.
Remove completion.js to make way for the coffeescript implementation
A WIP rewrite of completion in the vomnibar.

The purpose of this refactor is to simplify the contract so it's easier
to modify, and to make some substantial usability improvements.

One of the key differences is that matching is no longer fuzzy. If you
want to search more than one term, separate them by spaces. This matches
the behavior in Firefox.

While fuzzy matching is a nice experience for a limited set of known
items (like files in the current project), it doesn't work well for
a huge messy collection, like URLs in your history. The query "hello"
will match random stuff from your google search results for instance,
and it's hard to prune that noise using ranking intelligence.