* three_d:
  3D Secure Valuting

* activate-with-balance:
  Do not activate directly in cronjob

Instead, just insert and notify. sgx-jmp will handle billing and activation now
when it sees the balance is sufficient.

* invite-rewards:
  Process invite/referral rewards

Select all unrewarded codes where there are associated transactions to meet the
reward criteria, and insert the rewards to the DB.

People expect to be able to set their auto top up setting in response to a low
balance alert, and have this solve the problem instantly.  This change resets
the lock that prevents sgx-jmp from acting on a low_balance notification, and
then asks the database to check if the balance is low and issue a notify if
relevant, which would then result in sgx-jmp acting and charging their card at
the newly-configured level.

No longer used for either registrations or as a hack for payments, everything
handled by ad-hoc commands now and nothing links here any longer.

* do-not-bill-unregistered:
  Query sgx-jmp for every expired user
  Show backtrace and bail out hard on panic

* rubocop:
  Update rubocop

If they have no assigned tel, do not bill them or notify them.

And use settings from sgx-jmp

* guix:
  Build Guix package

No need to make Rakefile depend on rubocop if we don't even use it.

I missed this, but the original commit was already merged.

This is meant to go through all customers who aren't already on sgx_jmp
and who don't already have an open porting request to get them there.

Everyone gets told to go finish up with sgx-jmp

We use runitor in prod now

* fix-months-to-balance:
  Not going to run this, new plan
  Give everyone $5.0001 to prevent low balance and eat one month
  Make days correct

This way they keep most of their activation time, and the side effect of
interest is mitigated.

Fix-up for the web register previously doing 5 month activations with 0 balance
instead of adding balance + 1 month activation.

This is largely duplicated code, but the whole web-activation path should go
away soon.  This fixes web activation to produce the data we actually expect
instead of the hack previously produced.  Instead of an account activation for 5
months, we insert 5 months of balance and then bill for only one month as is reasonable.

This is a valid case for when we have sent BTC received at this address out.

Since these files didn't have shebangs, rubocop didn't look at them.
Once it started looking it found a bunch of stuff it didn't like, but
the original commit where they were written is already merged, so I'm
fixing those issues here.

I've added shebangs to the starts and chmod'd the scripts to match the
others.

Locally I just ran `bundle exec rescue` and so didn't notice until it went
into prod that they didn't match.

There were some issues with Electrum, and we lost a bit of confidence,
so I built these to help with that.

bin/check_electrum_wallet_completeness
- This one is meant to be run in cron. It checks for addresses we've
  given a user that Electrum doesn't know we have. It just prints out,
  so we get an email and can go look.
  The purpose of this is to know before our users that we're missing
  something.

bin/detect_duplicate_addrs
- This one is meant to be run in cron. It looks through the addresses
  that users has have been given to make sure the same address hasn't
  been given out to more than one person.
  It just prints out the issues, so we'll be notified and can take a
  look

bin/correct_duplicate_addrs
- This is one potential solution that can be run in response to
  duplicate addresses.
  Since I'm expecting an email from bin/detect_duplicate_addrs, this
  takes as input the text that was sent to us.
  It goes through each address and re-assigns it away from all users,
  parking the addresses on the support account so we still get notified
  when people send money, etc
  Because it takes output as input, they could be piped together in
  theory, but I never tested that because I assume some investigation
  would be warranted

bin/reassert_electrum_notification
- This script goes through every bitcoin address that's been given to a
  customer and makes sure that electrum knows to tell us about changes
  to that address

* auto-top-up:
  Default auto-top-up to $15 and allow changing from credit card management screen