Phase 2: core/runtime/storage dependency upgrades outside ui/

[justinrayshort]

Summary

Implement phase 2 of the repository-wide Rust modernization: upgrade non-UI dependencies to current stable releases, with focused work in SurrealDB, Wasmtime, wasmCloud/WIT tooling, and supporting shared/runtime crates.

Primary Architectural Plane

cross-layer

Owning Subsystem

shared storage/runtime crates, platform runtime/tooling, and service/workflow non-UI dependencies

Architectural References

• AGENTS.md
• ARCHITECTURE.md
• docs/architecture/layer-boundaries.md
• platform/README.md
• services/README.md
• schemas/AGENTS.md

Integration Boundaries

Allowed cross-plane touchpoints:

• Cargo.toml
• Cargo.lock
• shared/
• platform/
• services/
• workflows/
• xtask/
• plans/
• docs/ if migration notes are needed
• schemas/ only for additive compatibility changes forced by upstream breaks

Explicit non-goals:

• Do not upgrade the Leptos/browser/Tauri stack in this phase.
• Do not introduce breaking schema/event redesign.
• Do not bypass shared/surrealdb-access.

Scope In

• Upgrade SurrealDB consumers under shared/surrealdb-access and services/knowledge-service.
• Upgrade Wasmtime consumers under platform/runtime/strategy-sandbox.
• Upgrade wasmCloud/WIT helper dependencies such as wit-parser where needed.
• Upgrade remaining non-UI direct dependencies to current stable heads while keeping contracts stable.

Scope Out

• UI framework modernization.
• Edition 2024 uplift.

Background and Scope

The current largest non-UI gaps are SurrealDB 2.6 -> 3.0 and Wasmtime 36 -> 42. These upgrades can introduce API breakage and runtime behavior changes, so they should be isolated from UI work.

Acceptance Criteria

• cargo test --workspace --all-targets passes after non-UI dependency upgrades.
• cargo verify-repo passes.
• Focused regressions for shared/surrealdb-access, services/knowledge-service, platform/runtime/strategy-sandbox, and platform/wasmcloud/bindings pass.
• No architectural boundary violations are introduced.

Validation Requirements

• cargo test --workspace --all-targets
• cargo verify-repo
• cargo test -p surrealdb-access --all-targets
• cargo test -p knowledge-service --all-targets
• cargo test -p strategy-sandbox --all-targets
• cargo test -p wasmcloud-bindings --all-targets

Rollback Considerations

Rollback must revert the upgraded runtime/storage crates as one bounded set to avoid mixed dependency expectations.