feat(types): Phase 1.6+ Slice 2 — origin-chain-types fully no_std v0.0.11

origin-chain-types ahora fully no_std-compatible canonical — preparado para
WASM runtime build canonical Slice 2b.

## Refactor sistemático canonical
- src/lib.rs: #![cfg_attr(not(feature = "std"), no_std)] + extern crate alloc
- src/errors.rs: String → alloc::string::String
- src/provenance.rs: Vec<AccountId> → alloc::vec::Vec<AccountId>
- src/pallets.rs: Vec<AssetAttestation> → alloc::vec::Vec<AssetAttestation>
- Cargo.toml: [features] default=["std"] + std=["thiserror/std", "serde/std"]

## Workspace deps bump canonical (no_std-compatible)
- thiserror 1.0 → 2.0 default-features=false (no_std support nativo)
- serde 1.0 → =1.0.219 default-features=false (pin canonical para evitar
  serde_core breaking change canonical post-1.0.220)
- log 0.4 → default-features=false
- serde-big-array default-features=false

## Decisión empírica DEFERRED: WASM_BINARY a Slice 2b dedicated
substrate-wasm-builder retry encountered serde 1.0.x alloc/serde_core feature
conflict durante isolated WASM build (duplicate exchange_malloc lang item entre
rustup stdlib alloc + wbuild dir alloc). Investigation requires deep Rust
toolchain debugging — Slice 2b dedicated session merece DC propio.

Investigation canonical scope para Slice 2b:
1. substrate-wasm-builder 25.x o 27.x version regression test
2. cargo workspace.metadata.wasm-builder section config
3. RUSTFLAGS -Z build-std=core,alloc nightly approach
4. Fallback: pre-built WASM binary loaded from file
5. Possible upstream issue paritytech/polkadot-sdk

## Filosofía canonical
origin-chain-types era barrera canonical para hermanos consumers WASM runtimes.
Esa barrera canonical ya NO existe post-refactor. Forward compatibility canonical
preservada para Trinity 3D + Codex Vault + Ethos credential minting + AGI
co-authoring canonical futuras integrations.

David canon 2026-05-14 "la libertad infinita acota solo donde empieza la del
otro" — la liberación arquitectónica del no_std sucede ahora.

## Build
- cargo check workspace 17.06s warm
- cargo build --release 1m 38s cold rebuild (serde version regress full
  recompile triggered)
- origin-chain-node binary canonical ejecuta 4 subcommands
- Full workspace test OOM (signal 137) — per-crate testing deferred

## Phase 1.6+ progress
- Slice 1 ✅ (v0.0.10 CLI skeleton)
- Slice 2 ✅ (v0.0.11 ESTA no_std refactor)
- Slice 2b ⏳ WASM_BINARY dedicated debug
- Slice 3 ⏳ sc_service::ChainSpec
- Slice 4 ⏳ Full sc-service (consensus + RPC + networking)

Refs: CHARON_ROADMAP_V1 Phase 1.6+ Slice 2, no_std refactor canonical
preparation para WASM runtime build canonical Slice 2b

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

crates/origin-chain-runtime/src/lib.rs

@@ -50,17 +50,23 @@ pub mod genesis_config_presets;
 pub mod opaque;
 
 // ============================================================
-// WASM binary canonical — DEFERRED a v0.0.11+ (canonical decision empírica)
+// WASM binary canonical (Slice 2 v0.0.11 — DEFERRED Slice 2b)
 // ============================================================
 //
-// `WASM_BINARY` via `substrate-wasm-builder` requiere que TODAS las dependencias
-// transitivas del runtime sean no_std-compatible canonical. Actualmente
-// `origin-chain-types` no es fully no_std canonical (uses std `String` + `Vec`
-// directly sin `alloc::` prefix). Refactor canonical es Phase 1.6+ Slice 2
-// (substantial scope canonical: 5-10+ files affected canonical).
+// `substrate-wasm-builder` canonical encounters `serde 1.0.x` alloc/serde_core
+// feature conflict canonical durante isolated WASM build (`liballoc.rmeta`
+// duplicate lang item `exchange_malloc` canonical entre rustup stdlib +
+// wbuild dir).
 //
-// Mientras canonical: el `chain_spec.rs` node-side puede usar mock-WASM o
-// pre-built WASM file canonical (path-loaded en runtime canonical).
+// Investigation canonical requires deep Rust toolchain debugging canonical
+// — Slice 2b dedicated:
+// 1. Try substrate-wasm-builder 25.x or 27.x (version regression)
+// 2. Try serde 1.0.219 pinned + workspace.resolver = "2" explicit
+// 3. Try cargo workspace.metadata.wasm-builder section canonical
+// 4. Fallback canonical: prebuilt WASM binary loaded from file canonical
+//
+// Mientras canonical: `chain_spec.rs` Phase 1.6+ Slice 3 puede usar mock-WASM
+// canonical o pre-built WASM file canonical para development chain specs canonical.
 
 // Re-export canonical traits + types desde origin-chain-types (single-crate surface).
 pub use origin_chain_types::{