event_engine 0.1.0 → 0.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 47b43f18ac9a1a5d3afc2e169344b1750499409496e2035bcc25e23ed5ec7c13
-  data.tar.gz: 31ad25b00b80dd1f53a3005f7a6a7f87c1c0fd4328d3fa638467192622251e6b
+  metadata.gz: 9f780a13e96d7a1fd1534d39aeda5cca32379d283e886839538f969d2cdcfa53
+  data.tar.gz: 1dad812c37e3d4b44178d8d2a9b42b1623a94fef984c6e32d66f84a0b4a3d76a
 SHA512:
-  metadata.gz: 42338a458274a692268e1c95bf003f85a8053f3903b3383813c3780f70d13d23a3035e1b9e4435fdf1542344ddf4442aa7210d4be5cfe8cd9deb7a8e3ced8cef
-  data.tar.gz: 4621cf3779124f63c686e23ce3414bf67d4d7683b338153da3e1a24a7bf10776e2f82c085cff57a89e88b7e9e5c9e5bb228257ad0642d22747c31adabd4f327a
+  metadata.gz: 685bad2445b1b6022625790855b51c4614be06e7cfafc81556d959a1a2d3254663a5a701bccfdc805c3260ec19919e939f22a5733d64481bdf894a60daeae896
+  data.tar.gz: bd15af2c996f15d0422b624947c78fa2d2607e13a611b028ed6f03a3d5a470ee3d8963c15c038976c5bb2c164f3eebe41a90fe372d4c3c28b39abb0e4fa8d955

data/CHANGELOG.md

@@ -7,6 +7,79 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.2.1] - 2026-07-29
+
+### Fixed
+
+- Running `event_engine:catalog` broke `emit`. The task scaffolds a rules file
+  listing every catalogued event with no value, and those bare keys counted as
+  declared rules — so routing was considered active while every event resolved to
+  nothing, raising `UnroutableEventError` on emit until each rule was filled in.
+
+  An app that processes events through **handlers** rather than processors — for
+  example one using `event_engine-store`, whose `Recorder` observes every event —
+  could not emit at all after building its catalog.
+
+  An undecided rule is now treated as no rule: a rules file where nothing is decided
+  behaves exactly like no rules file, and `event_engine:rules:check` still reports
+  the undecided events so the gap stays visible.
+
+
+## [0.2.0] - 2026-07-29
+
+This release completes the split between **authoring** and **runtime**. Events are
+now declared with `event_engine-event_definition` and compiled into a committed
+catalog; this gem builds a validated event from that catalog and hands it to a
+processor. How an event is processed is declared by the host in a rules file.
+
+### Added
+
+- **Processing rules.** `config/event_rules.yml` declares which processor handles
+  each event, resolved **event → pack → default**. `event_engine:catalog` writes the
+  file alongside the catalog, listing every catalogued event so a new one is visible
+  rather than silently unrouted; rules you have already decided are preserved.
+- **Processor registry.** `EventEngine.register_processor(name, processor)`, with
+  processor gems registering themselves under the process types they service.
+- **Pack discovery.** `EventEngine.schema_sources` prefers `publisher_schema_paths`
+  when set and otherwise discovers every pack that registered itself, so a host with
+  packs in its Gemfile needs no per-pack configuration.
+- **`DefinitionPublisher`**, registered at boot, so a pack's generated helper routes
+  into `EventEngine.emit` with no wiring in the host.
+- **`event_engine:rules:check`** — verifies every rule names a registered processor
+  and that no catalogued event is left unrouted. Intended for CI or deploy.
+- Errors that name the fix: `UnregisteredProcessorError`, `UnroutedEventsError`,
+  `InvalidRulesError`.
+
+### Changed
+
+- **Breaking.** `process_type` now comes from the rules file, not the schema. The
+  catalog is the event's contract — what it carries — and no longer describes what
+  happens to it. Previously `emit` read `schema.process_type`, which raised
+  `NoMethodError` for any event authored by a pack.
+- **Breaking.** `EventEngine::EventDefinition::Schema` is now
+  `EventEngine::CatalogEntry`, at `lib/event_engine/catalog_entry.rb`. The old file
+  shared a require path with `event_engine-event_definition`, so in an app running
+  both gems this gem's own class never loaded.
+- **Breaking.** The Rails engine is now a `Rails::Railtie`. Hosts with
+  `mount EventEngine::Engine => "/…"` must remove that line; the gem served no routes.
+- **Breaking.** `event_engine:schema:catalog` is now `event_engine:catalog`.
+
+### Removed
+
+- **Breaking.** The authoring layer — the DSL, compiler, definition loader, lifecycle
+  definitions, schema writers and authoring rake tasks. Declare events with
+  `event_engine-event_definition` instead.
+- **Breaking.** `Configuration#default_processor`, `#domain_processors` and
+  `#event_processors`. Processing is declared in the rules file, which is now the only
+  source for that decision.
+- **Breaking.** `EventEngine::SubjectRegistry`, `EventEngine.define_subjects` and
+  `.subject_registry`. Subjects are an authoring concern; the runtime passes through
+  the subject its catalog entry declares.
+- The markdown catalog printer (`SchemaCatalog`). It omitted the domain, the
+  `from:`/`attr:` mapping and the fingerprint; `db/event_schema.json` is complete.
+- Unreferenced `ProcessType` and `EventSchemaMerger`.
+
+
 ## [0.1.0] - 2026-06-25
 
 ### Added