More observable Wasm

[expede]

Don't strip symbols & improve a few expect messages

[Copilot]

Pull request overview

This PR aims to improve production observability for the Wasm builds by preserving symbol names (for readable stack traces) and making JS boundary failures easier to diagnose via safer casts and clearer expect messages.

Changes:

• Preserve Wasm function names in release builds by adjusting per-package strip settings for Wasm crates.
• Improve runtime diagnostics by replacing unchecked_into with fallible dyn_into at several JS/Wasm boundaries and upgrading expect messages.
• Move console_error_panic_hook installation to module instantiation via a wasm-bindgen start function and enable the feature by default for subduction_wasm.

Reviewed changes

Copilot reviewed 8 out of 9 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
subduction_wasm/src/subduction.rs	Switch hash metric override casting from unchecked to fallible with clearer panic text.
subduction_wasm/src/signer/webcrypto.rs	Improve expect messages around IDB upgrade flow and key parsing; clarify WebCrypto sign failure text.
subduction_wasm/src/signer.rs	Make JS signer return-type handling fail loudly with explicit dyn_into diagnostics.
subduction_wasm/src/lib.rs	Add #[wasm_bindgen(start)] to install the panic hook at module instantiation time.
subduction_wasm/src/connection.rs	Replace unchecked JS casts with dyn_into and add an error variant for unexpected JS types.
subduction_wasm/Cargo.toml	Enable console_error_panic_hook by default.
sedimentree_wasm/src/storage.rs	Make digest parsing fallible and convert several unchecked casts into typed errors.
Cargo.toml	Override release profile stripping for Wasm crates to keep names while stripping DWARF debuginfo.
flake.lock	Update pinned Nix inputs.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.