react-tsx-template

The build sandbox the AIA TSX sidecar (AIA.Agents.SemanticKernel → TsxBuildSidecar) type-checks agent-authored TSX against, and the workspace the dashboard composer copies per session (tsc → vitest → scripts/bundle.js).

Its type surface is @aintela/bi (^0.2.0; in this repo, run npm install ../packages/bi --install-links after building the package to work against the sibling source). That is the whole point of this folder living next to the package: the legacy setup mirrored ~40 files from three repos into a hand-maintained packages/ui-library with a sync script; here there is nothing to sync.

• Published as @aintela/bi-tsx-template (a host image does npm pack @aintela/bi-tsx-template@<v> and npm install --install-links). Locally: npm run build in ../packages/bi, then npm install ../packages/bi --install-links here to test against the sibling.
• .npmrc sets install-links=true: the dependency is installed as a copy, not a symlink. A symlink makes every hook in the package resolve React/MUI/emotion from packages/bi/node_modules and throw Cannot read properties of null (reading 'useState') — and a copy is what a published package is anyway.
• Legacy specifier: @envision/ui-library still resolves (a tsconfig path + a vitest alias) so bundles and tests written before the rename keep type-checking. New code imports from @aintela/bi; instructions.md says so.
• npx tsc --noEmit and npx vitest run must stay green; scripts/bundle.js (ESM) externalises both specifiers.