Web Interface to View Command Invocations

[geowa4]

Every command invocation from Slack or a webhook must be logged. This audit log must be retrievable and viewable on a simple web interface. The entered text, user, timestamp, channel, whether it was from a webhook, and any other relevant data should be visible with the newest on top. This should update as commands are executed without the need to refresh. Keep the list of commands on the web page to no more than 100 elements. The rest can be kept indefinitely in Postgres.

[dantswain]

This and #12 and possibly #11 seem like they're beyond proof-of-concept. Do we want to limit scope of the POC or just throw whatever at it?

[geowa4]

I can think of four main categories of this application: chat commands, webhook commands, distributed execution, and security/auditing. These initial tickets aim to stub those out to prove their value and allow me to iterate on these hypotheses.