Published event has no handler

How to fix

1. Add or restore the expected handler.
2. Remove the event if it is obsolete.
3. Align event names between publisher, contract, and handler registration.

What the rule validates

Code emits an event, but ArchPilot cannot find evidence that anything consumes it.

Why it matters

Unhandled events can represent dead integration paths or missed side effects.

Common causes

• A handler was removed but publisher stayed.
• The handler registration is missing.
• Event naming drift prevents matching publisher and handler.

Typical violation example

RepositoryUploadedEvent is published, but no handler is registered.

Typical compliant example

RepositoryUploadedEvent has a registered handler or is removed from the workflow.

Related rules

Adjacent categories

Related files/config

• apps/api/src
• packages/contracts/src

Related CLI commands

• archpilot validate
• archpilot validate --ci