Whether this app process has read its Bloks prism configuration. Until it
does, the app reports the neutral control palette: the 451 warm launch's
requests before its first screen (business/…/eligibility,
creators/…/gating, feed/reels_tray, feed/timeline) say
x-bloks-prism-colors-enabled: false and x-bloks-prism-button-version: CONTROL, and every REST request after the feed is in front says the
profile's palette (the iOS 451 launch shows the same on its first two REST
requests). Process state like MobileProcessStart: one per runtime layer,
never in the session snapshot, and a process that never ran a launch flow is
in the steady state of a running app — the palette read.
The neutral palette's other causes are not this fact: a logged-out request,
a checkpoint-gate request and a session-start job render it by their own
rules (the pre-login captures, the 429 UFAC/challenge captures and the
post-login bursts' startup jobs). A process that begins logged out is not
reset here: no recording shows whether its palette is read before or after
the login-home render (every pre-login request is logged out and renders the
control palette regardless), and once the session's request stack runs the
recording shows the profile's palette. The recording that closes it is a
logged-out process whose palette switches inside its pre-login flow.
Whether this app process has read its Bloks prism configuration. Until it does, the app reports the neutral control palette: the 451 warm launch's requests before its first screen (
business/…/eligibility,creators/…/gating,feed/reels_tray,feed/timeline) sayx-bloks-prism-colors-enabled: falseandx-bloks-prism-button-version: CONTROL, and every REST request after the feed is in front says the profile's palette (the iOS 451 launch shows the same on its first two REST requests). Process state likeMobileProcessStart: one per runtime layer, never in the session snapshot, and a process that never ran a launch flow is in the steady state of a running app — the palette read.The neutral palette's other causes are not this fact: a logged-out request, a checkpoint-gate request and a session-start job render it by their own rules (the pre-login captures, the 429 UFAC/challenge captures and the post-login bursts' startup jobs). A process that begins logged out is not reset here: no recording shows whether its palette is read before or after the login-home render (every pre-login request is logged out and renders the control palette regardless), and once the session's request stack runs the recording shows the profile's palette. The recording that closes it is a logged-out process whose palette switches inside its pre-login flow.