v0.1.3 — reconcile with npm, publish the stranded flags

Published as @moshcoder/moshpit-resolve@0.1.3.

Added

Work that had been on main but reached no published build:

• --timeout MS — registry request deadline, threading timeoutMs through lookupMoshpit() (default 8000)
• --console URL — a custom namespace management console
• --parking URL — a custom base for unpointed names
• validation for every value-taking flag — --registry with no URL is now an error instead of silently swallowing the next flag as its value, and --timeout must be a positive integer

Why 0.1.3 and not 0.1.2

npm served 0.1.2, but no commit ever set that version — it was bumped in a scratch worktree, published from there, and the bump was never committed. main therefore read 0.1.1 while the registry served 0.1.2, which meant this repo could not be published at all: its own version was already taken.

0.1.3 skips the orphaned 0.1.2 and puts git and npm back in agreement.

Compatibility

Purely additive. The public export list is identical to the published build — nothing removed, nothing renamed; resolutionFor and destinationFor both remain.

Verified

From the tarball pulled back down from the registry, not the source tree: version 0.1.3, --help lists all three new flags, and both validation paths reject bad input. 27 tests, 27 pass.

v0.1.1

Adds the ./package.json export.

Tagged retroactively; this repo had no tags before.

Note: npm currently serves 0.1.2 for @moshcoder/moshpit-resolve, which was published without the version bump ever landing in git. Meanwhile main carries a timeoutMs option for lookupMoshpit that is not in any published build. Reconciling that needs a 0.1.3, which is deliberately not part of this retroactive tagging.