zero-native Files

New Features

• Compiler-truth checks for TypeScript cores: native check now ends with the pinned external core compiler's analyzer over the entry with the shipped SDK declarations mapped, so check and build share one compiler verdict. Type errors the frontend's own line would miss fail with the compiler's diagnostics verbatim; an analyzer that cannot reach a verdict defers to the build instead of wedging check.
• TypeScript cores compile through the external core compiler: the frontend checks src/core.ts and emits its contract sidecar, the exact-pinned compiler builds a native archive, and the app links a generated mirror over it — no JS runtime in the binary, nothing to configure.
• The TS-to-Zig transpiled lane is removed (a deliberate pre-1.0 break): core_compiler = "transpiler" in app.zon (and -Dcore-compiler=transpiler) is refused with a teaching, and native check runs the checker and contract only — no emitted Zig lands under .native/check/.
• The compiler is a package dependency: it ships exact-pinned with the SDK's packages/core (repo checkouts install it with npm ci there; an npm-installed CLI carries it automatically).
• The core dev loop is restart-shaped: markup hot reload and the instant native dev --core node loop are unchanged, and a core edit now pays a native compile measured in seconds on rebuild.
• TypeScript cores are desktop-only for now: a mobile target with src/core.ts is taught before lane selection (the external toolchain does not target mobile yet); Zig and markup cores stay fully supported on mobile.
• Shipped type declarations: @native-sdk/core now ships generated sdk/*.d.ts declaration files beside its TypeScript sources, so external tooling can resolve the SDK's types without compiling them.

Improvements

• Leaner TypeScript toolchain installs: the unused @typescript/typescript6 compatibility wrapper is no longer a dependency of @native-sdk/cli or @native-sdk/core. The frontend already imports its compiler directly through the exactly pinned @typescript/old alias, while consumer trees carrying their own wrapper remain unaffected.

Contributors

• @ctate