styles(avatars): fix the gravatar button alignment
feat(signin): Add cached signin
Merge pull request #1449 from vladikoff/login-chooser

feat(signin): Add cached authentication credentials
fix(hsts): force hsts headers and use milliseconds
Merge pull request #1615 from mozilla/issue-1614-hsts-header

fix(hsts): force hsts headers and use milliseconds

Fixes #1614
r=ckarlof
feat(client): Add support for `preVerfiyToken`.

`preVerifyToken` is sent by trusted RPs to indicate that a user is already verified. The Auth Server
then does a dance with the trusted RP to determine whether to create an account for the user without
the need to verify their email address. If the user is pre-verified, the signup flow completes at the
`/signup_complete` screen. If the pre-verification fails, the user is still requried to verify their
email address as is currently done.

This PR also introduces the concept of a "Relier" model. A Relier is a model
that represents an RP and information about/from the RP.

fixes #1540
Merge pull request #1607 from mozilla/gravatar-icon-alignment

styles(avatars): fix the gravatar button alignment
fix(styles): Un-nesting some CSS to fix /signin links
Merge pull request #1622 from pdehaan/issue-1620

fix(styles): Un-nesting some CSS to fix /signin links.

This nesting was causing the links to not be properly floated left and right.

r=ckarlof
pre-verify tokens work end to end!

* Add functional tests for the preverified flow.

To test using 123done, apply the following diff to fxa-auth-server/

diff --git a/config/dev.json b/config/dev.json
index 7919bd9..f08a03a 100644
--- a/config/dev.json
+++ b/config/dev.json
@@ -19,5 +19,6 @@
   "bounces": {
     "region": "us-east-1"
   },
-  "customsUrl": "none"
+  "customsUrl": "none",
+  "trustedJKUs": ["http://127.0.0.1:8080/.well-known/public-keys"]
 }

Then visit:

http://127.0.0.1:8080/api/preverify-signup?email=<your_email>
Merge pull request #1606 from mozilla/issue-1540-preverified-emails

feat(client): Add support for `preVerifyToken`.

A preVerifyToken is sent by trusted RPs to indicate that a user is already verified. The auth server
then does a dance with the trusted RP to determine whether to create an account for the user without
the need to verify their email address. If the user is pre-verified, the signup flow completes at the
/signup_complete screen. If the pre-verification fails, the user is still required to verify their
email address as is currently done. See https://github.com/mozilla/fxa-auth-server/blob/master/docs/api.md#preverifytoken for further information on preVerifyTokens.

This PR also introduces the concept of a Relier model. A Relier is a model
that represents an RP and information about/from the RP.

fixes #1540
r=ckarlof,nchapman
chore(build): Adding jscs validateIndentation rule

Conflicts:
	app/tests/spec/lib/fxa-client.js
Merge pull request #1619 from pdehaan/jscs-validate-indentation

chore(build): Adding jscs validateIndentation rule
chore(docs): Update README badge [skip ci]

Jenkins plugin updated the badges, now we don't need to change the image height anymore
WIP feat(client): Add our first broker - FxDesktopBroker.

* app-start creates a broker.
* Simplify the start page selection logic.
* Ask the broker what the start page is.