@cosmicdrift/kumiko-bundled-features 0.178.0 → 0.178.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cosmicdrift/kumiko-bundled-features",
-  "version": "0.178.0",
+  "version": "0.178.1",
   "description": "Built-in features — tenant, user, auth, delivery. The stuff you'd rewrite anyway, already typed.",
   "license": "BUSL-1.1",
   "author": "Marc Frost <marc@cosmicdriftgamestudio.com>",
@@ -120,12 +120,12 @@
     "./step-dispatcher": "./src/step-dispatcher/index.ts"
   },
   "dependencies": {
-    "@cosmicdrift/kumiko-dispatcher-live": "0.178.0",
-    "@cosmicdrift/kumiko-framework": "0.178.0",
-    "@cosmicdrift/kumiko-headless": "0.178.0",
-    "@cosmicdrift/kumiko-renderer": "0.178.0",
-    "@cosmicdrift/kumiko-renderer-web": "0.178.0",
-    "@cosmicdrift/kumiko-types": "0.178.0",
+    "@cosmicdrift/kumiko-dispatcher-live": "0.178.1",
+    "@cosmicdrift/kumiko-framework": "0.178.1",
+    "@cosmicdrift/kumiko-headless": "0.178.1",
+    "@cosmicdrift/kumiko-renderer": "0.178.1",
+    "@cosmicdrift/kumiko-renderer-web": "0.178.1",
+    "@cosmicdrift/kumiko-types": "0.178.1",
     "@mollie/api-client": "^4.5.0",
     "imapflow": "^1.3.3",
     "mailparser": "^3.9.8",

package/src/template-resolver/api.ts

@@ -1,7 +1,6 @@
-// TemplateResolverApi — Cross-Feature-Schnittstelle. renderer-foundation
-// + delivery + Apps importieren NUR Types und holen die Implementation
-// runtime aus ctx.templateResolver. Pattern symmetrisch zu textContent
-// (siehe text-content/api.ts).
+// TemplateResolverApi — cross-feature interface. renderer-foundation,
+// delivery and apps import types ONLY and take the implementation from
+// ctx.templateResolver at runtime.
 
 import { selectMany } from "@cosmicdrift/kumiko-framework/bun-db";
 import type { DbConnection } from "@cosmicdrift/kumiko-framework/db";

package/src/template-resolver/feature.ts

@@ -15,14 +15,14 @@ import { upsertSystemWrite } from "./handlers/upsert-system.write";
 import { upsertTenantWrite } from "./handlers/upsert-tenant.write";
 import { templateResourceEntity } from "./table";
 
-// template-resolver — strukturierter Template-Storage mit Tenant-
-// Override-Hierarchie, Locale-Fallback und Resource-Linking via
-// file-foundation. Plan-Doc: kumiko-platform/docs/plans/features/template-resolver.md
+// template-resolver — structured template storage with tenant-override
+// hierarchy, locale fallback and resource linking via file-foundation.
+// Plan doc: kumiko-platform/docs/plans/features/template-resolver.md
 //
-// Konsumtions-Pfade:
-//   - Render-Time: ctx.templateResolver.resolveTemplate(...) (siehe api.ts)
-//   - Admin-UI: write/query-handlers (upsertSystem, upsertTenant, publish, archive, findById, list)
-//   - Cross-Feature: requireTemplateResolver(ctx, callerName) — Pattern wie requireTextContent
+// Consumption paths:
+//   - Render time: ctx.templateResolver.resolveTemplate(...) (see api.ts)
+//   - Admin UI: write/query handlers (upsertSystem, upsertTenant, publish, archive, findById, list)
+//   - Cross-feature: requireTemplateResolver(ctx, callerName)
 export type TemplateResolverOptions = {
   /** Content collections this app mounts. Declared here rather than inside the
    *  feature because `access` needs the host's role vocabulary — a bundled
@@ -50,7 +50,7 @@ export function createTemplateResolverFeature(opts: TemplateResolverOptions = {}
   }
   return defineFeature("template-resolver", (r) => {
     r.describe(
-      "Stores notification and mail templates in the database with a 4-level fallback: tenant+locale \u2192 system+locale \u2192 tenant+fallback-locale \u2192 system+fallback-locale. Call `ctx.templateResolver.resolveTemplate({ tenantId, slug, kind, locale })` at render time; manage templates via the `upsertSystem`, `upsertTenant`, `publish`, and `archive` write handlers. Tenants can override system-default templates without touching application code.",
+      "The one content store: notification and mail templates, PDF document templates, AI prompts and plain editable text blocks all live here as one entity, distinguished by `kind` (`notification`, `mail-html`, `document-pdf`, `ai-prompt`, `text-block`, `image-snapshot`). Resolution uses a 4-level fallback: tenant+locale \u2192 system+locale \u2192 tenant+fallback-locale \u2192 system+fallback-locale, so tenants can override system defaults without touching application code. Call `ctx.templateResolver.resolveTemplate({ tenantId, slug, kind, locale })` at render time; manage templates via the `upsertSystem`, `upsertTenant`, `publish` and `archive` write handlers. Apps that want an editable collection in their navigation declare it at mount: `createTemplateResolverFeature({ collections: [{ id, kind, access: { roles }, nav }] })` \u2014 `access` belongs to the mount because a bundled feature does not know the host's role vocabulary. Each collection gets its own `<id>-list` / `<id>-item` / `<id>-set` handlers carrying that collection's access rule, so the dispatcher enforces the separation. Replaces the former `text-content` feature, whose blocks now live here as kind `text-block`.",
     );
     r.uiHints({
       displayLabel: "Template Resolver",

package/src/template-resolver/handlers/shared.ts

@@ -3,14 +3,13 @@ import { z } from "zod";
 import { CONTENT_FORMATS, TEMPLATE_STATUSES, UPSERT_KINDS } from "../constants";
 import { templateResourceEntity, templateResourcesTable } from "../table";
 
-// Single executor pro Bundle — Pattern aus text-content. Wird von allen
-// 4 Handlers geteilt für create/update-Operationen mit Event-Store +
-// Optimistic-Lock.
+// One executor per bundle, shared by all four handlers for create/update via
+// event store + optimistic lock.
 export const executor = createEventStoreExecutor(templateResourcesTable, templateResourceEntity, {
   entityName: "template-resource",
 });
 
-// Slug-Regex symmetrisch zu text-content + plan-doc naming-convention.
+// Slug regex follows the plan-doc naming convention.
 export const slugSchema = z
   .string()
   .min(1)

package/src/template-resolver/handlers/upsert-system.write.ts

@@ -18,12 +18,11 @@ export const upsertSystemWrite = defineWriteHandler({
   access: { roles: ["SystemAdmin"] },
   handler: async (event, ctx) => {
     const db = ctx.db;
-    // @cast-boundary engine-payload — SYSTEM_TENANT_ID ist UUID-Literal,
-    // assert auf TenantId-Branded-Type (parseTenantId-Equivalent).
+    // @cast-boundary engine-payload — SYSTEM_TENANT_ID is a UUID literal,
+    // asserted to the branded TenantId (parseTenantId equivalent).
     const tenantId = SYSTEM_TENANT_ID as TenantId;
-    // executor-user muss SYSTEM_TENANT als tenantId haben, sonst sucht
-    // event-store stream unter user.tenantId statt SYSTEM_TENANT → conflict.
-    // Pattern symmetrisch zu text-content setWrite Override-Branch.
+    // The executor user must carry SYSTEM_TENANT as tenantId, otherwise the
+    // event store looks up the stream under user.tenantId → conflict.
     const executorUser = { ...event.user, tenantId };
 
     const existing = await fetchOne<TemplateResourceRow>(db, templateResourcesTable, {