filesMove skips Linux VST3 bundles without Info.plist

[ktinubu]

Reproduction

1. Use ManagerLocal.install() for a Linux archive containing Dexed.vst3/Contents/x86_64-linux/Dexed.so but no Contents/Info.plist (the current asb2m10/dexed@1.0.1 registry artifact has this shape).
2. Observe filesMove() in src/helpers/file.ts.

Actual behavior

The .vst3 directory is not added to bundleDirs because bundle detection requires Contents/Info.plist. Its nested shared library is considered independently and the VST3 bundle is never installed under <pluginsDir>/VST3/.... The CLI can still report the package as installed because other formats or metadata were moved.

Expected behavior

A directory whose extension maps to a bundle format (at minimum .vst3) should be moved atomically even when its platform bundle does not carry a macOS plist. Descendants should remain excluded from individual-file handling.

Environment

• @open-audio-stack/core@0.1.55
• @studiorack/cli@3.0.6
• Linux x86_64

A possible fix is to recognize mapped bundle-directory extensions in the first pass in addition to the existing plist and LV2-manifest checks.

[kmturley]

Investigated this against the current codebase — the bug is real and was still present after the issue was closed (no PR had actually addressed it).

Root cause confirmed: in filesMove() (src/helpers/file.ts), the first-pass bundle-directory detection only checked for a macOS Contents/Info.plist or an LV2 manifest.ttl. A Linux (or some Windows) VST3 bundle directory — e.g. Dexed.vst3/Contents/x86_64-linux/Dexed.so — has neither, so the .vst3 directory was never added to bundleDirs. The bundle directory itself was then skipped entirely by the filter (directories not in bundleDirs are ignored), while its nested .so file was picked up independently by the per-extension pass and moved to the generic VST folder — losing the Contents/<arch> structure and never installing anything under VST3/..., exactly as described.

Reproduced this directly with a test fixture matching the issue's shape before applying any fix.

Fix opened: #88

• Recognizes directories with a .vst3 extension as bundles directly, alongside the existing plist/manifest checks, so the whole bundle moves atomically regardless of platform
• Adds a regression test that reproduces the exact Linux VST3 layout from this issue and asserts the bundle lands intact under VST3/<slug>/<version>/... (previously zero test coverage existed for filesMove)
• Verified the new test fails on main and passes with the fix; full npm run check suite passes (172 tests)

🤖 Generated with Claude Code