Named actions

[alex-dixon]

UI should have an expand/collapse table with human readable names that correspond to actions, or facts unconditionally inserted from outside the session that correspond to event 0 of each state

• Actions should be discoverable within the devtool at runtime or registered in Precept and sent to the devtools ahead of time
• Each row's title should default to the inserted fact
• Each row's title should be customizable via a text input
• When a custom row title is added, it should be paired with the fact it corresponds to and written to a .precept-config.edn file via the server
• Actions defined in the app that are not identified by fact should not be persisted
• Each row should contain a delta icon that lights up when an action fires
• A state view contextual to the action and its resultant calculations should be visible within the action's table cell
• A line chart should be used to represent fact inserted by the action as shown in the drawing above. Lines indicating additions and removals should be shown.
• defconseq should be added to Precept as an optional drop-in replacement for then that registers the action by its name, namespace, and the facts it inserts. Note these may not be resolved at runtime.