ReadonlyinputReadonlynavigateReadonlysendSends answer's request now and goes on without waiting for it: the
request stays in flight, and its answer is held for the screen this one
pushes next, which takes it with takeAcrossPush instead of sending the
request itself (answerAcrossPush). Call it at the point of the burst
where the app sends the request.
ReadonlytakeThe answer the screen below — the one whose edge pushed this screen — left
in flight for answer with sendAcrossPush, awaited if it is still in
flight; when it left none, answer's request sent here
(answerAcrossPush).
ReadonlyvisitThe visit this enter begins, without its chain: the burst itself moves the chain.
What a screen's
enterreceives: the edge's input,navigate, the screen's own navigation event —NavigateTofor a screen,SwitchTabfor a tab,SwitchTopTabfor an inner tab — with the source and ordinal skip of the edge that led here, and the visit it begins. The screen yieldsnavigateexactly once, at the point of its burst where the app writes it (in 451 the firstUserProfilerequests still carry the SERP); a second yield dies withScreenEnterNavigationError, and so does an enter that never yields it: the burst is the library's own definition, so a wrong count is a defect of the declaration, never a typed failure. The screen itself never sees the source.