ReadonlyissuedReadonlyaac: stringAccount-access-context token the client-data redirect issued.
Optional ReadonlyattestationChallengeNonce?: stringKeystore attestation nonce of the cold start, echoed as x-ig-attest-params.
ReadonlyloginEntryPoint: "login-home" | "landing-screen"Which screen the app entered the login from (the landing screen or the native login home).
ReadonlyoauthQpl: { instanceId: number; markerId: number }QPL marker/instance the login step's oauth.token.fetch action carries.
ReadonlypasswordTextInputId: stringReadonlyqpl: { instanceId: number; markerId: number }QPL marker/instance the issued send_login_request action carries.
Optional ReadonlyrecoveryTicket?: string & Brand<"RecoveryActionTicket">The login home's issued "Forgot password" action, as an opaque ticket.
ReadonlyusernameTextInputId: stringThe login form's text input ids the issued action carries.
ReadonlywaterfallId: stringThe waterfall id the cold start generated; the login and recovery steps chain it.
The process slot the logged-out launch fills and the login home reads: the burst belongs to the launch (it is the process bootstrap, sent before the screen), so the screen's
entersends nothing and shows what the launch issued. One value per runtime layer, like the stack; never in the snapshot. The issued state is read-only outside this module and is cleared when a login succeeds, so a second login in the same process takes the login home's fresh state, never the previous contact's aac, waterfall or QPL ids.