Investigate source-first workspace package consumption

[joshuasilva414]

What to build

Produce a tested recommendation for developing the HackKit Web App against workspace package source without manually generating dist artifacts first.

The investigation should distinguish the fast inner-loop development workflow from production builds, package publishing, and executable delivery. It should identify where compiled artifacts remain a necessary boundary rather than assuming every package can use the same approach.

Acceptance criteria

• Map where development, typechecking, tests, HackKit CLI execution, and package publishing currently depend on generated dist artifacts.
• Compare viable source-first approaches and document their tradeoffs, including compatibility with the current pnpm, Turbo, TypeScript, and Next.js setup.
• Prototype the strongest approach across representative workspace boundaries: HackKit Core, HackKit UI, a HackKit Plugin, and the HackKit CLI.
• Demonstrate that an edit to workspace package source is picked up by the HackKit Web App during development without manually rebuilding that package.
• Verify that typechecking, tests, and production builds remain reliable under the proposed workflow.
• Define the build and publishing boundary for packages that still need compiled output, including any exception required for the HackKit CLI executable.
• Record the recommended approach, rejected alternatives, risks, validation commands, and a migration breakdown sized into independently implementable follow-up tickets.

Blocked by

None — can start immediately.

[linear-code]

HK-250