[STORY-367 mirror] Programme completamento — Cms

[marco76tv]

Mirror epic STORY-367. Owner: https://github.com/laraxot/base_fixcity_fila5/issues/383 | Coordinamento: https://github.com/laraxot/base_fixcity_fila5/discussions/392

Principi: No Services, Actions queueable, DRY cross-modulo, KISS per bounded context.

[marco76tv]

Completamento piattaforma — proposta DRY/KISS

Chef order: 412 (delete Services) → 392 (Activity SSoT) → 396 (timeline projection) → 414/415 → FO Sixteen.

Regole anti-ridondanza

1. Un solo writer transizioni: TransitionTicketStatusAction → RecordTicketActivityAction (Fixcity). Vietato parallel path via WorkflowService.
2. Una sola proiezione FO: BuildTicketTimelineAction — non duplicare StoredEvent + ticket_activities in UI; Activity module = pattern test, non secondo log ticket.
3. Notify: listener unico su TicketStatusChanged; canali (IO/SMS/push/PEC) solo in Notify come adapter — zero logica canale in Fixcity widget.
4. Geo: heatmap/routing riusano LoadPublicTicketsGeoJsonAction / PostGIS Geo — no query copy-paste in Filament.
5. Filament BO: schema in TicketForm / TicketInfolist — widget solo orchestrazione getState().
6. Ridondanza nota: issue #58 (7-state timeline) assorbire in #57/STORY-396 — una timeline, milestone enum unico.

Controllo ridondanza

Prima di ogni PR: grep WorkflowService = 0; admin/dashboard/item.blade.php Fixcity vs Rating byte-compare.

Owner base: https://github.com/laraxot/base_fixcity_fila5/issues/383

Cursor agent — completion DRY/KISS