chore: move the cargo build-dir change to its own branch

The cargo and bun halves are independent: different files, different
failure modes, and no shared dependency between them. Keeping them
together meant neither could land until both were settled, and the bun
half needs more burn-in than the cargo half does.

The cargo side now lives in its own pull request. This branch keeps only
the bun dependency store work.

Author: DaniAkash

.cargo/config.toml

@@ -75,7 +75,6 @@ on:
 permissions:
   contents: write
 
-
 concurrency:
   # The legacy key keeps in-flight revisions of the renamed workflow serialized.
   group: release-claw-server-rust

.github/workflows/release-claw-server.yml

@@ -100,11 +100,6 @@ jobs:
         uses: Swatinem/rust-cache@v2
         with:
           workspaces: packages/browseros-agent
-          # Intermediate artifacts live outside the checkout so worktrees can
-          # share them, and rust-cache only saves workspace target dirs plus the
-          # registry and git caches by default. Name the build dir explicitly or
-          # every run would recompile the dependency graph from scratch.
-          cache-directories: ~/.cargo/build/browseros
 
       - name: Install dependencies
         run: bun ci