Looks good to me. 

I had tried to remove it, thinking the `csrf` one wasn't used because
`identity` used `csrf_token` but unfortunately the `session` module
still used `csrf` and deleted it from the model during the response
transform. Instead, let the `csrf` value stick to the model to be
available on session object and mark the `csrf_token` value as the
deprecated one in the backend. Support for that will drop further in
the future.

Fix responsive styles when running Sass >= 3.4.

In Sass 3.4 the index() function now returns null instead of false. So
we just perform a truthy check in the respond-to mixin rather than a
direct comparison.

http://sass-lang.com/documentation/file.SASS_CHANGELOG.html

* Same padding to top/bottom of tags.
* Remove unused styles.
* Apply consistent padding/margins and remove extra margin above
  first line of tags.
* Update pattern library.

We're parsing the search expression for " and ' characters
to treat the text between the quotes as one unit.
But this wasn't working well, when there was a facet before the quoted part,
the quote characters were leaking into the search as meaningful characters.

I.e. tag:"no way" , the system was looking for '"no way"', instead of just 'no way'.
This has been fixed

With this proper working tag-search,
when the tag has space characters, is just adding two extra quotes.

Fix #1431

This isn't the most elegant thing. It may be time to drop
angular-bootstrap. Ah, well.

Add markdown preview, add markdown help icon, and adjust styles for markdown output

Tag Styles

The selectors and markup here could use a cleanup, but at least now
collapsed annotations that have markdown lists and things will still
collapse.

Tags Redux: styling tags

Account Management

Otherwise, this only clears at the appropriate time when triggered
by a scope change, not when triggered by keyup.

The form-input class now has the directive responsible for setting
the error classes. It watches its scope and sets the errors only
if the model is defined or pristine. This guard keeps the error class
from being set until validation passes (when the model becomes defined)
and keeps it from being cleared until the pristine state is reset.

The form-validate directive is now just a controller for form-input to
register with. It sets all fields to dirty and forces a render on
submit.

These mechanisms are better all around than trying to listen for a the
model to be undefined and setting pristine automatically. The model is
undefined whenever validation is failing. There are times when the from
should maybe be cleared but still show errors. Now, it is left up to
other code to set pristine if the form should be reset.

The $setViewValue field wasn't working.

This fixes an issue where logging in, then logging out and opening
the login form will reveal a form with error messages. This is due
to the execution order of events post login.

https://github.com/hypothesis/h/pull/1275#issuecomment-51777983