OptionalprofileReadonlyentryPoint: "profile_auto_expand"ReadonlytargetUsername: stringtarget_username, sent when the profile opens.
ReadonlyentryPoint: "profile_chaining_button"The profile header's add-person ("suggested users") icon: the
profile_chaining_button rail, with no target_username/from_module
and both chaining flags off (android-451/follow-from-search,
request_entry_point=profile_chaining_button).
User id/pk the suggestions are based on.
The profile screen's suggested-users row (Android 451): sent together as
consumption_surface=profile_hscrollandmodule=profilewhen given. The row has three forms, and only the opening one carries the profile's username and the module it was reached from. That module is the screen in front's endpoint module, read from the navigation state — never a caller argument, so the body and the headers cannot name different screens.