Take a week to do an experimental merge to see how easy or difficult the merge is going to be:

• if this experiment goes well, we'll just use the result as-is.
• if it goes badly, we'll throw it away and come up with another strategy

look at how compatible with the merges the toolchain is

Approach:

Not merge directly (as in `git merge`) but instead introduce the LFA code as new modules in the application, and then migrate the existing application code piecemeal until the original books database is no longer referenced by the code (rather than trying to `git merge` and then fix conflicts).

Success:

The experiment will be considered successful if:

• All of the code is merged in
• The app still compiles, runs, and passes all tests
• The app can successfully view the catalog (including audio books)
• The app can successfully borrow NON-ENCRYPTED epub books

The next steps assuming the experiment succeeded would be:

  1. Reimplement borrowing and saving audio books (easy)

  2. Reimplement the Adobe DRM for encrypted epubs (possibly difficult)