Fix source package resolution during development startup

[LeoXing1996]

Summary

After a dependency install without workspace build outputs, pnpm dev exits with ERR_MODULE_NOT_FOUND for @traderalice/update-lifecycle/dist/node.js. Guardian previously enabled source exports only for its backend children, after its own imports had already loaded. The frontend then independently fails to resolve @traderalice/update-lifecycle and @traderalice/connector-protocol.

Enable openalice-source when launching Guardian in both development commands, alias the frontend's workspace dependencies to their TypeScript source in Vite, and document the source startup contract. The existing package exports and backend child configuration remain the authoritative source-resolution mechanism.

Verification

• Verified the actual pnpm dev browser surface on macOS / Node 26.5.0 before building workspace packages: Quick Start rendered correctly, refresh produced no new console errors, and the previously failing update-lifecycle and connector-protocol modules returned HTTP 200. Their dist/ directories were absent during this check.
• pnpm exec tsc --noEmit — passed.
• UI pnpm exec tsc -b — passed after building its workspace declaration dependencies.
• pnpm exec tsc --noEmit --target ES2023 --module ESNext --moduleResolution bundler --esModuleInterop --strict --skipLibCheck ui/vite.config.ts — passed.
• pnpm test — 7,733 passed, 3 failed, 9 skipped; 897 files passed, 3 failed, 1 skipped. The same three test-selection assertion failures and Electron suite-loading failure reproduced in a detached, unchanged dev worktree at d2914227184b71be115ce714cd53dbeaa0ccb03c using the same installed dependencies. Test-selection failures are tracked in Test-selection subprocess contracts fail on the dev baseline with Vitest 5 #1774; the Electron failure is a local installation missing its runtime path.
• git diff --check — passed.

Boundary touch

Source development startup and frontend module resolution. Native Windows startup and the direct dev:no-relay surface have not been exercised in this change. The full hermetic suite remains failing on the baseline described above; this PR is left open for maintainer review.

[vercel]

Someone is attempting to deploy a commit to the luokerenx4's Team Team on Vercel.

A member of the Team first needs to authorize it.