Remote/cloud repository-trust permission answers can now be named and flagged as user rejections
When a remote or cloud session responds to a permission request for the confirm_repository_trust tool, and the config.nameRepositoryTrustAnswers setting is turned on, the response is now annotated with the tool's name, the same way allowed responses were already annotated elsewhere via nameToolOnPermissionAllow. A denial of this request can now also carry a decisionClassification of user_reject.
This gives remote and cloud sessions more detailed information about repository-trust permission decisions, including explicitly marking a denial as a deliberate user rejection.