fix(ci): pin wasm32-wasip1 in rust-toolchain.toml so the pinned toolchain has its std

The verify smoke still failed with E0463 after adding the target to the dtolnay
@stable step: rust-toolchain.toml pins channel 1.89.0, so every cargo invocation
uses 1.89.0 — not stable — and the wasm target had been added to the wrong
toolchain. Declare `targets = ["wasm32-wasip1"]` in rust-toolchain.toml so rustup
auto-installs the wasm std for the pinned toolchain everywhere (CI and local), and
drop the now-redundant `targets:` from the workflow step. Verified locally: the
home-cli wasm build compiles clean.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: SashaMIT

.github/workflows/ci.yml

@@ -80,9 +80,8 @@ jobs:
       - uses: dtolnay/rust-toolchain@stable
         with:
           components: clippy, rustfmt
-          # The carrier smoke builds the Home capsules (home-cli etc.) to wasm32-wasip1,
-          # so that target's std must be installed or the build fails with E0463.
-          targets: wasm32-wasip1
+          # The carrier smoke builds the Home capsules to wasm32-wasip1; that target is
+          # declared in rust-toolchain.toml so the pinned toolchain installs its std.
       - uses: Swatinem/rust-cache@v2
         with:
           workspaces: |

rust-toolchain.toml

@@ -1,3 +1,7 @@
 [toolchain]
 channel = "1.89.0"
 components = ["rustfmt", "clippy"]
+# The Home capsules (capsules/home-cli and friends) build to wasm; pin the target so the
+# pinned toolchain auto-installs its std (carrier smoke + `just verify`) everywhere — CI and
+# local — instead of failing with E0463 "can't find crate for std".
+targets = ["wasm32-wasip1"]