Awkward space.
Starting the mesh_t* type
Fixing up the mesh type and adding some test
In theory, I have an stl_mesh_t
mesh_init() signature takes a second param for data.
stl_mesh_t* tests
reader.[ch] scaffold.

Using the same pattern from commands, a list of
readers that should be tried in order.

Eash "reader" is a pair of functions of a path.

  * a `predicate` which should cheaply determine
    if a file should be read at all.
  * a `loader` which should actually produce a
    fresh-and-valid `mesh_t *`
Starting reader tests
Meet `mesh_t* reader_load(char *)`
Test `reader_load() on an STL`
Kick the stl predicate down the road for a little bit
A theoretical ->write method
Wire up the default write function into the proto
mesh_to_bsp()
Move src/commands to mesh_t from stl_object
DO NOT LEAK. LEAKS ARE NOT FUN.
WIP: Test script [failing]
Append `.stl` to path in the default writer.
Revert "Append `.stl` to path in the default writer."

This reverts commit fcbd713fbcc25d307d92fa3c63b1393c31f220ab.
Tests for mesh_t->write()