web: make the settings drawer readable and honest

[Rust-KVM]

Requested by 4c · project thread

Summary

Before: the Cloud section printed the raw getCloudState JSON ({"appUrl":…,"connected":false,"url":…}), wrapped mid-word. Many fields had only placeholders, so once filled (e.g. MQTT base topic "rustkvm") nothing said what they were. Save buttons fired silently. Some controls did nothing on the device, and the brightness slider never saved.

After: Cloud shows a status dot with "Connected / Not connected" and the API and App URLs on separate rows, with the inputs prefilled. Every field has a visible label, save actions report success or the device's error, and controls the device ignores are hidden.

How

• New util::fire_status: like fire, but writes "Saving…" / ok message / Failed: <error> into a status line. Used for cloud, Tailscale, extension, HTTPS, EDID, WOL, IP settings, SSH, MQTT, macros.
• Extension is a select (None / ATX power board / DC power board) instead of a free-text id; applying it reloads the Power section.
• Network and About render as label/value rows; virtual media, update and OCR status lines are full sentences.
• Bug fix: setBacklightSettings requires dim_after and off_after; the slider sent only max_brightness, so every change failed deserialization silently. They are now read and sent back unchanged.
• Hidden because the backend does not act on them: serial Send (sendCustomCommand only logs; old history is still shown and clearable), video sleep, host display idle (both stored, never read). Time zone shows as text instead of a disabled select.
• Danger-zone and deregister confirmations reworded; macro Delete asks first.
• .muted wraps with overflow-wrap: anywhere instead of word-break: break-all.

No RPC method or backend changes.

Testing

• cargo +nightly fmt --check in crates/rkvm-web
• cargo +nightly clippy --workspace --release --all-targets -- -D warnings (backend untouched)
• cargo +nightly test --workspace (backend untouched)
• Frontend touched: wasm32 clippy -D warnings clean locally; trunk build runs in CI
• Tested on an RK3588 device: needs a look at the settings drawer on the device (Cloud, MQTT, Extension, brightness)

Checklist

• No #[allow(...)] suppressions and no new unwrap() / expect() in production paths
• Hot paths stay zero-copy; periodic loops use MissedTickBehavior::Delay
• Shared protocol types live in rkvm-proto
• RPC method set changed → not changed
• Module tree or build invariants changed → not changed

---

Generated by Claude Code