[Hermes Agent] “Could not load command” truncates “entry point file appears to be corrupted”

Extension

https://www.raycast.com/dailin4321/hermes-agent
(also observed with other Store extensions)

Raycast Version

1.104.25

OS Version

macOS

Description

When a Store command fails to load, Raycast shows:

• Title: “Something went wrong”
• Body: “You can try reloading, or report the error to the extension developer, by copying the log from the Action Panel ⌘K”
• Toast/footer: “Could not load command” / “The entry point file appears to be co...”

The footer string is truncated (“co...” instead of “corrupted”). The UI does not say to reinstall the extension from the Store. That makes a load/integrity failure look like an in-extension crash.

No logs, hostnames, or file paths attached.

Steps To Reproduce

1. Install a Store extension that ships compiled *.js command entry points (example: Hermes Agent).
2. Trigger a command-load failure (corrupt/mismatched entry file, or failed update).
3. Observe the error screen and the truncated footer.

Current Behaviour

Truncated “The entry point file appears to be co...” with only Reload as the obvious action.

Expected Behaviour

Full sentence, e.g. “The entry point file appears to be corrupted. Reinstall the extension from the Store.” Reload should still be offered.

Start by reproducing the failure with a Store extension that ships compiled *.js command entry points, then locate the error-screen and command-load handling in the TypeScript codebase. Done means the footer shows the complete corruption message, explains that the extension should be reinstalled from the Store, and still offers Reload.