The composer session ids whose composer this process has focused: the sheet logs the composer's tap and focus once per sheet, and a second comment in the same sheet sends again without re-opening the composer.
Whether the user session that showed this process's sheet has read the viewer's restricted accounts.
The media pks this process has asked the shop eligibility of.
What this app process has already asked the comments sheet's open for: the viewer's restricted accounts (read once in the user session that read them) and the media pks whose shop eligibility it has asked about (asked once per media, for the process).
The restricted accounts are the viewer's, and the app caches the list on the
UserSession; the layer registers its reset withonUserSessionEnd(android.layer.ts), so a login that adopts an account reads the next account's list again. The shop eligibility is a property of the media: the corpus records two processes of one account (android-451/media-like-repost-commentandandroid-451/reels-commentshareig-intended-user-id), each of its own start, and each sendsrestrict_action/get_restricted_users/on its first sheet open. A snapshot restored into a later process must therefore not carry them, or the later process would skip reads the app makes; a process restored from a checkpoint continues this one, so the checkpoint carries them.The shop list is a set of media pks, not an ever-growing snapshot array: a session that comments on thousands of posts keeps thousands of entries in the process it lives in, and a restore carries only what the process read. A new session's sheet writes the restricted read afresh; the shop checks stay.
One
MediaCommentsScreenenter writes both, beside the sheet'senter(media.comments.ts); the sheet'scomment()writes the composer sessions it has opened.