UX: apply_patch diff viewer shows raw deviceCode as plain text with no label or icon

### Self Checks
- [x] I have searched for existing issues, including closed ones.
- [x] I confirm that I am using English to submit this report.
- [x] I have filled in all the required fields.

### Syncless version
Cloud 2026.7.14

### Platform / Device
Web (Browser)

### Steps to reproduce
1. Open a task where an agent has called `apply_patch` with a valid unified diff.
2. Expand the tool call detail card.
3. Observe the text below the file path header and above the diff view.

### ✔️ Expected Behavior
The device on which the patch was applied should be identified with a clear label or icon (e.g. a cloud icon + "Cloud" or "Executed on: cloud"), so the user understands what it refers to at a glance.

### ❌ Actual Behavior
The raw `deviceCode` string (e.g. `cloud`) is rendered as bare monospace text with no prefix label, icon, or visual affordance. It appears as an isolated word, making it unclear what it represents — especially for users unfamiliar with the internal device code naming convention.

### Additional context
The `deviceName` value is resolved from the device list when available (showing the friendly display name), but falls back to the raw `deviceCode` when the device is not found. In both cases, there is no surrounding label to explain the semantic meaning. Suggested improvement: add a small device icon and/or a prefix such as a location/device badge to make the origin of the patch self-explanatory.

Start at the apply_patch diff viewer and tool call detail card, then trace how deviceName and the fallback deviceCode are rendered above the diff. Verify the current cloud case in the web interface and identify the relevant UI entry point. Done means the patch origin has a clear label or icon, including when only the raw deviceCode is available.

Written by the indexing model from the issue text.