fix(federation): enable minification for production bundles — @originjs/vite-plugin-federation workaround

[ojfbot]

Problem

`@originjs/vite-plugin-federation` ≤1.4.x mangles its own placeholder identifiers (`_federation_expose`, `_federation_shared`) when esbuild or terser minification is applied, causing the remote to fail at runtime in the shell.

Current workaround in `packages/browser-app/vite.config.ts`:
```ts
build: {
minify: false, // affects the ENTIRE build, not just the federation chunk
}
```

This ships the production bundle (~1.6 MB exposed Dashboard chunk + main bundle) completely unminified, causing a page-load regression and exposing source-level identifiers.

Goal

Re-enable minification for production builds while keeping Module Federation working.

Investigation paths

1. Upgrade vite-plugin-federation — check if a version > 1.4.1 fixes minification.
2. Selective exclusion via rollupOptions — skip minification for remoteEntry.js chunk only.
3. Terser keep_fnames — may preserve federation identifiers while minifying the rest.
4. Check upstream: https://github.com/originjs/vite-plugin-federation/issues

Acceptance criteria

• pnpm build produces a minified dist/assets/remoteEntry.js
• Shell mounts cv-builder Dashboard without runtime errors
• No _federation* identifier mangling in output

[ojfbot]

Disposition: parked below Gas Town priority.

This affects all 9 Federation remotes fleet-wide, not just cv-builder — every repo has minify: false on the entire build. The fix requires a custom Vite plugin or terser reserved-identifier config, validated across the fleet. Targeting a workaround PR for the sprint after Gas Town MVP.

Tracked as fleet-level tech debt (HIGH severity, M effort).

---

Triaged via /frame-standup audit of daily-logger 2026-03-28