feat(chat-tools): add delete_event tool for trashing wrong-venue duplicates

[chubes4]

Closes #286

Summary

Adds a delete_event chat tool wrapping a new data-machine-events/delete-event ability. Fills the gap when a show moves venues and the calendar ends up with two posts — get_venue_events finds both, delete_event trashes the stale one, and update_event (optionally) corrects the kept one.

Uses wp_trash_post() — NOT wp_delete_post() — so:

• The wp-admin trash safety net applies (recoverable if the wrong post was picked).
• The dedupe/upsert system can still see the post if it reappears in a scrape.

New files

• inc/Abilities/DeleteEventAbilities.php — registers data-machine-events/delete-event. Accepts event (single ID) or events (array of IDs) plus optional reason. Validates post existence and post_type === data_machine_events. Skips already-trashed posts into skipped[] rather than erroring. Returns deleted[] with {id, title, venue_name, start_date} snapshots captured pre-trash so the agent can confirm to the user. Emits datamachine_log + new data_machine_events_event_trashed action for future audit subscribers.
• inc/Api/Chat/Tools/DeleteEvent.php — BaseTool wrapper registering the delete_event chat tool. Tool description explicitly tells the agent to use it for wrong-venue duplicates or cancellations and that events go to trash (not hard-deleted).

Wiring

• data-machine-events.php bootstraps both the chat tool (next to UpdateEvent / MoveEvent) and the ability (next to EventUpdateAbilities / MoveEventAbilities).

Permissions

Uses the shared AbilityPermissions::canWrite() helper introduced in #291, matching the pattern in EventUpdateAbilities.php. Team members with write access get the tool; admin-only gating is gone.

How to verify

Chat invocation

User: Remove iration from firefly keep refinery
Agent: (calls get_venue_events for "firefly" → finds post ID 12345)
       (calls delete_event with { "event": 12345, "reason": "show moved venues; duplicate at old venue" })
       Trashed 1 event:
         - "Iration at The Firefly" (2025-04-12)
       The Refinery copy was kept.

Direct ability call

wp --allow-root --path=/var/www/extrachill.com --url=events.extrachill.com \
  ability execute data-machine-events/delete-event \
  --input='{"event": 12345, "reason": "duplicate at wrong venue"}'

Expected:

• Post 12345 transitions to post_status=trash.
• Response includes deleted[0] with id, title, venue_name, start_date captured pre-trash.
• datamachine_log info entry written with source=delete-event-ability.
• data_machine_events_event_trashed action fires.

Edge cases handled

• Already-trashed post → lands in skipped[] with reason "Already in trash.", does not error.
• Wrong post_type → skipped[] with explicit type mismatch reason.
• Missing post → skipped[] with "Post not found.".
• Neither event nor events provided → WP_Error with HTTP 400.
• Duplicate IDs across event + events → deduped before processing.

Notes

• wp_trash_post() is used, not wp_delete_post(). Hard delete is explicitly out of scope per the issue.
• No CHANGELOG.md edit, no version bump — homeboy owns both via conventional commits.

[homeboy-ci]

Homeboy Results — data-machine-events

Audit

✅ audit — passed

• requested_detectors — 4 finding(s)
• test_coverage — 2 finding(s)
• dead_code — 1 finding(s)
• intra-method-duplication — 1 finding(s)
• Total: 8 finding(s)

Deep dive: homeboy audit data-machine-events --changed-since fa857db

Tooling versions

• Homeboy CLI: homeboy 0.194.0+5dd0fa4
• Extension: wordpress from https://github.com/Extra-Chill/homeboy-extensions
• Extension revision: edb75b19
• Action: Extra-Chill/homeboy-action@v2