$ inv docs
Failing test proving #116
As I work it feels more and more like we really need collection[name] to yield a Task that knows its canonical name. We start Executor.execute with just the name, but must hop back and forth between name and task object, both for it and its pretasks, for purposes of both deduping/ensuring no double-calling, and also for the configuration stuff.
It probably can be done without doing this - just pass around both bits of info as needed - just feels maybe a bit verbose. Will see.
Dumb issue with that idea, the tests use an 'idealized' handful of Collection objects with no tasks. Works fine for the "ask for the collection-level name/path" approach; but not when we switch it to be task focused. Still, feels dumb to try and work around it just for shorter tests. Will take a shot.
Herpaderp, all tests pass now, real world use case works now, YAY.
Overhaul Collection.configuration(), fixes #116
Forgot a changelog re #116