subsecond::call/try_call are cfg!(debug_assertions)-gated no-ops (subsecond/src/lib.rs:250-254, :411-414). cfg!() resolves against THIS crate's own compilation flags, not a downstream consumer's - unlike cargo, where one profile's debug-assertions setting covers the whole dependency graph uniformly, each reindeer-generated third-party BUCK target is its own independent rustc invocation. Measured 2026-09-20: without this, apps/hotdemo's own -Cdebug-assertions=yes had zero effect on subsecond's internal gate (nm showed no call to subsecond's get_jump_table anywhere in the patched binary - the redirect was a complete no-op, apply_patch "succeeded" but nothing ever jumped).

11rustc_flags = ["-Cdebug-assertions=yes"]