What
Requests for a dialog on the user's machine now validate both the question and the answer against a schema, and fall back to the dialog's declared default whenever the host does not support that dialog, the question is malformed, the user cancels, or the answer does not parse.
Details
- Every case is logged with an outcome (undeclared, invalid_payload, cancelled, invalid_result, answered) and a latency measurement.
- The client refuses to forward its own directory-sync consent dialog back from the cloud session.
Evidence
tengu_remote_headless_client_host_dialog
Strings lifted out of the shipped bundle, so the claim above can be checked against them.