storyletengine CLI 0.1.0

storyletengine can say which build it is

A standalone binary has no package.json beside it and no npm to ask, so before
this there was no way to answer "what are you running?" - the first question any
support conversation opens with, and one that matters more for a downloaded
executable than for anything installed by a package manager.

--version, -v, and a bare `version`, all three, because people try all three.

The number comes from package.json, imported and inlined at BUILD time rather
than hand-copied into a constant. Both shipping paths bundle the same entry and
both inline the import, verified on real artifacts rather than assumed: the tsup
dist/cli.js prints 0.1.0, and so does the Bun --compile signed macOS binary on
all three spellings. That is what stops the binary disagreeing with the tag its
release asset is named for.

The test pins the printed string to the manifest rather than to a literal, so it
cannot pass by agreeing with a copy of itself. Probed both ways it can fail: with
the dispatch broken it goes red, and with the version hardcoded to 9.9.9 it goes
red naming both numbers. It also asserts the flag appears in the usage text,
since an undiscoverable flag is only half-shipped.

Patter's CLI has the same gap and does not have this fix. Written up for them
rather than left as a quiet divergence.