davidherranandClaude Opus 4.7 274ddf3957 docs(slice-2d): findings consolidados — serde/std leak via types/std identified ...

Slice 2d empirical investigation completada (sesión 2 cont 2026-05-24):
- WASM_BUILD_STD=0 resuelve alloc/exchange_malloc (Slice 2c attempt #5)
- NEW layer: panic_impl duplicate via serde/std leak transitive
- Diagnostic vía cargo tree wasm32 -e features: ruta exacta identificada
  `origin-chain-types feature "std"` → `serde feature "std"` activation
- Root cause: dep transitive activa types/std en wasm32 build incluso
  con --no-default-features (probable macro expansion automation)

Slice 2e future requires architectural fix:
- [patch.crates-io] serde override con strict no-std
- O sp-io feature gate adjust
- O wait stable2512-4+ upstream

Mientras Slice 2e land: build.rs no-op + Slice 3 v0.0.13 mock-WASM estable.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-24 13:14:36 -05:00

..

src

feat(node): Phase 1.6+ Slice 3 — ChainSpec builder canonical mock-WASM fallback v0.0.13

2026-05-22 07:54:57 -05:00

build.rs

docs(slice-2d): findings consolidados — serde/std leak via types/std identified

2026-05-24 13:14:36 -05:00

Cargo.toml

docs(slice-2d): findings consolidados — serde/std leak via types/std identified

2026-05-24 13:14:36 -05:00