fix(compile): force crypto feature in auto-optimized stdlib (v0.5.871)

perry-stdlib unconditionally re-bundles perry-updater (so user code
calling `perry/updater` resolves at link time). perry-updater's
`perry_updater_verify_signature_v2` references the extern symbol
`js_crypto_ed25519_verify`, which only exists when perry-stdlib is
built with `feature = "crypto"`. The auto-optimize path passes
`--no-default-features` and only adds features inferred from user
imports, so `crypto` is off for any user binary that doesn't
explicitly import a crypto API — and the link fails on
`undefined reference to js_crypto_ed25519_verify` from the bundled
updater object.

Surfaced when v0.5.868 re-enabled the gtk4 doc-tests entry; the
gtk4 link path triggers the auto-optimize rebuild, the rebuilt
stdlib didn't include crypto, and every doc-test failed to link.

Forces `crypto` on always (mirrors how `async-runtime` is forced
when `ctx.needs_ui` for the same reason — bundled object code
that needs a symbol gated behind a feature).

Author: proggeramlug

crates/perry-codegen/src/stmt.rs

@@ -972,8 +972,7 @@ pub(crate) fn lower_stmt(ctx: &mut FnCtx<'_>, stmt: &Stmt) -> Result<()> {
             let val = lower_expr(ctx, expr)?;
             if ctx.is_async_fn && ctx.try_depth == 0 {
                 let blk = ctx.block();
-                let handle =
-                    blk.call(crate::types::I64, "js_promise_rejected", &[(DOUBLE, &val)]);
+                let handle = blk.call(crate::types::I64, "js_promise_rejected", &[(DOUBLE, &val)]);
                 let boxed = crate::expr::nanbox_pointer_inline_pub(blk, &handle);
                 blk.ret(DOUBLE, &boxed);
             } else {

crates/perry/src/commands/compile/optimized_libs.rs

@@ -342,6 +342,16 @@ pub(super) fn build_optimized_libs(
     if ctx.needs_ui {
         features.insert("async-runtime");
     }
+    // perry-stdlib unconditionally re-bundles perry-updater (so user code
+    // calling `perry/updater` resolves at link time without extra wiring).
+    // perry-updater's `perry_updater_verify_signature_v2` references the
+    // extern `js_crypto_ed25519_verify`, which lives in perry-stdlib's
+    // crypto module — gated by `#[cfg(feature = "crypto")]`. With
+    // --no-default-features the symbol is absent and the link fails on
+    // every program (regardless of whether the user touched crypto APIs).
+    // Force `crypto` on whenever the auto-optimize path rebuilds stdlib
+    // so the bundled updater always has a resolvable target.
+    features.insert("crypto");
     let feature_arg = features_to_cargo_arg(&features);
 
     // panic = "abort" is safe whenever no `catch_unwind` callers are