scripts/build/react/

script	emits	why it exists
build-demos.ts	frameworks/react/**/*.generated.js, one per .tsx	JSX is compiled ahead of time, not in the browser, so a demo page loads a real ES module with no transform step. It also rewrites each relative ./X.tsx import to ./X.generated.js, which is what makes the compiled tree self-consistent.
build-vendor.ts	frameworks/react/vendor/*.generated.js	React 18 ships CommonJS only, and an importmap needs real ES modules. Bundles the three entry points, appends the named exports Bun's static detection misses, and keeps react external so it stays a singleton across the three files.
build-react-barrel.ts	frameworks/react/Index.generated.ts	The layer's entry point: one export * per component directory, plus the four layer-root helpers. Derived from the tree rather than hand-listed, because a hand-listed barrel is how the Angular layer shipped five primitives nobody could import. Tokens.generated is deliberately absent, for the reason its Angular counterpart is.
build-react-package.ts	frameworks/react/dist/	Assembles @dravensoft/arena-react. The .tsx goes through Bun.Transpiler, the same path build-demos.ts uses, and each declaration is emitted by tsc rather than copied, so it cannot disagree with the implementation. One rewrite, applied to the emitted declarations too: every relative specifier becomes .js, whether it carried another extension or none at all. rewriteRelativeImportExtensions does not reach declaration output, so an unrewritten one names a file the package lacks, and an extensionless one names nothing a consumer on node16 can resolve. unresolvedProblems then resolves every specifier against what was emitted, so neither half is a claim the build takes on trust.

Every output here is git-ignored. The first two are read only by the demo pages, and check:demos and check:vendor compare them against a fresh compile. The barrel is what a package consumer imports, and the package build compiles it and emits its declaration, so the only reader outside this repository is a tarball; check:react-barrel holds it to a fresh run.

Editing a component .tsx means running bun run build:demos in the same tree. The React DOM suites import the .tsx directly, so every test stays green with the .generated.js sibling stale, and the demo pages load the sibling, so bun run demos would show the pre-fix component while the suites prove the fix.

Every X.test.ts beside a script covers that script.