This doing like 5 different things, can we split it apart? e.g.:

• Move/rename controllers.
• Switch to modular transactions.
• "Manager" string updates.
• UI updates to menus.
• New features/workflows after all that infrastructure stuff is in place.

Phortune is somewhat difficult to test convincingly and doesn't get much usage during the week until we deploy it, so I'd like to take extra care here to try to spread risk across a lot of small, low-risk events instead of concentrating it into a gigantic "rewrite everything" change that leaves me scrambling to figure out what's going on after I deploy it and billing breaks.