Make the project installable from a clean checkout (ts-maps file dep, lockfile v2, vendored bun-router)

Problem

bun install fails on a clean checkout: package.json has ts-maps: file:../../Libraries/ts-maps/... (a sibling repo that may be absent) and bun.lock is lockfileVersion 2 (newer bun). The @stacksjs/bun-router@0.0.15 fix currently lives only in node_modules (a surgical drop-in), so a reinstall wipes it. Maps work only because public/js/ts-maps.mjs is committed.

Acceptance

• Point ts-maps at npm (^0.2.7) or a workspace; it's only used via import type at runtime.
• Regenerate a lockfile the project's bun can read; bun install succeeds clean.
• bun-router 0.0.15 resolves from the manifest, not a hand-patched node_modules.

Done. Verified by doing it rather than by reading the manifest: cloned the repo to an empty directory with no node_modules and ran bun install — exit 0, 198 packages, in under a second.

• ts-maps points at npm. "ts-maps": "^0.3.14", and no file: dependency remains anywhere in package.json. Installed as ts-maps@0.3.14.
• The lockfile is readable by the project's bun. bun.lock is lockfileVersion: 1, and the clean install resolved from it without complaint.
• bun-router resolves from the manifest. @stacksjs/bun-router@0.1.18 arrived in the fresh node_modules as a transitive dependency of @stacksjs/router@0.74.70, not as a hand-patched drop-in. A reinstall no longer wipes it.