I never did get around to writing one of these.  At this point in history,
I guess I don't regret the omission.

This will probably eventually bite me, since it could overlap with other
entry display logic, but it doesn't seem to break anything at the moment.

This is a fairly p1k3-specific thing.

- adds include_process() in WRT::Markup
- moves eval_perl() into WRT::Markup.  The way object instances are
  composed (and instance methods called) here still feels pretty janky,
  and this does nothing to help the situation.
- changes all existing $root_dir instances to $entry_dir; adds a $root_dir
  which represents the root of the archive (top-level folder containing
  the wrt.json file)

I'd be worried about the $root_dir change if I thought this module had a
single other user in the wild, but I strongly doubt that it does.  If I
am wrong and you are that user, I apologize sincerely in advance.

The include feature still has fairly unsettled semantics, but it gets the
whole thing much closer to a usable site generator.

These used to live in bpb-kit; moving them in here since they're specific
to the wrt format.

Now uses:

  wrt display
  wrt render-all
  wrt fcgi

Rename to wrt

It's shorter and the letters are all right there on the keyboard.

Rolls in render.pl stuff from p1k3.  Now gets deployed system-wide,
to /usr/local/bin.

There's nothing quite like finding a stupid bug in your stupid code you
wrote when you were like 20.

Anyway this turns out to be a nearly-pointless micro-optimization, but in
principle I think it's not wrong.

Stupid.

This reverts commit 4767c623c7.

Something is broken - only rendering a single year.

It appears to be a _lot_ faster to check "is a regular file" (knowable
just from stat, presumably) than a heuristic for "is ASCII or UTF-8", and
it's completely reasonable to treat regular files matching entry patterns
as markup blobs.