@kehto/services 0.22.0 → 0.22.1

package/README.md

@@ -73,7 +73,10 @@ do not select a handler.
 `ok: true` means the selected target was ready and the convention was dispatched.
 The result includes `handled`, `handler`, `windowId`, and `convention`. The
 target receives the convention and opaque payload through one runtime-attested
-`inc.event`; there is no separate `intent.deliver` lifecycle.
+`intent.deliver` envelope with a nested `delivery` object. The host-owned
+`intent.onDelivery` binding buffers arrivals until a handler registers; INC is
+not required. Invocation and result semantics remain on the existing package
+contract pending the separate upstream NAP migration.
 
 Paja currently exposes only an exact-contract development simulator, and the
 playground currently exposes only a verified-manifest catalog builder. Phase
@@ -637,3 +640,13 @@ Generated API module: `docs/api/modules/_kehto_services.html` (run `pnpm docs:ap
 ## License
 
 MIT
+
+## NIP-5D event compatibility
+
+Current manifests use a direct artifact `x` hash, plain-text `content`, independent
+`z`/`i` routing declarations, and required `R` / optional `O` domains. Kehto also
+accepts legacy aggregate events through an isolated compatibility adapter.
+Existing `aggregateHash` host/cache/ACL fields carry the verified artifact hash
+for current events; legacy identities keep their original aggregate. Both paths
+verify signatures and bytes before runtime injection and `srcdoc` execution.
+For the schema and removal boundary, see [event migration](https://kehto.github.io/web/docs/migrations/NIP-5D-EVENT-SCHEMA.html).

package/dist/index.d.ts

@@ -2311,7 +2311,7 @@ declare function createCatalogIntentResolver(options: CatalogIntentResolverOptio
 /**
  * manifest-intent-catalog.ts — signed-manifest → NAP-INTENT catalog adapter.
  *
- * Adapts a resolved NIP-5A/5D napplet manifest's archetype tags into an
+ * Adapts a resolved NIP-5D manifest's normalized routing declarations into an
  * {@link IntentCatalogEntry} — the shape `createCatalogIntentResolver.loadCatalog`
  * consumes. This lets NAP-INTENT availability and handler candidacy flow from
  * verified manifest tags rather than host-injected catalog data.
@@ -2336,7 +2336,7 @@ interface ManifestArchetypeInput {
     /** Optional human-readable title from the manifest. */
     title?: string;
     /**
-     * Ordered convention contracts from the manifest's `archetype` tags.
+     * Normalized current z/i combinations or exact legacy archetype pairs.
      */
     archetypes: Array<{
         slug: string;

package/dist/index.js

@@ -4091,7 +4091,7 @@ function actionFromConvention(convention) {
   return match[2];
 }
 function manifestToIntentCatalogEntry(manifest) {
-  const archetypes = {};
+  const archetypes = /* @__PURE__ */ Object.create(null);
   for (const { slug, convention } of manifest.archetypes) {
     if (!/^[a-z0-9][a-z0-9-]*$/.test(slug)) {
       throw new TypeError("manifest archetype slug is invalid");