Add extensibility hooks for item/location lifecycle and scoped queries

[datengraben]

Summary

Small, independent extensibility additions identified while assessing what it would take to integrate CommonsBooking with an external community/group system (e.g. BuddyPress) without forking core logic. Each is its own commit:

• Lifecycle action hooks (b1322fc, trimmed by 4f5c5fc): adds commonsbooking_booking_cancelled, commonsbooking_item_created and commonsbooking_location_created. Previously the only custom hook in the plugin was commonsbooking_mail_sent, so external code had no reliable way to react to these state transitions without hooking generic save_post/post_updated and re-deriving the "what changed" logic itself. Each hook fires at the single existing point in the codebase where that transition already happens (Model\Booking::cancel(), Item::savePost(), Location::savePost()).

  Note: this originally also added commonsbooking_booking_created / commonsbooking_booking_confirmed, but Add filter/action hooks for admin-extensible booking process #12 (open, unmerged) already adds both at the same call sites with a richer ($postId, $booking) signature. Commit 4f5c5fc drops the duplicates from this PR to avoid double-firing with incompatible signatures once both land — Add filter/action hooks for admin-extensible booking process #12 is the source of truth for those two hooks.

• Filterable booking eligibility (c79ea5f): commonsbooking_isCurrentUserAllowedToBook() now applies a commonsbooking_isCurrentUserAllowedToBook filter to its result, matching the existing pattern used by commonsbooking_isCurrentUserAdmin / commonsbooking_isCurrentUserCBManager. Today, restricting a timeframe to members of some external group means minting a dedicated WordPress role per group, which doesn't scale. The filter lets external code layer additional eligibility logic on top of the existing role check.

• Scoped Item/Location queries (88187e4): BookablePost::get() (shared by Item::get()/Location::get(), and therefore also the map, the cb_items/cb_locations shortcodes and the REST API) now applies a commonsbooking_repository_query_args filter to the WP_Query args before running the query. This lets external code scope results by an arbitrary criterion (e.g. a postmeta value tying a post to an externally-managed group) instead of only the built-in category taxonomy. The query cache key is derived from the filtered args rather than the raw input args, so context-dependent scoping (e.g. "current group") can't return stale results cached for a different context.

None of these change default behavior — they only add hook points that no-op until something attaches a callback.

Test plan

• php -l on all changed files
• Confirmed no other overlap with Add filter/action hooks for admin-extensible booking process #12 (only touches Booking.php + 2 templates; my remaining hooks touch Model/Booking.php, Item.php, Location.php, includes/Users.php, Repository/BookablePost.php)
• CI (PHPUnit/PHPCS) — no local PHP toolchain (composer/vendor) available in this environment to run it beforehand
• Manual smoke test: attach a callback to each new hook/filter in a throwaway mu-plugin and confirm it fires at the expected point (booking cancellation, item/location creation, item/location listing)

---

Generated by Claude Code