Action parameters.

A very clear flaw of the current design is that actions can't be easily reused in sequence since they all read from the same config object. e.g. it's not possible to use `navigate` for navigating to 2 different URLs, it's also not possible to .

Actions should be able to define their own parameters, the main program should provide a way to elaborate the arguments, and finally `runActions()` should feed arguments accordingly.

The implementation won't be hard; how to design the command line option is more crucial. Specifically, for a sequence actions A, B, and C. How could users put down the arguments for A and C if B doesn't need one?

Start by tracing the action definitions, the main program's command-line argument handling, and runActions(), which the issue identifies as the affected entry points. Define how a sequence such as actions A, B, and C receives arguments when only A and C need them. Done means actions can declare parameters, the command line can express them unambiguously, and runActions() passes the corresponding values to each action.

Written by the indexing model from the issue text.