hermes - 💡(How to fix) Fix Agentic update review before installing Web UI updates

Problem

The current update experience appears to expose a raw version bump, for example Web UI v0.6.4 with a button like Update to v0.6.5. That confirms an update is available, but it does not help the user understand whether the update matters, what changed, what could break, or whether it is useful for their setup.

A better client experience would not be only: "there is an update, click here". It would be: "here is what matters in this update, here is what may affect you, and here is the explicit approval step before installing it."

Proposed experience

Before running an update, the Web UI should offer an agentic update review.

Suggested flow:

1. Detect the available update.
2. Fetch release notes, changelog, merged PRs, fixed issues, breaking changes, security notes, and migration notes when available.
3. Summarize the update in plain language.
4. Classify each meaningful change, for example:
   • useful for this user/setup
   • security-related
   • bug fix
   • cosmetic/UI-only
   • risky or potentially breaking
   • irrelevant for this user/setup
5. Let the user check or acknowledge the changes they care about.
6. Ask for explicit approval before applying the update.
7. Then run the update, ideally showing backup/rollback information if supported.

Why this matters

For an agent product, the update flow is a natural place to use agentic behavior. The updater can inspect the project/release context, explain the delta, and turn a blind update button into an informed decision.

This would be especially useful for users who do not want to read long changelogs manually but still want to know whether a release includes important fixes, security changes, compatibility changes, or features relevant to their workflow.

Acceptance criteria

• When an update is available, the UI can show an "Review update" step before "Install update".
• The review summarizes release notes and important merged changes.
• The review separates high-value changes from low-value/noise changes.
• The user must explicitly approve before the update is applied.
• If the review cannot fetch enough release data, the UI should say so clearly instead of presenting a confident summary.

Note

This request is based on seeing an update prompt from Web UI v0.6.4 to v0.6.5. If the Web UI is versioned separately from the main Hermes Agent release stream, the same pattern should still apply to that component's updater.