@cosmicdrift/kumiko-samples 0.363.0 → 0.364.0

package/samples/apps/ui-walkthrough/src/app/template-seed-data.ts

@@ -16,6 +16,9 @@ export type SeedTemplate = {
 // Document HTML marks a variable as an empty span; only link targets take {{name}}.
 const v = (name: string): string => `<span data-variable="${name}"></span>`;
 
+// Resource key of the logo image the invoice mail embeds (uploaded by seed-templates.ts).
+export const LOGO_RESOURCE_KEY = "logo-nordlicht.png";
+
 const AUTH_VARIABLE_SCHEMA = {
   appName: { type: "text", required: true },
   actionUrl: { type: "link", required: true },
@@ -44,16 +47,134 @@ const DOCUMENT_LINES_SCHEMA = {
   },
 } as const;
 
+// Same variable names the billing notifications declare; labels follow the template language.
+type InvoiceDocumentLabels = {
+  readonly recipientAddress: string;
+  readonly invoiceNumber: string;
+  readonly invoiceDate: string;
+  readonly invoiceTotal: string;
+  readonly netTotal: string;
+  readonly vatAmount: string;
+  readonly dueDate: string;
+  readonly lines: string;
+  readonly position: string;
+  readonly description: string;
+  readonly period: string;
+  readonly net: string;
+  readonly paymentReference: string;
+  readonly iban: string;
+};
+
+function invoiceDocumentSchema(labels: InvoiceDocumentLabels) {
+  return {
+    recipientAddress: {
+      type: "text",
+      required: true,
+      label: labels.recipientAddress,
+      example: "Familie Yilmaz, Lindenstraße 14, 24103 Kiel",
+    },
+    invoiceNumber: {
+      type: "text",
+      required: true,
+      label: labels.invoiceNumber,
+      example: "RE-2026-0142",
+    },
+    invoiceDate: { type: "date", required: true, label: labels.invoiceDate, example: "2026-10-01" },
+    dueDate: { type: "date", required: true, label: labels.dueDate, example: "2026-10-15" },
+    netTotal: {
+      type: "money",
+      label: labels.netTotal,
+      example: { amount: 107900, currency: "EUR" },
+    },
+    vatAmount: {
+      type: "money",
+      label: labels.vatAmount,
+      example: { amount: 20501, currency: "EUR" },
+    },
+    invoiceTotal: {
+      type: "money",
+      required: true,
+      label: labels.invoiceTotal,
+      example: { amount: 128401, currency: "EUR" },
+    },
+    lines: {
+      type: "list",
+      required: true,
+      label: labels.lines,
+      item: {
+        position: { type: "text", label: labels.position },
+        description: { type: "text", label: labels.description },
+        period: { type: "text", label: labels.period },
+        net: { type: "money", label: labels.net },
+      },
+      example: [
+        {
+          position: "1",
+          description: "Kaltmiete Lindenstraße 14, WE 3",
+          period: "Okt 2026",
+          net: { amount: 98000, currency: "EUR" },
+        },
+        {
+          position: "2",
+          description: "Stellplatz 7",
+          period: "Okt 2026",
+          net: { amount: 9900, currency: "EUR" },
+        },
+      ],
+    },
+    paymentReference: {
+      type: "text",
+      label: labels.paymentReference,
+      example: "RE-2026-0142 / Yilmaz",
+    },
+    iban: { type: "text", label: labels.iban, example: "DE12 2105 0170 0012 3456 78" },
+  } as const;
+}
+
+const INVOICE_DOCUMENT_SCHEMA_DE = invoiceDocumentSchema({
+  recipientAddress: "Empfängeradresse",
+  invoiceNumber: "Rechnungsnummer",
+  invoiceDate: "Rechnungsdatum",
+  invoiceTotal: "Rechnungsbetrag",
+  netTotal: "Nettobetrag",
+  vatAmount: "Umsatzsteuer",
+  dueDate: "Fälligkeitsdatum",
+  lines: "Rechnungspositionen",
+  position: "Nr.",
+  description: "Bezeichnung",
+  period: "Zeitraum",
+  net: "Netto",
+  paymentReference: "Zahlungsreferenz",
+  iban: "IBAN",
+});
+
+const INVOICE_DOCUMENT_SCHEMA_EN = invoiceDocumentSchema({
+  recipientAddress: "Recipient address",
+  invoiceNumber: "Invoice number",
+  invoiceDate: "Invoice date",
+  invoiceTotal: "Invoice total",
+  netTotal: "Net amount",
+  vatAmount: "VAT",
+  dueDate: "Due date",
+  lines: "Invoice lines",
+  position: "No.",
+  description: "Description",
+  period: "Period",
+  net: "Net",
+  paymentReference: "Payment reference",
+  iban: "IBAN",
+});
+
 export const SYSTEM_PDF_LAYOUT: SeedTemplate = {
   slug: "default",
   kind: "pdf-layout",
   locale: "en",
   title: "Briefpapier",
   content: [
-    `<div data-header><p><strong>${v("tenantName")}</strong></p></div>`,
+    `<div data-header><table><tbody><tr><td><img data-resource="logo" alt="Nordlicht"></td><td><p data-align="right" data-size="small">Am Hafen 12 · 24103 Kiel</p></td></tr></tbody></table></div>`,
     "<div data-content></div>",
     "<div data-signature></div>",
-    `<div data-footer><p>${v("tenantName")} · Seite ${v("page")} von ${v("pages")}</p></div>`,
+    `<div data-footer><p>Seite ${v("page")} von ${v("pages")}</p><p>${v("tenantName")} · HRB 18422 Kiel · IBAN DE12 2105 0170 0012 3456 78</p></div>`,
   ].join(""),
 };
 
@@ -65,14 +186,14 @@ export const TENANT_MAIL_LAYOUT_VERSIONS: readonly string[] = [
     `<div data-footer><p>${v("tenantName")}</p></div>`,
   ].join(""),
   [
-    `<div data-header><p><strong>${v("tenantName")}</strong></p><p>Ihre Hausverwaltung in Kiel</p></div>`,
+    '<div data-header><img data-resource="logo" alt="Nordlicht"></div>',
     "<div data-content></div>",
     `<div data-signature><p>Mit freundlichen Grüßen</p><p>${v("signature")}</p><p>${v("tenantName")}</p></div>`,
-    `<div data-footer><p>${v("imprint")}</p><p><a href="https://nordlicht-immobilien.de/datenschutz">Datenschutz</a> · <a href="{{unsubscribeUrl}}">Abmelden</a></p></div>`,
+    `<div data-footer><p>${v("imprint")}</p><p><a href="https://nordlicht-immobilien.de/datenschutz">Datenschutz</a> · <a href="{{unsubscribeUrl}}">Abmeldelink</a></p></div>`,
   ].join(""),
 ];
 
