Describe the issue

Shortcuts actions that use custom AppIntents fail with LNPerformActionErrorCodeActionNotFound, while the system “Find Virtual Machine” action works.

• Symptom: Adding or running an action connects Shortcuts → UTM, but fetching dynamic parameter defaults/options fails with ActionNotFound.

• Likely root cause: The action’s identifier previously relied on the derived fully-qualified Swift type name. After module/target/type renames, the derived ID changed. Shortcuts still requests the old ID persisted in existing shortcuts; UTM (exposing the new ID) replies “action not found”.

Reproduction steps

1. Use a Shortcut action (e.g. Get Virtual Machine Status).
2. Run the Shortcut or open the action to load its parameter options.
3. Observe the error in Console.

Console excerpt (Shortcuts.app)

[com.utmapp.UTM] Not Connected → Connecting → Connected
Starting operation <LNFetchParameterOptionDefaultValueConnectionOperation …>
Error Domain=LNContextErrorDomain Code=2002 "LNPerformActionErrorCodeActionNotFound"

Expected behavior

• The action loads parameter options (VM list) and returns status.

Actual behavior

• Shortcuts connects to UTM, then fails with ActionNotFound.

Configuration

• UTM Version: 4.7.4 (115)
• macOS Version: 26.0 (25A354)
• Mac Chip: M3 Pro

Proposed fix

• Stabilize identifiers: Add explicit, stable IDs to all custom AppIntents so they no longer depend on module/type names.