Remove stuff before trying all over w/ the modular approach
Jet::Engine is now based on Moose roles. This means that every action
can be amended with method modifiers etc. Also, all phases are stored in
arrays, so at some point in the future I might make it possible to
control the flow by adding or (especially) removing to or from these
arrays.
Also, t/engine.t now tests something sensible.
Putting the basenode on the stash belongs to an engine part. So now it's
removed from lib/Jet.pm
Create the basetype's engine class and use it whenever there's a new
basenode of that type passing by.
New Jet::Engine, default, with Jet::Part::Basenode
The partname trait is the one maing the magic happen. I think it can be
made to accept more attributes with parts, so e.g. Jet::Engine::Default
can be extended seamlessly.