Use smart uninstall for recognized applications in mo analyze

[Aaditya2605]

Problem

mo analyze is a natural place to find large applications and remove them. Today, deleting a selected path uses the generic move-to-Trash flow. For a recognized .app bundle, this removes the application itself but does not route through the application-aware cleanup already provided by mo uninstall, so related support files can remain.

Discussion #474 confirms that Analyze uses the generic Trash path. Discussion #1114 describes GUI detection after an app is removed through Finder, but the CLI Analyze workflow should also be complete when the GUI or background helper is not running.

Proposed behavior

For the current macOS implementation:

• When the selected Analyze item is a recognized .app bundle, offer the smart-uninstall flow.
• Reuse the existing mo uninstall discovery, review, confirmation, and Trash logic instead of duplicating application-cleanup rules.
• Show associated files before removal and keep the existing safety checks.
• Keep the current generic move-to-Trash behavior for normal files and directories.
• If the item cannot be identified safely as an application, do not guess.

The experimental Windows branch can use a separate platform-specific design later.

Suggested UX

When the user presses Delete on an application, Analyze could ask:

Uninstall this app and review its related files?

Confirming would open or invoke the existing smart-uninstall flow with that app preselected. The user could still choose to move only the application bundle to Trash.

Why

This makes deletion behavior consistent across Mole and prevents users from thinking an application was fully removed when only its bundle was moved.

Implementation

I would like to implement this after the maintainers confirm the preferred UX: should Analyze invoke the uninstall flow directly, or hand off to mo uninstall with the application preselected?

[tw93]

@Aaditya2605 Thanks for writing this up properly, including the two earlier discussions. The problem is real: deleting a .app in analyze moves the bundle to Trash and leaves the support files behind, and nothing on screen tells the user that happened.

I do not want analyze to invoke the uninstall flow inline, though. analyze is a disk explorer whose delete path is deliberately one generic, well-understood operation. Embedding a second command's discovery, review and confirmation inside it puts two different confirmation models on one screen, and creates a coupling that every future change to either side then has to respect.

What I would take is the smaller version. When the selected item is a recognized .app bundle, say so in the confirmation before deleting, and name the command that handles the rest: that this removes the bundle only, and that mo uninstall <App> also removes its support files. One mental model per command stays intact, and the "I thought it was fully removed" problem, which is the actual complaint, goes away.

If you want to implement that, I will merge it. If you build it and still think the inline flow is genuinely better, show me the confirmation screen and I will look again, but start from the smaller one.

[mehmetcansahin]

Implemented the smaller version as #1485.

[tw93]

@Aaditya2605 This shipped. #1485 landed the smaller version on main: deleting an app bundle in mo analyze now points at mo uninstall instead of silently leaving the support files behind, without pulling the uninstall flow inline.

mo update --nightly has it now, and it arrives in the next stable release.