hermes - 💡(How to fix) Fix Optimization: Robust update process for hermes update [1 pull requests]

Problem

hermes update can leave web/node_modules in a partially broken state after an in-place update. In that state the dashboard service may crash-loop because build-time dependencies or package contents are missing or inconsistent.

Symptoms seen

• tsc: command not found
• lucide-react resolution failures during the web build
• hermes-agent.service repeatedly restarting and returning 502 behind the proxy

Desired behavior

The update process should detect and recover from an inconsistent web dependency tree instead of leaving the dashboard unusable.

Suggested improvements

• Validate the integrity of web/node_modules after update.
• Detect missing critical binaries or partial installs before restarting the service.
• Prefer an atomic recovery path such as a clean reinstall / npm ci when lockfile or dependency state is inconsistent.
• Surface a clear failure with recovery guidance rather than allowing a crash-loop.

Acceptance criteria

• hermes update does not leave the dashboard in a broken state.
• Missing build dependencies or partial installs are detected and repaired automatically or reported clearly.
• Regression tests cover the update/recovery path.