-const LINES_TABLE = `<table><tbody><tr><th><p>Position</p></th><th><p>Betrag</p></th></tr><tr data-each="lines" data-repeat-header=""><td><p>${v("description")}</p></td><td><p>${v("amount")}</p></td></tr></tbody></table>`;
+const LINES_TABLE = `<table><tbody><tr><th><p>Position</p></th><th><p data-align="right">Betrag</p></th></tr><tr data-each="lines" data-repeat-header=""><td><p>${v("description")}</p></td><td><p data-align="right">${v("amount")}</p></td></tr><tr><td><p><strong>Gesamt</strong></p></td><td><p data-align="right">${v("invoiceTotal")}</p></td></tr></tbody></table>`;
 
 // The registry of the billing notifications declares the variables, so these
 // templates carry no variableSchema of their own.
@@ -82,14 +203,14 @@ function invoiceIssuedBody(args: {
 }): string {
   const due = args.withDueDate ? ` Bitte überweisen Sie den Betrag bis zum ${v("dueDate")}.` : "";
   return [
-    "<h2>Ihre Rechnung ist da</h2>",
+    `<h2>Ihre Rechnung ${v("invoiceNumber")}</h2>`,
     `<p>Guten Tag ${v("recipientName")},</p>`,
-    `<p>${args.intro} <strong>${v("invoiceNumber")}</strong> über <strong>${v("invoiceTotal")}</strong>.${due}</p>`,
-    '<a data-button href="{{invoiceUrl}}">Rechnung öffnen</a>',
+    `<p>${args.intro} ${v("invoiceNumber")} über ${v("invoiceTotal")}.${due} Die Rechnung finden Sie als PDF im Anhang und jederzeit online.</p>`,
+    '<a data-button href="{{invoiceUrl}}">Rechnung online ansehen</a>',
     LINES_TABLE,
     "<hr>",
-    "<p>Mit freundlichen Grüßen</p>",
-    `<p>${v("tenantName")}</p>`,
+    "<p>Bei Fragen zur Rechnung antworten Sie einfach auf diese E-Mail.</p>",
+    `<p>${v("signature")}</p>`,
   ].join("");
 }
 
