How this app process began: with a stored user session, or logged out with a
login inside the process. Process state like the navigation, one per runtime
layer, never in the session snapshot — a restored session starts a new
process that begins with the session it restored.
Android evidence, the fact the header layer renders: only a process that
started with a session reports x-ig-nav-chain on its session GraphQL
requests. The Android 451 warm launches of 2026-10-21 and the 450 client
scenes carry the chain on every session GraphQL call once it exists, whether
the process's first GraphQL ran before the first screen or not; the 448
post-login capture (its login runs inside the process) and the Android 451
post-login capture (its process begins at the account-recovery code-entry
screen and logs in by code) carry it on no GraphQL request at all, although
their REST requests report the same live chain. The fact is set at process
start and never cleared by a login.
How this app process began: with a stored user session, or logged out with a login inside the process. Process state like the navigation, one per runtime layer, never in the session snapshot — a restored session starts a new process that begins with the session it restored.
Android evidence, the fact the header layer renders: only a process that started with a session reports
x-ig-nav-chainon its session GraphQL requests. The Android 451 warm launches of 2026-10-21 and the 450 client scenes carry the chain on every session GraphQL call once it exists, whether the process's first GraphQL ran before the first screen or not; the 448post-logincapture (its login runs inside the process) and the Android 451post-logincapture (its process begins at the account-recovery code-entry screen and logs in by code) carry it on no GraphQL request at all, although their REST requests report the same live chain. The fact is set at process start and never cleared by a login.