### When `IDENTIFICATION_*` events fire
`IDENTIFICATION_OPERATOR_CHECK_UPDATE`, `IDENTIFICATION_DOCUMENTS_UPDATE` and
`IDENTIFICATION_BIOMETRY_UPDATE` are **not** completion events: they are emitted
mid-flow, while an identification attempt is actively progressing through one of
its sub-phases (typically on reinforced/second-provider identification flows).
Each is fired the moment that sub-phase starts:
- `IDENTIFICATION_OPERATOR_CHECK_UPDATE`: an operator live-check starts, or an
in-progress live-check is suspended.
- `IDENTIFICATION_DOCUMENTS_UPDATE`: document retrieval starts.
- `IDENTIFICATION_BIOMETRY_UPDATE`: biometry retrieval starts.

Do not treat receiving one of these as a signal that the identification step is
finished — the definitive outcome is only known once the enclosing Request
transitions status (`STATUS_UPDATE` / `STATUS_UPDATE_STEP`) or is finalized
(`REQUEST_FINALIZED`).