The pre-session screens carry server-issued recovery state as opaque tickets:
a ticket is a branded string a screen holds and passes on, and the values it
stands for — the login home's issued action with its server_params and QPL
ids, the search screen's action params, the code entry's submit action and
context token — live in the process's ticket registry
(screens.auth.tickets.registry.ts, one value per runtime layer). A ticket
issued in one runtime layer is not resolved in another; a screen resolves the
same values again on every action, so a repeated action works.
The pre-session screens carry server-issued recovery state as opaque tickets: a ticket is a branded string a screen holds and passes on, and the values it stands for — the login home's issued action with its
server_paramsand QPL ids, the search screen's action params, the code entry's submit action and context token — live in the process's ticket registry (screens.auth.tickets.registry.ts, one value per runtime layer). A ticket issued in one runtime layer is not resolved in another; a screen resolves the same values again on every action, so a repeated action works.