Run tests from source, persist the ttsc cache in CI, and export only the root entry

[samchon]

Follow-up review of #102. Everything here came out of a "review until dry" pass over that PR's toolchain changes, with the goal that nothing depends on cwd, execution mode, or duplicated configuration.

Tests run from source only

ttsx injects its loader into NODE_OPTIONS, so child_process.fork() and worker_threads.Worker children execute .ts files directly (verified for both). That removes the need for:

• test/node/runtime.ts, which rewrote test/**/*.ts to bin/test/**/*.js based on process.cwd();
• the __filename.endsWith(".ts") / process.cwd() branches in TestBundler and test_worker_compiler;
• the .ts/.js extension switch in test/node/index.ts.

test:browser now runs through ttsx --project test/tsconfig.json too, so both suites share one execution mode and every path is __dirname-relative. build:test remains because browserify consumes the emitted JavaScript.

Also fixed while there: the test runner built paths with "/" on Windows, so location === __filename never matched; it now uses path.join. A leftover debug console.log in the runner is gone, as is the unused source-map-support dependency.

ttsc cache in CI

Per the ttsc build-cache docs: actions/cache after pnpm install, path plugins/ only (28 MB; the 1.6 GB go-build accelerator is skipped), key os-arch-ttsc-<lockfile hash> with restore-keys, then ttsc prepare before the build.

TTSC_CACHE_DIR is pinned to one workspace path. This works around samchon/ttsc#1469: ttsx creates test/node_modules/.cache/ttsc/ttsx under the nested tsconfig, which makes the plugin cache resolve to test/node_modules/... and rebuilds the Go plugin cold a second time. With the env var set, ttsc prepare → ttsx was verified locally to reuse the warmed binary (no building linked plugin host line). Once the upstream fix lands the env line can be removed.

CI hygiene in the same files: the pnpm version duplicated from packageManager is dropped, action majors are aligned (checkout@v7, setup-node@v7, pnpm/action-setup@v6, cache@v5), and build.yml now also triggers on tsconfig*.json, rollup.config.js, and itself.

Exports

./node and ./browser subpaths and the typesVersions block are removed. The API is identical across platforms and the browser / react-native / node conditions on "." already select the right build; the subpaths only widened the surface. They have not been published (npm still has 1.2.1 with the old exports). Resolution verified for node/browser × CJS/ESM.

Validation

• pnpm build, pnpm run test:node (18 tests), pnpm run test:browser (3 pages) locally on Windows
• TTSC_CACHE_DIR warm/reuse cycle verified locally from an empty directory

🤖 Generated with Claude Code

https://claude.ai/code/session_01PYz2NPPRFDMR6CMoCeArb9