vhaudiquet
09019b484d
The published rhema-sandbox-http gates its reqwest code on the wasm target alone, so a featureless build compiles only on wasm — and the DO declares the crate featureless, because workerd has no sockets. On the host, where the neutral half compiles and tests, the feature is not optional: without it the crate cannot resolve `reqwest` and the workspace does not build. This workspace only ever saw the feature on, masked by member unification under --all-features; the extraction to registry deps removed the mask. The declaration splits by target: featureless on wasm (the fetch transport covers the protocol there), native on host. The crate's own cfg keeps the reqwest code native-only either way; the feature brings the dependency. The upstream gate repair — gating the code on the feature, not just the target — rides the rhema side.