@@ -101,6 +222,12 @@ const invoiceIssuedMeta = (subject: string) => ({
   previewText: "Rechnung {{invoiceNumber}} über {{invoiceTotal}}, online abrufbar",
 });
 
+const tenantInvoiceMeta = (subject: string) => ({
+  ...invoiceIssuedMeta(subject),
+  senderName: "Nordlicht Immobilien GmbH",
+  replyTo: "buchhaltung@nordlicht-immobilien.de",
+});
+
 // The platform default has a due date; the tenant drafts below drop it, which
 // is what blocks publishing in the walkthrough.
 export const SYSTEM_INVOICE_ISSUED: SeedTemplate = {
@@ -123,7 +250,7 @@ export const INVOICE_ISSUED_DRAFT_VERSIONS: readonly SeedTemplate[] = [
       intro: "anbei senden wir Ihnen die Rechnung",
       withDueDate: false,
     }),
-    meta: invoiceIssuedMeta("Ihre Rechnung {{invoiceNumber}}"),
+    meta: tenantInvoiceMeta("Ihre Rechnung {{invoiceNumber}}"),
   },
   {
     slug: INVOICE_ISSUED_SLUG,
@@ -131,7 +258,7 @@ export const INVOICE_ISSUED_DRAFT_VERSIONS: readonly SeedTemplate[] = [
     locale: "de",
     title: "Rechnung versendet",
     content: invoiceIssuedBody({ intro: "anbei erhalten Sie die Rechnung", withDueDate: false }),
-    meta: invoiceIssuedMeta("Ihre Rechnung {{invoiceNumber}} von {{tenantName}}"),
+    meta: tenantInvoiceMeta("Ihre Rechnung {{invoiceNumber}} von {{tenantName}}"),
   },
 ];
 
@@ -279,7 +406,22 @@ export const SYSTEM_AUTH_MAILS: readonly SeedTemplate[] = [
   ]),
 ];
 
