Proper readme coming soon.
Monitor user stories in production on a rolling basis - as a cron would.
See mother-example
- request authentication
externalize yaml configurationproper left side errors- alert webhook (i.e. slack) on story/step failure
- condition checking on response
- user stories via directory (re-usable !inlcude for story definitions)
- passable context from previous requests
change binary to run forever, self-invoking on defined frequency- persist analytics surrounding history of requests
- API to expose persisted data - graphs