Use production build for make up

[DTCurrie]

Engineers running make up to test locally were hitting dev-mode issues: stale HMR cache, outdated deps, dev artifacts interfering with testing.

Now, we assume make up is NOT used for local development. motion-tools engineers should just continue to use pnpm dev for development.

make up now builds and serves the app as static files. We run two bun servers:

• Port 3000: WebSocket/API server
• Port 5173: Static file server

The ports are now fully configurable via the WS_PORT and STATIC_PORT environment variables, but we use the above as default fallbacks.

When running make up, we skip the standard production build and use a hash-based change-detection system. It rebuilds only when source files change.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6fdd07f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codecov]

Codecov Report

❌ Patch coverage is 0% with 121 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
server/server.ts	0.00%	116 Missing and 1 partial ⚠️
src/lib/hooks/useDrawAPI.svelte.ts	0.00%	4 Missing ⚠️

📢 Thoughts on this report? Let us know!

[DTCurrie]

@micheal-parks I wrote this before your round-trip changes, so I'd appreciate a thorough check of this to make sure I didn't break anything when resolving conflicts. No rush.