refactor(events): split services/events.py into a package

CHANGELOG.md

@@ -8,6 +8,10 @@ Format roughly follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## Unreleased
 
+### Changed
+
+- **The events service is a package, one module per write verb** ([#371](https://github.com/vidithq/vidit/pull/371), [`backend/app/services/events/`](backend/app/services/events), [`docs/engineering.md`](docs/engineering.md)). `services/events/` holds `create`, `request`, `geolocation`, `revision`, `batch` and `closure`, one write verb each, over the shared `errors`, `coordinates`, `source_links`, `rules` and `readiness` modules. The package root re-exports the public API, so every caller imports from `app.services.events` as before. The code moved unchanged.
+
 ### Fixed
 
 - **The map detail panel shows only the selected event** ([#357](https://github.com/vidithq/vidit/pull/357), [`frontend/src/app/map/page.tsx`](frontend/src/app/map/page.tsx), [`frontend/src/components/map/DetailSidePanel.tsx`](frontend/src/components/map/DetailSidePanel.tsx), [`docs/design.md`](docs/design.md#layout)). A failed load shows the error with a Retry control instead of the previous event, on the map and in the collection page's step player, and a late response for an earlier pin is discarded. The panel takes the whole read as one prop, so a caller cannot drop the error. Reopening a pin after closing it reads the event again.

backend/app/routers/events/read.py

@@ -363,10 +363,11 @@ def list_detections(
     publish floor (``ready``) or to those that don't (``incomplete``), ``all``
     being the whole queue; anything else is a 422, as ``view`` is on
     :func:`list_events`. The floor is :func:`detection_ready_predicate`, the SQL
-    projection of the one ``services.events._publish_detection`` enforces. Filtering
-    here rather than over the loaded page is the point: the queue pages at 10
-    rows over imports of several hundred, so a page-local filter answers about
-    ten detections while the analyst reads it as an answer about the queue.
+    projection of the one ``services/events/batch._publish_detection``
+    enforces. Filtering here rather than over the loaded page is the point: the
+    queue pages at 10 rows over imports of several hundred, so a page-local
+    filter answers about ten detections while the analyst reads it as an answer
+    about the queue.
 
     ``total`` counts the filtered set, so the page arithmetic describes what is
     being walked; ``ready_total`` and ``incomplete_total`` always count the

backend/app/routers/tags.py

@@ -43,7 +43,7 @@ def _warn_if_truncated(rows: list[Tag], *, view: str) -> list[Tag]:
 USER_CREATABLE_CATEGORIES = {"free"}
 
 # Server-managed taxonomy: every new geolocation must carry one tag from it
-# (enforced in `services/events.py`). Surfaced as the required selector on
+# (enforced in `services/events/rules.py`). Surfaced as the required selector on
 # the submit form via `?curated=true`.
 CURATED_CATEGORIES = ("capture_source",)