-const INVOICE_DOCUMENT_ROWS = `<table><tbody><tr><th><p>Leistung</p></th><th><p>Betrag</p></th></tr><tr data-each="lines" data-repeat-header=""><td><p>${v("description")}</p></td><td><p>${v("amount")}</p></td></tr></tbody></table>`;
+const UTILITY_ROWS = `<table><tbody><tr><th><p>Leistung</p></th><th><p>Betrag</p></th></tr><tr data-each="lines" data-repeat-header=""><td><p>${v("description")}</p></td><td><p>${v("amount")}</p></td></tr></tbody></table>`;
+
+const right = (inner: string): string => `<p data-align="right">${inner}</p>`;
+
+function invoiceRows(labels: {
+  readonly service: string;
+  readonly period: string;
+  readonly net: string;
+}): string {
+  return [
+    "<table><tbody>",
+    `<tr><th><p>#</p></th><th><p>${labels.service}</p></th><th><p>${labels.period}</p></th><th><p data-align="right">${labels.net}</p></th></tr>`,
+    `<tr data-each="lines" data-repeat-header=""><td><p>${v("position")}</p></td><td><p>${v("description")}</p></td><td><p>${v("period")}</p></td><td><p data-align="right">${v("net")}</p></td></tr>`,
+    "</tbody></table>",
+  ].join("");
+}
 
 export const SYSTEM_INVOICE_DOCUMENTS: readonly SeedTemplate[] = [
   {
@@ -288,16 +430,29 @@ export const SYSTEM_INVOICE_DOCUMENTS: readonly SeedTemplate[] = [
     locale: "de",
     title: "Rechnung",
     content: [
+      `<p data-size="small"><u>Nordlicht Immobilien GmbH · Am Hafen 12 · 24103 Kiel</u></p>`,
+      `<p>${v("recipientAddress")}</p>`,
+      right(`Rechnungsnummer: ${v("invoiceNumber")}`),
+      right(`Rechnungsdatum: ${v("invoiceDate")}`),
+      right(`Fällig am: ${v("dueDate")}`),
       `<h1>Rechnung ${v("invoiceNumber")}</h1>`,
-      `<p>Rechnungsdatum: ${v("invoiceDate")}</p>`,
-      `<p>Guten Tag ${v("customerName")},</p>`,
-      "<p>für unsere Leistungen stellen wir Ihnen folgenden Betrag in Rechnung.</p>",
-      INVOICE_DOCUMENT_ROWS,
-      `<p><strong>Gesamtbetrag: ${v("total")}</strong></p>`,
-      "<p>Bitte überweisen Sie den Betrag innerhalb von 14 Tagen auf unser Konto.</p>",
+      "<p>Sehr geehrte Damen und Herren,</p>",
+      "<p>wir stellen Ihnen die folgenden Leistungen in Rechnung:</p>",
+      invoiceRows({ service: "Leistung", period: "Zeitraum", net: "Netto" }),
+      right(`Nettobetrag ${v("netTotal")}`),
+      right(`Umsatzsteuer 19 % ${v("vatAmount")}`),
+      right(`<strong>Rechnungsbetrag ${v("invoiceTotal")}</strong>`),
+      `<p>Bitte überweisen Sie den Rechnungsbetrag bis zum ${v("dueDate")} unter Angabe der Referenz ${v("paymentReference")} auf ${v("iban")}.</p>`,
+      "<div data-page-break></div>",
+      "<p>Zahlungsbedingungen und Hinweise auf Seite 2 …</p>",
     ].join(""),
-    meta: { layoutSlug: "default", pageFormat: "A4", fileName: "Rechnung.pdf" },
-    variableSchema: DOCUMENT_LINES_SCHEMA,
+    meta: {
+      layoutSlug: "default",
+      pageFormat: "A4",
+      fileName: "rechnung-{{invoiceNumber}}.pdf",
+      metadata: { title: "Rechnung {{invoiceNumber}}" },
+    },
+    variableSchema: INVOICE_DOCUMENT_SCHEMA_DE,
   },
   {
     slug: "billing:invoice",
@@ -305,16 +460,29 @@ export const SYSTEM_INVOICE_DOCUMENTS: readonly SeedTemplate[] = [
     locale: "en",
     title: "Invoice",
     content: [
+      `<p data-size="small"><u>Nordlicht Immobilien GmbH · Am Hafen 12 · 24103 Kiel</u></p>`,
+      `<p>${v("recipientAddress")}</p>`,
+      right(`Invoice number: ${v("invoiceNumber")}`),
+      right(`Invoice date: ${v("invoiceDate")}`),
+      right(`Due on: ${v("dueDate")}`),
       `<h1>Invoice ${v("invoiceNumber")}</h1>`,
-      `<p>Invoice date: ${v("invoiceDate")}</p>`,
-      `<p>Dear ${v("customerName")},</p>`,
-      "<p>we charge you the following amount for our services.</p>",
-      INVOICE_DOCUMENT_ROWS.replace("Leistung", "Service").replace("Betrag", "Amount"),
-      `<p><strong>Total: ${v("total")}</strong></p>`,
-      "<p>Please transfer the amount to our account within 14 days.</p>",
+      "<p>Dear Sir or Madam,</p>",
+      "<p>we charge you the following services:</p>",
+      invoiceRows({ service: "Service", period: "Period", net: "Net" }),
+      right(`Net amount ${v("netTotal")}`),
+      right(`VAT 19 % ${v("vatAmount")}`),
+      right(`<strong>Total ${v("invoiceTotal")}</strong>`),
+      `<p>Please transfer the amount by ${v("dueDate")} quoting the reference ${v("paymentReference")} to ${v("iban")}.</p>`,
+      "<div data-page-break></div>",
+      "<p>Terms of payment and notes on page 2 …</p>",
     ].join(""),
-    meta: { layoutSlug: "default", pageFormat: "A4", fileName: "Invoice.pdf" },
-    variableSchema: DOCUMENT_LINES_SCHEMA,
+    meta: {
+      layoutSlug: "default",
+      pageFormat: "A4",
+      fileName: "invoice-{{invoiceNumber}}.pdf",
+      metadata: { title: "Invoice {{invoiceNumber}}" },
+    },
+    variableSchema: INVOICE_DOCUMENT_SCHEMA_EN,
   },
 ];
 
@@ -328,7 +496,7 @@ export const TENANT_UTILITY_STATEMENT: SeedTemplate = {
     `<p>Abrechnungsdatum: ${v("invoiceDate")}</p>`,
     `<p>Guten Tag ${v("customerName")},</p>`,
     "<p>nachfolgend erhalten Sie die Abrechnung der Betriebskosten für den Abrechnungszeitraum.</p>",
-    INVOICE_DOCUMENT_ROWS,
+    UTILITY_ROWS,
     `<p><strong>Ergebnis: ${v("total")}</strong></p>`,
     "<p>Ein Guthaben überweisen wir Ihnen innerhalb von 30 Tagen, eine Nachzahlung ist zum Monatsende fällig.</p>",
   ].join(""),
@@ -352,3 +520,51 @@ export const SYSTEM_TENANCY_CERTIFICATE: SeedTemplate = {
     invoiceDate: { type: "date", required: true },
   },
 };
+
+// Two other tenants customise the invoice for the "Anpassungen der Mandanten" drawer: one
+// published copy with a second save, one draft.
+export type TenantInvoiceOverride = {
+  readonly tenantId: string;
+  readonly tenantKey: string;
+  readonly tenantName: string;
+  readonly adminEmail: string;
+  readonly adminName: string;
+  readonly status: "active" | "draft";
+  readonly versions: readonly SeedTemplate[];
+};
+
+const SYSTEM_INVOICE_DE = SYSTEM_INVOICE_DOCUMENTS[0] as SeedTemplate;
+const INVOICE_INTRO = "<p>wir stellen Ihnen die folgenden Leistungen in Rechnung:</p>";
+
+function invoiceWithIntro(sentence: string): SeedTemplate {
+  return {
+    ...SYSTEM_INVOICE_DE,
+    content: SYSTEM_INVOICE_DE.content.replace(INVOICE_INTRO, `<p>${sentence}</p>`),
+  };
+}
+
+export const TENANT_INVOICE_OVERRIDES: readonly TenantInvoiceOverride[] = [
+  {
+    tenantId: "00000000-0000-4000-8000-000000000004",
+    tenantKey: "kuestenwohnen",
+    tenantName: "Küstenwohnen Kiel GmbH",
+    adminEmail: "verwaltung@kuestenwohnen-kiel.de",
+    adminName: "M. Petersen",
+    status: "active",
+    versions: [
+      invoiceWithIntro("für den genannten Zeitraum stellen wir Ihnen Folgendes in Rechnung:"),
+      invoiceWithIntro(
+        "für den genannten Zeitraum stellen wir Ihnen Folgendes in Rechnung. Die Nebenkosten rechnen wir jährlich ab.",
+      ),
+    ],
+  },
+  {
+    tenantId: "00000000-0000-4000-8000-000000000005",
+    tenantKey: "hansa-wohnbau",
+    tenantName: "Hansa Wohnbau eG",
+    adminEmail: "rechnungswesen@hansa-wohnbau.de",
+    adminName: "K. Lorenzen",
+    status: "draft",
+    versions: [invoiceWithIntro("nachfolgend die Abrechnung für Ihre Wohnung:")],
+  },
+];

package/samples/apps/ui-walkthrough/src/features/billing/feature.ts

@@ -10,6 +10,10 @@ const INVOICE_ISSUED_VARIABLES = {
     required: true,
     example: "Familie Yilmaz",
   }),
