[STORY-397] Competitor gap programme — Activity

[marco76tv]

Mirror BMAD multi-repo per STORY-397 (competitor gap).

Base (story owner):

• Issue: https://github.com/laraxot/base_fixcity_fila5/issues/438
• Discussion: https://github.com/laraxot/base_fixcity_fila5/discussions/439
• Census: https://github.com/laraxot/base_fixcity_fila5/blob/dev/docs/wiki/concepts/fixcity-competitor-census.md

Owner: Activity

Cluster: 392, 396. Workflow eventi e timeline cittadino.

---

Creato da sync-story-397-multi-repo-github.sh

[marco76tv]

Discussion modulo: #21

Collegamento bidirezionale con base https://github.com/laraxot/base_fixcity_fila5/discussions/439

[marco76tv]

✅ Sync multi-repo completato. Story cluster modulo documentati in issue body. Prossimo: .dev.md per story owner primario.

[marco76tv]

Sync STORY-397 — Deep dive BMAD in base: 63 .dev.md, wiki state-machine + event-contract.

• Owner: https://github.com/laraxot/base_fixcity_fila5/issues/438
• Discussion base: https://github.com/laraxot/base_fixcity_fila5/discussions/439
• Fondazione: STORY-392 workflow + STORY-396 timeline
• Catalogo: docs/stories/STORY-397-competitor-gaps-catalog.dev.md

Cursor agent — multi-repo BMAD

[marco76tv]

Pattern event sourcing — confine modulo

Activity module: test di riferimento (ActivityEventSourcingTest), NON secondo store ticket.

SSoT ticket = Fixcity\Models\TicketActivity scritto da RecordTicketActivityAction.

Evitare sync StoredEvent↔TicketActivity — KISS: un solo log dominio Fixcity.