How should I understand the conceptual boundary between jmolecules-ddd and jmolecules-events?

[youngledo]

I previously opened issue #183 to ask why jmolecules-ddd and jmolecules-events are separated.

In the reply, the rationale mentioned that domain events are not part of the original pattern catalog in the blue DDD book, and that events are also used outside DDD, so it is preferable not to force DDD concepts onto users that only want to work with events:
#183

After looking into it more carefully, I noticed a nuance that confused me:

• In the later DDD Reference (2016-05) by Eric Evans, Domain Events is explicitly listed.
• That document also marks it with * New term introduced since the 2004 book.
• So it seems true both that:
  • Domain Event was not part of the original 2004 catalog, and
  • Domain Event was later incorporated into the DDD vocabulary/reference material.

Reference:
https://www.domainlanguage.com/wp-content/uploads/2016/05/DDD_Reference_2015-03.pdf

So my question is:

Should the separation between jmolecules-ddd and jmolecules-events be understood mainly as a modularization/reuse decision, rather than as a statement that domain events are not part of DDD?

Put differently: if Domain Events are considered part of the later DDD reference vocabulary, is the main reason for the separate module simply that the event abstraction is useful outside DDD as well?

I am asking mostly to understand the conceptual boundary correctly, not to argue for a change request.