feat: produce single executable binary

[rtorresware]

Leverage bun to produce a single executable binary.

The registry pattern was used so bun could know the code at compile time (required for a single executable binary).

A big portion of the code additions is the bun.lock file.

---

Note

Medium Risk
Medium risk because it changes core CLI command resolution/loading and build-time asset handling; missing/incorrect registry entries or YAML loader differences could make commands/specs unavailable at runtime.

Overview
Refactors command discovery/loading to be compile-time resolvable by replacing filesystem existence checks and dynamic import() path probing with a centralized static src/lib/registry.ts (getModule/hasModule).

Changes spec loading to import specs.yaml directly (with a new *.yaml TS module declaration) and updates tsup/esbuild to load .yaml as text instead of copying the file post-build. Adds the generated bun.lock lockfile to support Bun-based builds.

^{Written by Cursor Bugbot for commit 123fd00. This will update automatically on new commits. Configure here.}

[designcode]

Thanks for the PR @rtorresware. As I mentioned in the original issue, our current focus at the moment is to add missing features.

[ovaistariq]

@rtorresware thanks for the contribution.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}