LambdaMOO Test Frame (l8tf)

So, LambdaMOO has never had a formal test suite. Pavel may have had something he ran before sending a release out the door, but whatever it was never left Xerox. And we really need to simplify the specification and running of tests.

From a distribution tarball one should be able to unpack
```
    tar xzf LambdaMOO-1.9xxxx.tar.gz
    mv MOO-1.9xxxx moo
    cd moo
```
then, if one wants (well okay, this is more what I want, but the only way to make this more likely to happen is to make it easy), to run some kind of broad spectrum of unit and general build tests on on an entire 'schedule' of configurations (defaulting to 'smoke', a short list of configurations we really care about and a small number of tests that will finish quickly, but having there be other schedules that are larger, take longer, or have particular specialized purposes),
```
    ./tests/runall [options...]
```
and then the usual paradigm of choosing which configuration you actually want to build, building it, and then running tests specific to it to have confidence that it built correctly:
```
    ./configure [options...]
    make
    make -C t [test_targets...]
```
For actual developers using git, this expands to a somewhat more complicated unpack:
```
    git clone MOO_REPOSITORY moo
    git clone L8TF_REPOSITORY l8tf
```
followed by some magic that
1. identifies which test sources are being used, there being choices here; the unit tests would be specific to this particular C implementation of the server, but many of the general tests that go through various client scenarios and test moo language compliance would not be, the theory being that l8tf could be applicable to other-language versions of the moo server or closely related servers, but for now there would be l8tf/moo directory with sources/schemas/etc for a set of (C-)LambdaMOO-specific tests and this would be the default choice (and the rest of l8tf/* is about providing the mechanism via which l8tf/moo becomes moo/tests
2. creates the moo/tests directory
3. performs whatever configuration of l8tf is necessary for building scripts, then run the m4 constructors (autom4te -l (autotest|m4sh) to create moo/tests/runall, the individual test suites, and the utilities they depend upon,
4. includes in moo/configure.ac whatever configuration of l8tf and moo/tests is needed for running tests on the target platform (e.g., finding a usable version of netcat… hm, that may be the only thing that needs doing), and so that moo/config.status can do substitutions for make testing targets and the atconfig scripts that autotest needs (to propagate information about the server sources into the test environment). Currently this "hole" takes the form of a file testing.ac that is sincluded by configure.ac at the very end right before AC_OUTPUT.
which we should be able to wrap up in a single shell script:
```
    cd moo
    ../l8tf/install-tests [options...]
```
then create the moo ./configure script
```
    autoconf
```
which then (finally) gets us to the state that the Tarball People are in:
```
    ./tests/runall [options...]    
    ./configure [options...]
    make
    make -C t [test_targets...]
```

(to be continued, …)

As of this writing (May, 2026), the repository for this is https://github.com/wrog/l8tf.git