New 'repository trust' confirmation flow for cloud sessions

What

• A new "repository trust" confirmation question type was added to the remote/cloud-session permission pipeline. Answering yes marks everything attached to that cloud session as trusted.
• The client refuses to show the confirmation unless the input matches exactly the digest served by the server. If the terminal isn't the device the cloud session is bound to, it adds a warning that the answer can't prove which device it came from, telling you to answer from claude.ai web, desktop, or mobile instead. If the terminal can't render the question at all, it leaves it unanswered for other devices along with an explanatory note.
• Tool-result rendering gained a matching "refusal" display: for repository-trust folder-wait errors, a localized message keyed repository_trust.folder_waits.<reason> is now shown instead of the plain error view, and detached/backgrounded tool call results are rendered with a dedicated rows/table-style component.
• A new nameRepositoryTrustAnswers capability flag, off by default, was added, gated behind a first-party check and a growthbook flag.
• The cloud session view now reports a repositoryTrust fingerprint and a directory-sync retention cutoff for directory-synced sessions.

Why

This gives Claude Code a way to ask for and record explicit trust confirmation before treating everything attached to a cloud session as trusted, with safeguards so the confirmation can only meaningfully be answered from the device the session is actually bound to.