The application a restored snapshot runs on: what the snapshot carries is
what goes out. A stored application of any app build keeps every literal it
holds — the version, the build code, the user agent's parts, the capability
list, the zero-rating table, the Bloks theme and its INTERNAL_INFRA_THEME
spelling, the bk_client_context shape, the UFI action list — whatever build
wrote it. Owner, 2026-10-31, verbatim: «Что лежит в снапшоте, то и уходит.
Сессия, сохранённая на 222, шлёт User-Agent 222, номер сборки 222 и прочие
данные приложения из снапшота». The snapshot outranks the code: owner,
2026-10-31, verbatim: «снэпшот приоритетнее чем код. снэпшот - декларация, а
не подсказка». This is the rule «Код просто отрабатывает, подставляя тот
юзера-агента и те данные девайса и приложения, которые есть. Юзер-агент,
который код не знает – это проблема того, кто передает этот юзера агент»:
the code builds its current request shapes with the application the snapshot
carries; whose user agent it is, is the caller's decision.
A version-bound field the snapshot omits is filled from defaultApplication,
because the request cannot be built without it (the GraphQL doc-id table,
GRAPHQL_OMIT_PRETTY, the Direct inbox mode, the feed/timeline wire, the
media like, repost and note wires, the reels-tray page size, the launch's
shopping experiments and AI-bot count, the routing-map sample the build
writes, the adaptive-UI flag, the Bloks prism palette, the Bloks theme
bloksThemeParams, its INTERNAL_INFRA_THEME spelling, the
bk_client_context shape bloksClientContext and the USDID registration's
name usdidRegistrationName). Nothing is replaced, dropped or refused: a
field the snapshot carries is never overwritten, and a value the default
lacks is kept as stored.
A new process (no snapshot) has no application to keep: it runs
defaultApplication whole.
The application a restored snapshot runs on: what the snapshot carries is what goes out. A stored application of any app build keeps every literal it holds — the version, the build code, the user agent's parts, the capability list, the zero-rating table, the Bloks theme and its
INTERNAL_INFRA_THEMEspelling, thebk_client_contextshape, the UFI action list — whatever build wrote it. Owner, 2026-10-31, verbatim: «Что лежит в снапшоте, то и уходит. Сессия, сохранённая на 222, шлёт User-Agent 222, номер сборки 222 и прочие данные приложения из снапшота». The snapshot outranks the code: owner, 2026-10-31, verbatim: «снэпшот приоритетнее чем код. снэпшот - декларация, а не подсказка». This is the rule «Код просто отрабатывает, подставляя тот юзера-агента и те данные девайса и приложения, которые есть. Юзер-агент, который код не знает – это проблема того, кто передает этот юзера агент»: the code builds its current request shapes with the application the snapshot carries; whose user agent it is, is the caller's decision.A version-bound field the snapshot omits is filled from
defaultApplication, because the request cannot be built without it (the GraphQL doc-id table,GRAPHQL_OMIT_PRETTY, the Direct inboxmode, thefeed/timelinewire, the media like, repost and note wires, the reels-tray page size, the launch's shopping experiments and AI-bot count, the routing-map sample the build writes, the adaptive-UI flag, the Bloks prism palette, the Bloks themebloksThemeParams, itsINTERNAL_INFRA_THEMEspelling, thebk_client_contextshapebloksClientContextand the USDID registration's nameusdidRegistrationName). Nothing is replaced, dropped or refused: a field the snapshot carries is never overwritten, and a value the default lacks is kept as stored.A new process (no snapshot) has no application to keep: it runs
defaultApplicationwhole.