Whisker CLI implementation.
Subcommands
doctor— environment / toolchain health check (Rust targets, Android NDK/SDK/JDK, Xcode).run—whisker run: build → install → launch → file-watch + hot-patch loop. Thin wrapper around [whisker_dev_server::DevServer]; the cli's job is to resolve the user crate'swhisker.rs(via [manifest] + [probe]) and project the resultingConfiginto the dev-server's flat [whisker_dev_server::Config].new/new-module— scaffolding.
No build subcommand: production builds happen through the same
xcodebuild / gradle assembleRelease invocations CI uses. Past
revisions shipped a whisker build convenience wrapper, but it
existed mostly to manage the ~/.cache/whisker/lynx/ user cache,
which is itself gone now (iOS uses SPM remote binary targets,
Android pulls aars from Maven).
Internal binaries
In addition to the user-facing whisker binary, the package also
produces two shim binaries used during the initial fat build to
capture the rustc + linker invocations that Tier 1 hot-patch will
replay later:
whisker-rustc-shim(-Cstrip=…/-Csave-temps=ystyle wrapper around rustc) — captures argv to$WHISKER_RUSTC_CACHE_DIR/<crate>-<timestamp>.json.whisker-linker-shim(forwarded by rustc's-C linker=…) — captures argv to$WHISKER_LINKER_CACHE_DIR/<output>-…json.