create-evlog-enricher

To add a new built-in enricher to evlog, implement a factory function using helpers like getHeader and mergeEventField, then update the six touchpoints: source, tests, docs, overview, AGENTS.md, and README.

An evlog enricher adds derived context to events across source code, tests, and documentation. You need one when extending evlog with consistent metadata like deployment info, tenant context, or feature flags.

Safe merging of evlog event fields is enforced by using the mergeEventField helper within your factory function, ensuring new enrichers do not overwrite existing data and maintain a consistent architecture.

Creating an evlog enricher requires updating six specific touchpoints: enricher source code, tests, built-in documentation, overview, AGENTS.md entry, and README to ensure consistent maintainability.

Yes, building a custom evlog enricher uses TypeScript to define the info interface, EnricherOptions, and the factory function, ensuring type-safe enrichment of events across your application.

The best way to structure an evlog enricher is using the create{Name}Enricher(options?: EnricherOptions) pattern, ensuring consistent architecture and safe merging of derived context into event fields.