Local workspace linking exposes broken package boundaries and webpack resolution assumptions across mashlib / solid-panes / solid-ui

[bourgeoa]

Linking solid-panes and solid-ui into mashlib

• webpack cannot resolve solid-ui and UI consistently from sibling workspace packages
• stale built artifacts and source/package export mismatch
• TypeScript config assumptions break when packages are linked but not fully installed/built
• current alias/declaration fixes are local workarounds, not the ideal package-boundary solution