documentation, tests, makecsl

Some interesting ideas percolating in this thread …

… about having a positive feedback loop between the test suite,
documentation, and makecsl.

Given the licensing discussion as well, I guess I’m wondering about a
"master.csl" style file that consists only of macros, and then some
way to integrate that into the test suite. Perhaps master.csl is in
fact created from the test suite?