Chris Tate
26df3687f4
* Make the Windows embedded WebView layer real - Vendor the WebView2 SDK header and loader under third_party/webview2 (BSD-3-Clause, license preserved) so repo state alone compiles the embedded layer; a missing header is now a hard error instead of a silent stub - Fix the conformance blockers behind the guard: a local WRL callback factory for mingw, the uncaptured bridge-handler variable, an EventToken shim, and STA COM initialization on the host thread - Stage the arch-matched loader beside built, run, packaged, and scaffolded apps, mirror it into the npm payload, and pin the wiring with vendor and loader-layout tests * Carry the SDK root through package shortcuts and generated builds - packageShortcut and package-ios now pass the environ map into createPackage like the package verb, so NATIVE_SDK_PATH resolves the framework root for loader staging from standalone binaries - Generated frontend builds export NATIVE_SDK_PATH on the package command and stage the loader dir on the dev command's PATH, mirroring the SDK-dependency graph
Native SDK command-app example
This example shows one app.sync command handled from each user-facing entry point:
- Native toolbar button.
- Native menu item.
- Native tray item.
- App shortcut.
- WebView bridge call.
- Manifest command catalog listing from the WebView.
Run with the system backend:
zig build run -Dplatform=macos -Dweb-engine=system
Run the headless test path:
zig build test -Dplatform=null