packages CLI: enable, disable, and remove Packages #300

This was generated by AI during triage.

Agent Brief

Category: enhancement
Summary: Add the folder-backed Package lifecycle without automatic publication.

Current behavior:
An Operator must move or delete Package folders by hand. Core considers a Package enabled only when its folder is in the enabled Package directory.

Desired behavior:
enable and disable move one Package between the enabled and disabled inventories. They refuse destination collisions and preserve the provenance stamp. remove deletes a disabled Package only after confirmation and refuses uncommitted or unrecorded local changes. Each command explains the next publication and client-sync steps but does not run them.

Before disabling compiled Package code, the CLI reports visible tables and explains that safe publication may refuse removal of populated tables. Package Delta cleanup uses the replay contract from the data-layer tickets once that contract exists.

Key interfaces:

• lyracore packages enable <name>
• lyracore packages disable <name>
• lyracore packages remove <name>
• Enabled and disabled Package directories

Acceptance criteria:

• Enabled state is derived only from folder location.
• Enable and disable are recoverable moves and preserve Package provenance.
• Name collisions fail before moving anything.
• Remove refuses dirty content and requires a disabled Package.
• A Package with visible tables gets the safe-publication warning before disable completes.
• Commands never publish or synchronize a client.

Out of scope:

• Applying or replaying Package Deltas
• Publishing Module changes