diff --git a/jenkins/L0_MergeRequest.groovy b/jenkins/L0_MergeRequest.groovy
index 1ef2aac37c97..f304703e05dc 100644
--- a/jenkins/L0_MergeRequest.groovy
+++ b/jenkins/L0_MergeRequest.groovy
@@ -187,8 +187,15 @@ def BOLT_CONSUME = "bolt_consume"
 // on for every eligible build is a reviewed code change; a `/bot run` with
 // `"bolt_consume": true` opts in a single run without one. Either way
 // resolveBoltConsume() still applies the post-merge and branch restrictions.
+//
+// On today means aarch64/SBSA only in practice: the post-merge producer promotes
+// `targetArch: aarch64-linux-gnu` alone (see the BOLT-Profile-Gen stage below), so
+// main has no x86_64 bundle. The x86_64 build still asks and takes apply_latest.sh's
+// documented "nothing promoted" exit (3), which Build.groovy reports as a skip and
+// leaves un-BOLTed. It starts consuming on its own once an x86_64 bundle is promoted,
+// with no change here.
 @Field
-def ENABLE_BOLT_PREMERGE_CONSUME = false
+def ENABLE_BOLT_PREMERGE_CONSUME = true
 
 def testFilter = [
     (REUSE_TEST): gitlabParamsFromBot.get(REUSE_TEST, null),