hart-agency-backend

To add an endpoint to an event-sourced Express backend, update commands and queries alongside the central api.ts and index.ts implementation registry. Maintaining correct API and types import boundaries keeps frontend and mobile TypeScript compilation intact during backend changes.

The withEventStore generator pattern processes creation and transformation events synchronously. You must avoid async-in-generator mistakes by using deterministic ids and synchronous generator usage to ensure event-sourced aggregates execute safely without runtime failures.

Wiring projection consumers and Ambar reactions requires registering projection repositories and Ambar consumers correctly. Reactions must handle at-least-once delivery risks by implementing idempotency or marker events to prevent duplicate processing.

Runtime failures happen because TypeScript cannot catch multiple runtime registration points for events, projections, and endpoint wiring. Exhaustive event handling using accept([...]) and proper registry wiring are required to prevent failures only visible when code runs.

Implementing auth guards in a CQRS backend requires enforcing a proper resolve versus authorize split. You must use correct privileges and actor-type narrowing to ensure authorization logic safely separates from query and command resolution.

Yes, refactoring domain logic is supported by aligning commands, queries, endpoints, events, projections, and reactions. Reviewing code for runtime-only gotchas and following deterministic id conventions ensures safe changes across the event-sourced Express backend.