[prismatic7]

Closes #49.

What

Adds a Compress action alongside Uncompress — the first item on the README roadmap's "planned" list. It zips the matched file or folder into <name>.zip next to it.

Behaviour:

• Files compress to a single entry; folders keep the folder itself as the wrapper entry, like Finder's "Compress".
• An existing <name>.zip is never overwritten or skipped — the new archive is numbered (report (1).zip), the same convention as Move/Copy conflicts. The existing archive is left untouched.
• The source stays in place, exactly like a copy; Undo is not offered, consistent with Uncompress.
• No options popover (hasOptions == false), per ActionKind.hasOptions's design: the button hides entirely when there's nothing to configure. The issue's destination/timestamp options can layer on later as params if wanted — the schema makes that additive.

Implementation

• ActionKind.compress in the catalog (Models.swift), wired through RuleSchema (label, icon, group, empty params) — the catalog's exhaustive switches guided every site.
• ActionExecutor.compress uses ZIPFoundation's FileManager.zipItem (already a dependency via Uncompress) and the shared resolveDestination for numbering; the Dry Run plan case reports the archive as a copiedPath artifact with a rename note when the name was taken.

Three-path consistency (per AGENTS.md)

New action runs through the same plan()/execute() machinery shared by Dry Run, Run Now, and the watcher — no path-specific code touched.

Verification

• swift build clean.
• swift test: 333 tests in 28 suites, all passed (330 existing + 3 new).
• New tests cover: file compress (archive contents + source kept + plan), folder compress (recursive entries, wrapper folder), and existing-archive conflict (numbered name in both plan and execute, original archive intact).
• Left to CI: the rule editor UI rendering; no GUI run locally.