Cargo schema on concurrent build breaks with `bus error`

```
launchpad-vesting-simple:build: Blocking waiting for file lock on build directory
launchpad:build: Finished dev [unoptimized + debuginfo] target(s) in 0.18s
launchpad:build: Running `/Users/bao/dev/tailwind.zone/target/debug/schema`
launchpad-vesting-simple:build: Finished dev [unoptimized + debuginfo] target(s) in 0.19s
launchpad-vesting-simple:build: Running `/Users/bao/dev/tailwind.zone/target/debug/schema`
launchpad:build: sh: line 1: 44078 Bus error: 10 cargo schema
launchpad-vesting-simple:build: Removing "/Users/bao/dev/tailwind.zone/contracts/launchpad-vesting-simple/schema/launchpad-vesting-simple.json" …
launchpad-vesting-simple:build: Exported the full API as /Users/bao/dev/tailwind.zone/contracts/launchpad-vesting-simple/schema/launchpad-vesting-simple.json
launchpad-vesting-simple:build: Exported /Users/bao/dev/tailwind.zone/contracts/launchpad-vesting-simple/schema/raw/instantiate.json
launchpad:build:  ELIFECYCLE  Command failed with exit code 138.
```
Turbo repo building a repo with both `launchpad` and `launchpad-vesting-simple` as dependencies.

Reproduce the concurrent Turbo build involving both `launchpad` and `launchpad-vesting-simple`, starting from the `cargo schema` commands and the generated files under `contracts/launchpad-vesting-simple/schema/`. Compare the two schema runs and determine why one exits with `Bus error: 10`; done means the concurrent build completes and both schema outputs are exported successfully.

Written by the indexing model from the issue text.