Declare shared Harness dependencies for WASM builds

Merged
VA
3d ago
+2-2

Harness's shared tool-outcome handler calls tracing::error! on browser builds, and two portable property-test modules import proptest. Both dependencies were declared only for native targets, so the browser library and then its tests failed with E0433.

Move tracing to shared dependencies and proptest to shared dev-dependencies. Keep their existing workspace versions/features; Cargo.lock is unchanged. Required work is the same dependency availability on every target compiling those modules; no runtime algorithm changes.

Validation: Windows MSVC lb.ps1 cargo check --locked -p acyclic-harness --features filesystem --lib --tests passed. bb1 browser test compilation passed with cargo test --locked -p acyclic-harness --features browser --target wasm32-unknown-unknown --lib --no-run. The browser test artifact linked successfully (3m38s build, no runtime suite invoked). These are the existing native/browser feature closures; no tests or checks are removed.

Decisions: fix the dependency gates in one manifest instead of excluding the shared handler or property tests from WASM.

Summary by cubic

Declares tracing and proptest as shared dependencies in the acyclic-harness manifest so browser (WASM) builds and tests compile instead of failing with E0433.

  • Moves tracing from native-only dependencies to shared dependencies and proptest from native-only dev-dependencies to shared dev-dependencies.
  • Keeps existing workspace versions and features; Cargo.lock is unchanged and there are no runtime behavior changes.
  • Validated with native MSVC cargo check and a wasm32-unknown-unknown browser test build; no tests or checks are removed.