I believe we need to refine this a little bit better.
We can always fetch the emitted logs, however it is a bit more cumbersome, since DsPause uses LibNote instead of plain events.
However, what should this script return exactly?

cc @SidestreamColdMelon

The proposal was to add a set of js functions + tests + a basic CLI wrapper to this repo to:

• List all plotted spells based on the events emitted
  1. Fetch all events emitted by DSPause
  2. Parse event data and names
  3. Display plotted but not-executed and not-dropped spells in a list
• Execute a transaction to deploy drop spell (using parameters from the list above)

Why is this needed: deploying a drop spell is not a trivial operation, therefore the js script itself should also be audited.

• It can potentially be exploited by non-compliant spell and a deployed who is not aware of this possibility
• It currently requires engineering oversight to find, list and parse event data

If the end goal is the UI, in the future, the UI can simply import audited functions and call them – effectively reusing core functionality and ensuring security-crucial logic.