journal processing refactored

Everywhere I check past transactions, I'm now using the same code and accessing the consolidated transactions.

Next step is to consider assigning a uuid to each command (in tki, wiki and web). If I can do that, then I can display commands rather than operations in the journal--much more user friendly--and use the last transaction time as the operation time. Makes navigating time a bit more reasonable, and without having to deal with state in the middle of an update.