setup / teardown code needs more unification

There are basically three main "control flow" paths in the code currently: `fowl`, `fowld` and `fowl --interactive` which have some similar but slightly different setup and teardown style of code.

This stuff needs to become more unified. Or something.