Requests are listed in the fresh 448 capture's issue order (seq 23–212) for
deterministic sequencing when concurrency is set to 1. The app issues them
concurrently, so the order only pins where state switches land relative to
other requests (zero phase on the campaign fetch, routing-map activation,
token rotations).
Production callers may keep the default bounded concurrency because the real
app also overlaps this bootstrap work. Navigation events (NavigateTo,
NavigateBack) are list items too: their position is the point where the app
changes screen, kept next to the request that anchors them.
Simulates the post-login flow.
Requests are listed in the fresh 448 capture's issue order (seq 23–212) for deterministic sequencing when
concurrencyis set to 1. The app issues them concurrently, so the order only pins where state switches land relative to other requests (zero phase on the campaign fetch, routing-map activation, token rotations).Production callers may keep the default bounded concurrency because the real app also overlaps this bootstrap work. Navigation events (
NavigateTo,NavigateBack) are list items too: their position is the point where the app changes screen, kept next to the request that anchors them.