BMAD-METHOD/tools/installer/ide
Brian Madison bcf86f2330 fix(installer): setupBatch must not claim a shared target_dir on failure
If the first platform's setup throws or returns success: false, the dedup map
previously still recorded the claim with skillCount: 0, causing every peer
sharing the target_dir to skip its install — leaving the dir empty/broken
behind a cascade of misleading "shares with X" rows.

Now the claim is only recorded when the install succeeded and wrote skills.
On failure, the next peer becomes the new first writer and recovers.

Adds Suite 40b regression test that monkey-patches cursor.setup to throw
and verifies gemini still populates the shared dir.
2026-04-25 21:05:22 -05:00
..
shared feat(installer): add 18 new platforms, dedup shared target_dir, ownership-aware cleanup 2026-04-25 20:48:36 -05:00
_config-driven.js feat(installer): add 18 new platforms, dedup shared target_dir, ownership-aware cleanup 2026-04-25 20:48:36 -05:00
manager.js fix(installer): setupBatch must not claim a shared target_dir on failure 2026-04-25 21:05:22 -05:00
platform-codes.js fix(installer): replace fs-extra with native node:fs to prevent file loss 2026-04-13 00:44:28 -05:00
platform-codes.yaml feat(installer): add 18 new platforms, dedup shared target_dir, ownership-aware cleanup 2026-04-25 20:48:36 -05:00