Update circuitjson deps and disable Bun lockfile

[zergzorg]

/claim #79

Summary

• updates the core tscircuit/circuit-json dependency set to the latest versions resolved by Bun
• removes the tracked bun.lock
• ignores future bun.lock/bun.lockb files while keeping the existing bunfig.toml [install.lockfile] save = false behavior

Validation

• bun install && test ! -f bun.lock && test ! -f bun.lockb — dependencies install and no Bun lockfile is generated
• bun run build — Vite production build succeeds
• git diff --check — passes

Notes

• I cannot manually verify a Vercel preview from this local environment without project deployment access, but the Vite production build path that Vercel uses is passing locally.
• bunx tsc --noEmit currently fails on existing docs/reference-implementation.tsx missing imports/globals, which is outside this lockfile/dependency update.

[vercel]

@zergzorg is attempting to deploy a commit to the tscircuit Team on Vercel.

A member of the Team first needs to authorize it.

[zergzorg]

Follow-up after comparing current #79 attempts:

• Added @tscircuit/runframe as a direct dependency because src/App.tsx and the docs sample import it directly. This matches the actual runtime import surface instead of relying on a transitive dependency.
• Kept the lockfile hygiene scope unchanged: bun.lock remains removed/ignored and Bun still does not recreate bun.lock/bun.lockb.

Validation:

• bun install && test ! -f bun.lock && test ! -f bun.lockb — passed.
• bun run build — passed.
• git diff --check — passed.
• bunx tsc --noEmit still fails only on the pre-existing docs/reference-implementation.tsx sample references/globals, not on @tscircuit/runframe resolution.

The Vercel failure still appears to be team authorization for the tscircuit Vercel project, not a code failure in this branch.

[zergzorg]

Follow-up after checking newer #79 attempts and the Vercel context:

• Added vercel.json so Vercel uses a non-frozen Bun install, runs bun run build, and publishes dist for the lockfile-free setup.
• This keeps the existing dependency and bun.lock cleanup intact while making the deployment intent explicit.

Validation:

• bun run build
• npx prettier --check vercel.json
• git diff --check