@hasna/events 0.1.16 → 0.1.18

package/README.md

@@ -8,8 +8,19 @@ This package is local-first. By default it stores JSON files under `~/.hasna/eve
 - `events.json`
 - `deliveries.json`
 
-The CLI `--dir` flag has highest precedence, followed by `HASNA_EVENTS_DIR`,
-then the legacy `HASNA_EVENTS_HOME` fallback.
+The data home is resolved through the shared `@hasna/paths` resolver, in this order:
+
+1. The CLI `--dir` flag (highest precedence);
+2. the exact-app `HASNA_EVENTS_DIR` override, then the legacy
+   `HASNA_EVENTS_HOME` fallback;
+3. the `@hasna/paths`-resolved XDG data home (`HASNA_DATA_HOME`/`~/.local/share/hasna/events`),
+   adopted once `HASNA_DATA_HOME` is set or the store has been physically migrated there
+   (`events.json` exists at that home);
+4. the legacy `~/.hasna/events` default.
+
+Nothing moves on its own: the package keeps reading and writing whichever home is
+effective, and the legacy `~/.hasna/events` stays effective until an operator opts into
+the XDG layout or the store is migrated to it.
 
 ## Storage Runtime Contract
 
@@ -458,7 +469,10 @@ const events = new EventsClient({
 
 ## CLI
 
-The package exposes `events` and `hasna-events`.
+The package exposes `events` and `hasna-events`. `hasna-events` is a
+**deprecated alias** of `events` (same entrypoint, kept for npm parity with
+0.1.15); new usage should call `events` directly, and the alias is scheduled
+for removal in a future major release (hasna/apps#1602).
 
 Global options must come before the command group:
 
@@ -480,6 +494,17 @@ events channels match ops
 events channels remove ops
 ```
 
+`channels test` exits with code 1 when delivery fails and code 0 when delivery
+succeeds or is skipped by `--honor-filters`. Its JSON delivery result and human
+status output are preserved in either case.
+
+The standalone CLI and default embedded Commander commands deny private webhook
+targets unless the administrator sets `HASNA_EVENTS_ALLOW_PRIVATE_WEBHOOK_TARGETS`
+to a comma-separated list of exact hostnames or IP addresses. For an intentional
+local receiver, set `HASNA_EVENTS_ALLOW_PRIVATE_WEBHOOK_TARGETS=127.0.0.1`.
+This setting does not change SDK defaults or override an embedded host's custom
+`createClient` policy. Redirects and DNS results still undergo target validation.
+
 Field filters can match nested `data` or `metadata` values. Plain
 `--data`/`--metadata` values are strings, which keeps ids and slugs such as
 `001` intact. Use `--data-json` or `--metadata-json` for typed JSON predicates.

package/dist/app-event.js

@@ -365,18 +365,18 @@ function requireTimestamp(value, key, issues) {
   }
 }
 export {
-  APP_EVENT_V1_MAX_DATA_BYTES,
-  APP_EVENT_V1_MAX_REFS,
-  APP_EVENT_V1_MAX_SUMMARY_LENGTH,
-  APP_EVENT_V1_MAX_TARGETS,
-  APP_EVENT_V1_METADATA_KEY,
-  APP_EVENT_V1_SCHEMA_VERSION,
-  AppEventReplaySafetyError,
-  AppEventValidationError,
-  appEventV1FromEventEnvelope,
-  appEventV1ReplayIdentity,
-  appEventV1ToEventInput,
-  assertAppEventV1,
+  validateAppEventV1,
   assertAppEventV1ReplaySafe,
-  validateAppEventV1
+  assertAppEventV1,
+  appEventV1ToEventInput,
+  appEventV1ReplayIdentity,
+  appEventV1FromEventEnvelope,
+  AppEventValidationError,
+  AppEventReplaySafetyError,
+  APP_EVENT_V1_SCHEMA_VERSION,
+  APP_EVENT_V1_METADATA_KEY,
+  APP_EVENT_V1_MAX_TARGETS,
+  APP_EVENT_V1_MAX_SUMMARY_LENGTH,
+  APP_EVENT_V1_MAX_REFS,
+  APP_EVENT_V1_MAX_DATA_BYTES
 };

package/dist/catalog.js

@@ -175,17 +175,17 @@ function registerDistributionEventTypes(catalog = defaultEventTypeCatalog) {
   return catalog;
 }
 export {
-  DISTRIBUTION_EVENT_CONTRACT_SCHEMAS,
-  DISTRIBUTION_EVENT_TYPES,
-  EventTypeCatalog,
-  EventValidationError,
-  createDistributionEventDefinitions,
-  defaultEventTypeCatalog,
-  registerDistributionEventTypes,
-  validateAnnouncementSentData,
-  validateAppInstalledData,
-  validateFeedbackCreatedData,
-  validateFeedbackTriagedData,
+  validateRolloutData,
   validateReleasePublishedData,
-  validateRolloutData
+  validateFeedbackTriagedData,
+  validateFeedbackCreatedData,
+  validateAppInstalledData,
+  validateAnnouncementSentData,
+  registerDistributionEventTypes,
+  defaultEventTypeCatalog,
+  createDistributionEventDefinitions,
+  EventValidationError,
+  EventTypeCatalog,
+  DISTRIBUTION_EVENT_TYPES,
+  DISTRIBUTION_EVENT_CONTRACT_SCHEMAS
 };