Skip wasm bodies on serialized module hits

docs/wasm-runtime-architecture.md

@@ -141,6 +141,10 @@ changing core-first, unit-load-order symbol resolution.
 into artifact lookup, wasm read, custom-section parse, serialized-module
 deserialization or wasm compilation, and immutable import classification. This
 keeps cold-worker module latency distinguishable without exposing source paths.
+When a current serialized module exists, the worker scans wasm section headers
+and reads only `dylink.0` and `uce.abi`; it does not fault the multi-megabyte code
+and data bodies into every new worker. A missing/stale/invalid serialized module
+still reads, validates, compiles, and republishes the complete wasm artifact.
 Cold module compilation and deserialization are host work, so `load_unit()`
 refreshes the epoch deadline before its first guest call. Otherwise a component
 whose compilation outlasted the guest CPU budget would immediately trap in the