v0.5.1

Fixed

• Signing in and connecting an account no longer fail with an internal error. The hosted
  server holds one connection to its key database, and a managed Postgres closes a connection
  that has sat idle. Writes reopened it; reads did not. Connecting an account reads before it
  writes - it looks up the application, then lists the account's keys - so the first person to
  arrive after a quiet spell met an internal error, and so did everyone after them, until the
  server was restarted. Authorised tool calls failed the same way and for the same reason.
  Every read now reopens a dropped connection the way writes always did, and the connection
  asks for TCP keepalives so an idle drop is noticed before somebody runs into it. A
  self-hosted server on SQLite was never affected.