Symptom and evidence
Native Windows x64 acceptance with Bun 1.4.0 successfully installed the generated OpenAlice package, ran the native command without host Node on PATH, and confirmed package-manager update/uninstall ownership. bun remove --global openalice then exited successfully but left the global openalice.exe entry behind.
Boundary and follow-up
The suspect subsystem is Bun's Windows global-bin cleanup, not OpenAlice version discovery or platform package selection. OpenAlice must not silently delete files owned by another package manager to hide this defect. Track this as an explicit known upstream limitation in acceptance receipts and the package-manager guide; keep asserting that the package itself was removed, and keep all npm removal assertions strict.
After an upstream fix is available, verify both Windows architectures and restore the no-residual-entry assertion for Bun. Until then, do not describe Bun removal as a completely clean Windows uninstall. Direct PowerShell installation and npm remain separate choices with their own ownership semantics.
Related integration: #1346
Symptom and evidence
Native Windows x64 acceptance with Bun 1.4.0 successfully installed the generated OpenAlice package, ran the native command without host Node on PATH, and confirmed package-manager update/uninstall ownership.
bun remove --global openalicethen exited successfully but left the globalopenalice.exeentry behind.8b84ff8a, version0.91.0-beta.4(test candidate, not a public npm release).scripts/windows-cli-package-smoke.ps1against a preserved canonical Windows candidate, using its isolatedBUN_INSTALLdirectory.bun remove -gdoes not remove binaries oven-sh/bun#11970 (also Bun remove global package does not remove all files oven-sh/bun#12232).Boundary and follow-up
The suspect subsystem is Bun's Windows global-bin cleanup, not OpenAlice version discovery or platform package selection. OpenAlice must not silently delete files owned by another package manager to hide this defect. Track this as an explicit known upstream limitation in acceptance receipts and the package-manager guide; keep asserting that the package itself was removed, and keep all npm removal assertions strict.
After an upstream fix is available, verify both Windows architectures and restore the no-residual-entry assertion for Bun. Until then, do not describe Bun removal as a completely clean Windows uninstall. Direct PowerShell installation and npm remain separate choices with their own ownership semantics.
Related integration: #1346