+  recipientEmail: templateVariable.text({
+    label: "Empfänger-Adresse",
+    example: "yilmaz.familie@example.org",
+  }),
   invoiceNumber: templateVariable.text({
     label: "Rechnungsnummer",
     required: true,

package/samples/apps/ui-walkthrough/src/run-config.ts

@@ -15,6 +15,7 @@ import { createTemplateResolverFeature } from "@cosmicdrift/kumiko-bundled-featu
 import { createDocumentDesignerFeature } from "@cosmicdrift/kumiko-document-designer";
 import { localeDe } from "@cosmicdrift/kumiko-locale-de";
 import { createRendererMailHtmlFeature } from "@cosmicdrift/kumiko-renderer-mail-html";
+import { createRendererPuppeteerClientFeature } from "@cosmicdrift/kumiko-renderer-puppeteer-client";
 import { TENANT_ADMIN_EMAIL } from "./app/auth-constants";
 import { billingFeature } from "./features/billing";
 import { rentalFeature } from "./features/rental";
@@ -35,6 +36,9 @@ export const APP_FEATURES = [
   // Mounted individually: composeRendererStack() would add a second template-resolver.
   createRendererFoundationFeature(),
   createRendererMailHtmlFeature(),
+  // The PDF preview of the template editor prints through the puppeteer-service
+  // (PUPPETEER_SERVICE_URL / PUPPETEER_AUTH_TOKEN); the e2e config starts one.
+  createRendererPuppeteerClientFeature(),
   createDeliveryFeature(),
   // In-memory transport: the test mail of the mail editor is rendered and
   // "sent" for real, nothing leaves the process. Every user resolves to the

package/samples/apps/use-all-bundled/feature-manifest.json

@@ -1423,7 +1423,7 @@
     },
     {
       "name": "jobs",
-      "description": "Persistence and operator tooling for background jobs registered via `r.job(...)`. Every job execution writes directly into `store_job_runs` (current status + duration) and `store_job_run_logs` (per-line log rows) from the BullMQ callbacks — no event stream in between (#2243). A daily `retention-cleanup` job deletes runs (and their logs) older than `retentionDays`; an hourly `stale-run-sweep` job marks runs stuck at status `running` past `staleRunTimeoutHours` as `failed` (#2246 — a crashed worker never fires the completion callback, so nothing else ever revisits the row). Exposes `jobs:write:trigger` (manual run) and `jobs:write:retry` (operator retry of a failed run), plus `jobs:query:list`, `jobs:query:details`, and `jobs:query:catalog` (manual jobs) for the operator UI. A job that declares `tenantVisibleFailure` also records its last failed attempt per tenant and subject in `store_tenant_job_failures`, which the tenant itself reads through `jobs:query:failures` — a translation key only, never the provider's message (fw#3079). A job that declares `tenantVisibleRun` also keeps its run state per tenant and subject in `store_tenant_job_runs` (queued, running, plus the latest completed or failed run, no payload, error text or logs), which the tenant reads through `jobs:query:tenant-runs` (fw#3616); the stale-run sweep fails its stuck `running` rows and drops its stuck `queued` rows.",
+      "description": "Persistence and operator tooling for background jobs registered via `r.job(...)`. Every job execution writes directly into `store_job_runs` (current status + duration) and `store_job_run_logs` (per-line log rows) from the BullMQ callbacks — no event stream in between (#2243). A daily `retention-cleanup` job deletes runs (and their logs) older than `retentionDays`; an hourly `stale-run-sweep` job marks runs stuck at status `running` past `staleRunTimeoutHours` as `failed` (#2246 — a crashed worker never fires the completion callback, so nothing else ever revisits the row). Exposes `jobs:write:trigger` (manual run) and `jobs:write:retry` (operator retry of a failed run), plus `jobs:query:list`, `jobs:query:details`, and `jobs:query:catalog` (manual jobs) for the operator UI. A job that declares `tenantVisibleFailure` also records its last failed attempt per tenant and subject in `store_tenant_job_failures`, which the tenant itself reads through `jobs:query:failures` — a translation key only, never the provider's message (fw#3079). A job that declares `tenantVisibleRun` also keeps its run state per tenant and subject in `store_tenant_job_runs` (queued, running, plus the latest completed or failed run, no payload, error text or logs), which the tenant reads through `jobs:query:tenant-runs` (fw#3616); the stale-run sweep fails its stuck `running` rows and drops `queued` rows older than `retentionDays`.",
       "toggleableDefault": null,
       "requires": [],
       "optionalRequires": [],
@@ -2170,7 +2170,7 @@
     },
     {
       "name": "renderer-puppeteer-client",
-      "description": "A `renderer-foundation` plugin that prints documents to PDF through a separately deployed `puppeteer-service`. A `document-pdf` request names a stored template (`{ slug, locale, variables }`): the plugin resolves the template and its `pdf-layout` (header, signature and footer regions), embeds every image as a data URI, turns repeating table header rows into a real table head and sends the finished HTML to the service, which performs no network fetches itself. The page format, margins, file name pattern and title come from the template meta. `renderAndStorePdf(ctx, ...)` renders and stores the PDF as a file with a `rendered-pdf` record that keeps the template and layout version, so a stored document can always be traced to the text it was created from. The `puppeteer-status` query tells a TenantAdmin whether the service answers; while it does not, rendering fails with a `puppeteer_unavailable` error (HTTP 503) and no PDF is created. `image-snapshot` requests still take ready HTML in `payload.content`. Configure the endpoint and token with `PUPPETEER_SERVICE_URL` and `PUPPETEER_AUTH_TOKEN`; the client retries 5xx and network errors with exponential backoff (default 3 retries), 4xx fails at once. The feature adds the `rendered_pdfs` table, so apps that mount it need a schema migration.",
+      "description": "A `renderer-foundation` plugin that prints documents to PDF through a separately deployed `puppeteer-service`. A `document-pdf` request names a stored template (`{ slug, locale, variables }`): the plugin resolves the template and its `pdf-layout` (header, signature and footer regions), embeds every image as a data URI, turns repeating table header rows into a real table head and sends the finished HTML to the service, which performs no network fetches itself. The page format, margins, file name pattern and title come from the template meta. A write handler renders with `renderPdfBeforeTransaction(ctx, { slug, locale, variables })` as its `beforeTransaction` phase, so the print service call holds no database connection, and stores the result with `storeRenderedPdf(ctx, event.prepared)` in the handler: a file plus a `rendered-pdf` record that keeps the template and layout version, so a stored document can always be traced to the text it was created from. The `puppeteer-status` query tells a TenantAdmin whether the service answers; while it does not, rendering fails with a `puppeteer_unavailable` error (HTTP 503) and no PDF is created. `image-snapshot` requests still take ready HTML in `payload.content`. Configure the endpoint and token with `PUPPETEER_SERVICE_URL` and `PUPPETEER_AUTH_TOKEN`; the client retries 5xx and network errors with exponential backoff (default 3 retries), 4xx fails at once. The feature adds the `rendered_pdfs` table, so apps that mount it need a schema migration.",
       "toggleableDefault": null,
       "requires": [
         "renderer-foundation"
@@ -2563,7 +2563,7 @@
     },
     {
       "name": "template-resolver",
-      "description": "Every piece of editable text lives here, in one entity: mail bodies, notification texts, PDF document templates, AI prompts and plain text blocks. What a record is used for is the `kind` (`notification`, `mail`, `mail-layout`, `document-pdf`, `pdf-layout`, `ai-prompt`, `text-block`, `snippet`, `image-snapshot`).\n\nReading is one call — `ctx.templateResolver.resolveTemplate({ tenantId, slug, kind, locale })`. It walks four levels: tenant+locale, system+locale, tenant+fallback-locale, system+fallback-locale. A tenant overrides a system default by simply having its own record; no application code changes. Writing programmatically goes through the `upsertSystem`, `upsertTenant`, `publish` and `archive` write handlers; a SystemAdmin retires or restores a system default with `publishSystem` and `archiveSystem`, and a tenant drops its override with `resetToSystem`.\n\nText an editor should be able to change belongs in a collection, declared at mount: `createTemplateResolverFeature({ collections: [{ id, kind, access: { roles }, nav }] })`. It appears in the navigation, and `access` is part of the mount because a bundled feature cannot know the host's roles. Each collection gets its own `<id>-list` / `<id>-item` / `<id>-set` handlers, so the dispatcher enforces the separation.\n\nHow a collection is edited follows from `contentFormat`: `plain` gives a text area, `rich` a small WYSIWYG (bold, italic, headings, lists, links), `markdown` a text area that stores markdown text (same insertable chips as `plain`). All three offer the collection's `variableSchema` as insertable chips and a preview rendered with sample data — an editor sees what `{{firstName}}` becomes without sending a mail. An app can register its own editor for a format; the last `clientFeature` that registers a format wins (a conflict logs a warning).\n\nA collection is tenant-wide by default. With `ownership: \"user\"` every user keeps their own entries — mail signatures being the obvious case. Those rows live in the separate `user-content-entry` entity and count as user data, so mounting one also requires the `template-resolver-user-data` feature and a migration on the app side.\n\n`validate` dry-runs the write pipeline for a draft (sanitizer, layout rules, placeholders) and reports what the template uses and misses. `export-bundle` / `import-bundle` (and `import-bundle-system`) move one template with all locales and resource files between tenants or environments; `copy-locale` starts a translation from an existing locale. Layouts are structured: a mail or PDF layout is `data-header` / `data-content` / `data-signature` / `data-footer` regions, and mjml layout source is system-only.\n\n`preview` renders a draft (or the stored template) with sample values taken from the `example` of each declared variable, through the same gates and the same mail renderer as a real send, and returns subject, html, `displayHtml` (the html with cid images as data URIs for an editor), text, attachments (inline images and files) and `checks` (images resolved, plain text present, size under 10 MiB, required placeholders used); nothing is saved or sent. `send-test` mails that rendering to the calling user's own address only, subject prefixed with `[TEST]`, at most 10 per user and hour; it needs `delivery`, `channel-email` and `renderer-mail-html` to be mounted.\n\nImages used by a template (`<img data-resource=\"logo\">`) are uploaded with `resourceUpload`, which re-encodes them, stores a file and links it under the key; `resourceRemove` unlinks it. `linkedResources` is written only through these two handlers. With `purpose: \"attachment\"` and a `fileName`, `resourceUpload` stores a PDF, PNG or JPEG as a file attachment of a mail template (original bytes, at most 10) that the mail renderer attaches after the inline images. `resourceLinkPdf` instead links a `document-pdf` template under a key: every mail sent from the template then carries that PDF, rendered at send time with the mail's own variables and locale, under a file name pattern such as `invoice-{{number}}.pdf`; files and linked PDFs share the limit of 10.\n\nReplaces the former `text-content` feature; its blocks now live here as kind `text-block`.",
+      "description": "Every piece of editable text lives here, in one entity: mail bodies, notification texts, PDF document templates, AI prompts and plain text blocks. What a record is used for is the `kind` (`notification`, `mail`, `mail-layout`, `document-pdf`, `pdf-layout`, `ai-prompt`, `text-block`, `snippet`, `image-snapshot`).\n\nReading is one call — `ctx.templateResolver.resolveTemplate({ tenantId, slug, kind, locale })`. It walks four levels: tenant+locale, system+locale, tenant+fallback-locale, system+fallback-locale. A tenant overrides a system default by simply having its own record; no application code changes. Writing programmatically goes through the `upsertSystem`, `upsertTenant`, `publish` and `archive` write handlers; a SystemAdmin retires or restores a system default with `publishSystem` and `archiveSystem`, and a tenant drops its override with `resetToSystem`. Saving a draft over an active template keeps the active version served and stores the edit beside it (column `draft`); `publish` makes it the served version, `discardDraft` / `discardDraftSystem` throws it away.\n\nText an editor should be able to change belongs in a collection, declared at mount: `createTemplateResolverFeature({ collections: [{ id, kind, access: { roles }, nav }] })`. It appears in the navigation, and `access` is part of the mount because a bundled feature cannot know the host's roles. Each collection gets its own `<id>-list` / `<id>-item` / `<id>-set` handlers, so the dispatcher enforces the separation.\n\nHow a collection is edited follows from `contentFormat`: `plain` gives a text area, `rich` a small WYSIWYG (bold, italic, headings, lists, links), `markdown` a text area that stores markdown text (same insertable chips as `plain`). All three offer the collection's `variableSchema` as insertable chips and a preview rendered with sample data — an editor sees what `{{firstName}}` becomes without sending a mail. An app can register its own editor for a format; the last `clientFeature` that registers a format wins (a conflict logs a warning).\n\nA collection is tenant-wide by default. With `ownership: \"user\"` every user keeps their own entries — mail signatures being the obvious case. Those rows live in the separate `user-content-entry` entity and count as user data, so mounting one also requires the `template-resolver-user-data` feature and a migration on the app side.\n\n`validate` dry-runs the write pipeline for a draft (sanitizer, layout rules, placeholders) and reports what the template uses and misses. `export-bundle` / `import-bundle` (and `import-bundle-system`) move one template with all locales and resource files between tenants or environments; `copy-locale` starts a translation from an existing locale. Layouts are structured: a mail or PDF layout is `data-header` / `data-content` / `data-signature` / `data-footer` regions, and mjml layout source is system-only.\n\n`preview` renders a draft (or the stored template) with sample values taken from the `example` of each declared variable, through the same gates and the same mail renderer as a real send, and returns subject, html, `displayHtml` (the html with cid images as data URIs for an editor), text, attachments (inline images and files) and `checks` (images resolved, plain text present, size under 10 MiB, required placeholders used); nothing is saved or sent. `send-test` mails that rendering to the calling user's own address only, subject prefixed with `[TEST]`, at most 10 per user and hour; it needs `delivery`, `channel-email` and `renderer-mail-html` to be mounted.\n\nImages used by a template (`<img data-resource=\"logo\">`) are uploaded with `resourceUpload`, which re-encodes them, stores a file and links it under the key; `resourceRemove` unlinks it. `linkedResources` is written only through these two handlers. With `purpose: \"attachment\"` and a `fileName`, `resourceUpload` stores a PDF, PNG or JPEG as a file attachment of a mail template (original bytes, at most 10) that the mail renderer attaches after the inline images. `resourceLinkPdf` instead links a `document-pdf` template under a key: every mail sent from the template then carries that PDF, rendered at send time with the mail's own variables and locale, under a file name pattern such as `invoice-{{number}}.pdf`; files and linked PDFs share the limit of 10.\n\nReplaces the former `text-content` feature; its blocks now live here as kind `text-block`.",
       "toggleableDefault": null,
       "requires": [],
       "optionalRequires": [],
@@ -2601,6 +2601,8 @@
         "template-resolver:write:archive",
         "template-resolver:write:archive-system",
         "template-resolver:write:copy-locale",
+        "template-resolver:write:discard-draft",
+        "template-resolver:write:discard-draft-system",
         "template-resolver:write:import-bundle",
         "template-resolver:write:import-bundle-system",
         "template-resolver:write:publish",