(- noop) Providing invocations for the examples

So, I've been away from this for a while. A lot of shit is broken, and for most of it, I've not the
slightest idea why, or where to start fixing it. To boot, there's some stashed work that implies I
ran into a *huge* wall, last time I was working on this, four months ago†.

For the moment, I'm going to work on fixing the examples that don't work, to “repair” the project to
its healthiest state, because I'm *itching* to implement some Sphere-of-Ownership related shit.
Time-travel needs to exist, ASAP. Let's hope I get somewhere before burning out, this time.

I've also got some ancient Things.app to-dos relating to this project; I'll see what I can tackle
(or even understand!) from those. I'll serialize those below, for posterity.

This, my friends, is what comes of not keeping clear and sane commit logs. ಠ_ಠ

(† side-note: I feel like a *normal* fucking human being, would *remember* something from work he
did *four months ago*. I hate my life.)

- Explore exact ownership & unjux semantics for time machines
- Figure out a way to use named functions *without* typing the name repeatedly
- Add tests for rest of datatypes
- Add tests for ownership / Stagings
- Align Thing.inspect()'s output-newline-commas to opening paren
- Make Execution's “Function subclasses” so they're callable
- Add “quoted labels” to the parser
- Add WebWorker-concurrency
- Make aliens properly declare their ownership
- Re-write examples to be concurrency-safe
- Start on the IPP
- Implement an alien with the semantics of “:”
- Implement IPP-driven syntactic sugar for “:”
- Start on Unitary implementation
- Start on distribution
- Implement Spheres of Influence, and thus, time-travel
- Completely re-write the pretty-printing/debugging-output code
- Figure out why none of the examples are working on HEAD
- Figure out why examples/03-aliens.js seems to be out-of-order
- Figure out why examples/04-schedule.js is completely non-functional
- Figure out why examples/05-realize.js seems to lose access to the normal infrastructure
(fix) Fixing examples/03 and examples/05, seperating JS API from Paws natives

Got messy, having one `infrastructure` bag that I was trying to expose as both the JS API for this
library *and* the Paws-side API. So, I'm going to be putting methods *on the JS objects* for calling
from the JS-side, and keep the execution-bags exclusively for calling from within the reactor (thus
providing the context they need implicitly.)
(fix re) Starting to re-write examples/04 (scheduling) for the direct JS API
(- fix) `stage()` now assumes `this`-context, have to bind it to `earth`
(- fix examples) Opted to directly modify responsibility

Libside, we have a #charge routine to do this ... but that seems like overkill in the JS API. It's
extremely simple to dive directly into the object-structure to do so.

Yeah, yeah, tight coupling, encapsulation, ask-don't-tell, &c ... whatevs. Fuck off.
(- fix) aliens weren't properly releasing ownership upon completion
(- re)
(- fix) Making sure examples/03 and 04 eventually exit. 04 also *works* now.
(- re new) Abstracting all the world.queue.push calls out to world.stage()
(- new) Changing the function-name of aliens' subs when the alien is named
(- new) Printing a debugging error when the `thing`-receiver finds no results.
(- fix examples) Ensuring the globals are available in examples/05
(- fix re) Cleaning up reactor-debugging output
(- new) Printing things names with their IDs
(- fix) name() should accept empty arguments, with no effect.
(new) The various Object-enumerator shims should take a thisObject argument
(- re) The names of the globals should be their entire “path.”
(new) Using UUIDs for objects. (No idea if I'll keep this.)
(- re) Hide stack-size debugging information except for highest verbosities