From the original cl interaction, let's first check how the test coverage is for first run.  If these abstractions would allow us to write more/better tests, then let's do that instead of deleting it.

Re: Test coverage, looks like we have the following tests:
  FirstRunFlowSequencerTest.java - unit test that just exercises FirstRunFlowSequencer code
  FirstRunIntegrationTest.java - integration test that simulates sending BACK key on FRE screen to make sure activity is closed

So there's no unit test coverage of FirstRunActivity, which is where FirstRunGlue is used. Though I'm also not sure how much the glue is helpful in writing tests for it - i.e. why would we need to abstract for example isDefaultAccountName() but not other things.

And maybe some of those can be done easier by just subclassing FirstRunActivity - for example a few of those already have methods in FirstRunActivity that just call the glue ones - like didAcceptTermsOfService, openAccountAdder, etc.

I guess the real question is which things we want to have test coverage for and whether the glue as it is implemented now is helpful for testing them or not.

Looks like FirstRunGlue and FirstRunGlueImpl no longer exist, so this is WontFix as obsolete. Yay for whoever did the cleanup.