Module execution 

Engine-specific package removal and filesystem cleanup.

The execution phase consumes a precomputed RemovalPlan and mutates the database and filesystem state accordingly. The exact removal strategy depends on the package engine:

• MSIX, MSI, and native executable packages are removed through the engine first and then cleaned from disk.
• Zip and portable packages are staged into a trash directory before the database row is deleted so the install tree can be restored if metadata removal fails.

The functions here favor best-effort cleanup. Filesystem failures after the removal path has already made progress are logged when practical so the main removal outcome stays focused on whether the package was successfully removed.

Functions

cleanup_committed_journal 🔒

execute_removal

Execute package removal using a fresh database connection.

execute_removal_with_conn 🔒

Execute a removal plan with a caller-provided database connection.