The verified original v0.11.14 macOS ARM64 executable exits before entering Buddy when invoked from the Stacks game checkout. Bun reads that application's Bunfig preload list and fails to resolve @stacksjs/env/plugin.js from the standalone runtime.
A retained native-CLI reproduction uses the original release ZIP, checks its advertised executable, and invokes it normally from a temporary consumer with a Bunfig preload that throws if executed. --version fails in the consumer's preload under the published Bun 1.3.14 runtime. The same verifier passes when the owning binary build explicitly disables consumer Bunfig autoloading.
Source owner: Buddy standalone build and release qualification. Bun's standalone executable documentation documents the compile-time switch. Buddy's own configuration loader remains the intended project configuration interface.
Acceptance:
- Retain the original released-binary failure at the native CLI boundary, without runtime override flags or changing the caller's application.
- Configure standalone builds so consumer Bunfig preloads do not execute before Buddy's entrypoint. Preserve the existing environment/configuration policies outside that build setting.
- Add a blocking release check that executes the actual host binary's version and doctor commands from a real consumer repository containing such a preload.
- Build and verify both SDK and native artifacts before publishing. Ensure already-built platform archives cannot leak into the npm SDK tarball.
- Pass lint, types, complete tests, documentation/build checks and the native consumer verifier. Publish through the normal patch command and qualify original artifacts and actual installed consumers.
This concerns the standalone developer tool, not Craft game hosting. Source and npm API checks alone do not qualify the native executable.