n8n-nodes-dingtalk-card 0.3.0 → 0.4.0-beta.2

package/CHANGELOG.md

@@ -1,12 +1,20 @@
 # Changelog
 
-## 0.3.0 (stable release preparation)
+## 0.4.0-beta.2 (prerelease)
+
+Adds the fixed AI-host compatibility value `flowStatus: "3"` to Presentation `cardParamMap`, preserving all 13 Presentation contract fields. Real Mac DingTalk visual acceptance passed with the user-published AI-card template when `flowStatus=3` was supplied: all 13 Presentation fields and the summary rendered. No private template, group, or card identifiers are recorded. The package ships no DingTalk templates. npm `latest` remains stable at `0.3.0`.
+
+## 0.4.0-beta.1 (published beta)
+
+Adds opt-in Presentation Card Data Mode for Create & Deliver and Update. Version 1 descriptors cover alert, status, digest, action presentation metadata, and report families, with deterministic validation and mapping to string-valued `cardParamMap` entries. Includes template variable contract documentation and examples. Status transitions are guidance only; Action does not route or execute. On self-hosted production n8n/runners 2.44.6, supported UI install, loaded schema, valid status Presentation Update, and full Presentation-mode Create & Deliver/Streaming Update/Finalize/final whole-body JSON Update transport lifecycle passed, including legacy lifecycle compatibility. The legacy public AI template used does not satisfy the v0.4 template variable contract; visual Presentation rendering/template acceptance remains pending a user-published matching template. No DingTalk templates are shipped. The public beta is published as `beta -> 0.4.0-beta.1`; npm `latest` remains `0.3.0`. The release and production acceptance evidence are recorded in [verification](docs/VERIFICATION.md#v040-beta1-production-install-and-connected-instance-transport-acceptance-2026-10-25). v0.5 callback/action normalization and v0.6 renderer/A2UI work remain deferred.
+
+## 0.3.0 (stable)
 
 Promotes the published v0.3.0-beta.1 package to stable without adding node behavior. Includes guided Form String/JSON card parameter values, sanitized normalized outbound `errorDetails`, stable caller-controlled `outTrackId` recovery guidance, and the existing Stream callback behavior. Reusing an ID does not guarantee Create deduplication or upsert.
 
-Stable live acceptance on connected n8n 2.44.5 passed for Robot Direct Message and whole-body JSON Create & Deliver through Update, Streaming Update, Finalize and final JSON Update. Repeated Create using one caller-controlled `outTrackId` was accepted in the tested path; no deduplication or delivery guarantee is implied. A v0.3 interaction-card button click reached DingTalk Card Trigger through a Stream callback and its downstream asynchronous Update succeeded. The temporary test listener was unpublished after the test. Earlier user-performed Community Nodes UI uninstall/reinstall restored package, manifest and installed-version consistency; stable Update-button verification is scheduled after stable publication.
+Stable live acceptance on connected n8n 2.44.5 passed for Robot Direct Message and whole-body JSON Create & Deliver through Update, Streaming Update, Finalize and final JSON Update. Repeated Create using one caller-controlled `outTrackId` was accepted in the tested path; no deduplication or delivery guarantee is implied. A v0.3 interaction-card button click reached DingTalk Card Trigger through a Stream callback and its downstream asynchronous Update succeeded. The temporary test listener was unpublished after the test. Earlier user-performed Community Nodes UI uninstall/reinstall restored package, manifest and installed-version consistency. npm update-discovery reports stable `0.3.0` as latest for an installed `0.3.0-beta.1`; this does not claim that the n8n UI Update button was clicked or observed. Stable upgrade remains a user-operated supported Community Nodes UI action.
 
-This release closes the v0.3.0 stable acceptance scope. It does not certify v1.0, other templates or form interactions, reconnect/failure behavior, or stable n8n versions beyond the tested instance. See [verification](docs/VERIFICATION.md#v030-stable-release-preparation--2026-10-24).
+This release closes the v0.3.0 stable acceptance scope. It does not certify v1.0, other templates or form interactions, reconnect/failure behavior, or stable n8n versions beyond the tested instance. See [verification](docs/VERIFICATION.md#v030-stable-release-2026-10-24) for publication, provenance and canonical asset evidence.
 
 ## 0.2.0-beta.1 (prerelease)
 

package/README.md

@@ -2,34 +2,19 @@
 
 Focused n8n community nodes for the **DingTalk Card Platform lifecycle and Stream card callbacks**.
 
-**v0.3.0 is prepared for stable release; it becomes the stable release when published.** It adds guided Form String/JSON card parameter values, additive sanitized normalized outbound error details, and stable-ID recovery guidance with a packaged fixture; existing v0.2 Stream behavior is preserved. Connected-instance acceptance on self-hosted production n8n 2.44.5 closes the documented v0.3 stable scope; this does not certify v1.0 or untested platform/runtime behavior. This project is not n8n-verified and is not affiliated with DingTalk or n8n.
+**v0.3.0 is the stable release.** It adds guided Form String/JSON card parameter values, additive sanitized normalized outbound error details, and stable-ID recovery guidance with a packaged fixture; existing v0.2 Stream behavior is preserved. Connected-instance acceptance on self-hosted production n8n 2.44.5 closes the documented v0.3 stable scope; this does not certify v1.0 or untested platform/runtime behavior. This project is not n8n-verified and is not affiliated with DingTalk or n8n.
 
-The published beta remains `v0.3.0-beta.1` until stable publication. The OIDC workflow supports exact prerelease and stable tags with provenance: beta uses the `beta` dist-tag, and stable `v0.3.0` uses `latest`. After a stable version exists, beta publication leaves `latest` unchanged.
+**v0.4.0-beta.2 is a prerelease** for the v0.4.0 milestone. It adds the fixed AI-host compatibility value `flowStatus="3"` to Presentation card data. Real Mac DingTalk visual acceptance passed with the user-published AI-card template when this value was supplied; all 13 Presentation fields and the summary rendered. The package ships no DingTalk templates. See the [presentation contract](docs/PRESENTATION.md) and [release verification](docs/VERIFICATION.md).
+
+The npm `beta` dist-tag will resolve to `0.4.0-beta.2` after publication; npm `latest` remains stable at `0.3.0`. Releases use GitHub Actions Trusted Publisher/OIDC with provenance. Beta publication leaves `latest` unchanged now that a stable version exists.
 
 It provides **DingTalk Card**, **DingTalk Card Trigger**, and the shared **DingTalk Card API** enterprise app credential. It does not implement OA, todo, tables or general robot messaging, and does not depend on `@cryozerolabs/n8n-nodes-dingtalk`. Robot delivery fields here exist only to deliver Card Platform instances.
 
 ## Installation
 
-Requires Node.js 24+ and a compatible n8n installation. Development compiles and loads the node against `n8n-workflow` 2.44.2 (the dependency of current stable n8n 2.44.6); full runtime/UI compatibility is not yet certified. CI uses Node 24. Current stable n8n 2.44.6 declares Node >=24; this takes precedence over older starter guidance mentioning Node 22.
-
-Install the package in self-hosted n8n from **Settings > Community Nodes > Install** by entering `n8n-nodes-dingtalk-card@0.3.0` after stable publication (or `@latest`). Community-node installation requires an Owner or Admin account and may be disabled by instance policy. npm installation does not certify live DingTalk behavior. The tested live scope and remaining limits are documented below; stable Update-button verification is scheduled after publication; v1.0 readiness is not certified.
-
-To rebuild the previously published v0.2.0-beta.1 artifact from its tag:
-
-```sh
-git clone https://github.com/NTLx/n8n-nodes-dingtalk-card.git
-cd n8n-nodes-dingtalk-card
-git checkout v0.2.0-beta.1
-npm ci
-npm run build
-npm test
-npm pack
-# Install the resulting tgz in your self-hosted n8n community-node directory:
-cd ~/.n8n/nodes
-npm install /absolute/path/to/n8n-nodes-dingtalk-card-0.2.0-beta.1.tgz
-```
+Requires Node.js 24+ and a compatible n8n installation. Development compiles and loads the node against `n8n-workflow` 2.44.2 (the dependency of n8n 2.44.6). Production install and the documented connected-instance transport paths passed on self-hosted n8n/runners 2.44.6; client pixel-perfect visual inspection was not independently performed, and other runtime versions are not certified. CI uses Node 24. n8n 2.44.6 declares Node >=24; this takes precedence over older starter guidance mentioning Node 22.
 
-Create the community-node directory/package.json if needed, run as the n8n service account, and restart n8n after installation. Container users must install into a persistent volume accessible to n8n. For development use `npm run dev` with the official CLI; follow its prerequisites for your n8n version.
+Install or upgrade the package through n8n's supported **Settings > Community Nodes** lifecycle. To install, enter `n8n-nodes-dingtalk-card` (stable) or `n8n-nodes-dingtalk-card@beta` (current beta). To install or upgrade to an exact prerelease version in the UI, uninstall the package and reinstall it with the exact version, for example `n8n-nodes-dingtalk-card@0.4.0-beta.1`; n8n's standard Update action targets the latest version. Where available, the official Public API `POST /api/v1/community-packages` and `PATCH /api/v1/community-packages/{packageName}` support package management and explicit update versions; use API keys scoped to `communityPackage:list` and `communityPackage:update` as applicable. See [n8n Community Nodes installation and management](https://docs.n8n.io/integrations/community-nodes/installation-and-management/gui-installation/) and [Public API authentication and scopes](https://docs.n8n.io/api/authentication/). Community-node installation requires an Owner or Admin account and may be disabled by instance policy. Installation does not certify live DingTalk behavior. The tested live scope and remaining limits are documented below; v1.0 readiness is not certified.
 
 ## Credentials
 
@@ -50,7 +35,7 @@ The credential test acquires an app token only. It does not send a card or prove
 | Streaming Update | PUT one frame with `key`, `content`, `guid`, `isFull`, `isFinalize`, `isError` |
 | Finalize | PUT a terminal streaming frame: success sets `isFinalize=true,isError=false`; failure sets `isError=true,isFinalize=false` |
 
-**Form** input provides guided fields. Card Data has its own Form/JSON selector; the JSON form is the full `{"cardParamMap":{"title":"Example"}}` object. Form parameters default to **String** mode, which preserves existing values; choose **JSON** mode to enter an object, array, or scalar that is serialized into the string required by `cardParamMap`. **JSON** input accepts the official request body for advanced delivery/space models, `privateData`, `cardUpdateOptions`, `userIdType`, or `callbackType: "STREAM"`. Fields pass through; you are responsible for model/space consistency. This prerelease provides no HTTP callback listener or guided HTTP mode.
+**Form** input provides guided fields. Card Data has its own Form/JSON/Presentation selector; the JSON form is the full `{"cardParamMap":{"title":"Example"}}` object. Presentation maps the v1 alert/status/digest/action/report descriptor into string-valued template variables. Form parameters default to **String** mode, which preserves existing values; choose **JSON** mode to enter an object, array, or scalar that is serialized into the string required by `cardParamMap`. **JSON** input accepts the official request body for advanced delivery/space models, `privateData`, `cardUpdateOptions`, `userIdType`, or `callbackType: "STREAM"`. Fields pass through; you are responsible for model/space consistency. Presentation variable names are a contract for templates you publish; no platform template or component is included or verified by this package.
 
 `outTrackId` identifies a card within DingTalk's app context and is always returned. Create generates a UUID when missing/empty; that generated ID is stable only within that execution. A rerun may generate a different ID. To refer to the same logical card across executions, derive and supply the ID from a stable business/event key, such as an order ID plus an immutable event ID; do not derive it from a random value generated on each attempt. Preserve that same caller-controlled ID for any manual replay. A repeated Create with the same ID does not guarantee deduplication or upsert and is not an Update: verify whether the card/delivery already exists, then use Update if the card exists. Store the create output before later lifecycle operations.
 
@@ -124,7 +109,7 @@ Uses the official [n8n node CLI](https://docs.n8n.io/connect/create-nodes/build-
 
 Programmatic execution is intentional: shared token handling, strict 2xx/partial-delivery failure checks, generated identifier propagation and sanitized item-level errors are implemented once, separated from pure payload builders. The current custom credential-test context in `n8n-workflow` exposes only the legacy `request` helper; that single call has a documented lint exception and sanitized error boundary. Main execution uses `httpRequest`. Pure helper errors are converted to `NodeOperationError` at the execution boundary.
 
-See [verification record](docs/VERIFICATION.md) for exact local/CI gates, dependency findings and limitations. GitHub prereleases are conditional on all non-live gates passing. No stable release is implied.
+See [verification record](docs/VERIFICATION.md) for release identity, public artifact digests, provenance, update-discovery evidence, exact local/CI gates, dependency findings and limitations.
 
 ## Roadmap
 
@@ -132,6 +117,6 @@ The direction is **Interactive-first, AI-when-needed**: use DingTalk cards for p
 
 The durable architecture, scope boundaries, controlled A2UI contract, and anti-drift decision rules are in the [design baseline](docs/DESIGN.md); the roadmap is subordinate to it.
 
-Historical milestones: **v0.1.0-beta.1** introduced outbound Card Platform lifecycle operations; **v0.2.0-beta.1** added the narrow Stream callback trigger and explicit callback opt-in, with one real request-button path verified; **v0.3.0-beta.1** added Form String/JSON values, normalized outbound error details and stable-ID recovery guidance. v0.3.0 stable acceptance evidence and limits are recorded in [verification](docs/VERIFICATION.md#v030-stable-release-preparation--2026-10-24).
+Historical milestones: **v0.1.0-beta.1** introduced outbound Card Platform lifecycle operations; **v0.2.0-beta.1** added the narrow Stream callback trigger and explicit callback opt-in, with one real request-button path verified; **v0.3.0-beta.1** added Form String/JSON values, normalized outbound error details and stable-ID recovery guidance, and **v0.3.0** is its stable release. Stable acceptance evidence and limits are recorded in [verification](docs/VERIFICATION.md#v030-stable-release-2026-10-24).
 
 MIT licensed. Please remove identifiers, card data and credentials before filing an issue.

package/dist/nodes/DingTalkCard/DingTalkCard.node.js

@@ -3,6 +3,7 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.DingTalkCard = void 0;
 const n8n_workflow_1 = require("n8n-workflow");
 const payload_1 = require("./payload");
+const presentation_1 = require("./presentation");
 const transport_1 = require("./transport");
 const operations = ['createAndDeliver', 'update'];
 const streamOperations = ['stream', 'finalize'];
@@ -52,6 +53,17 @@ const properties = [
         ],
         description: 'Use guided fields or supply the official API request body',
     },
+    {
+        displayName: 'Presentation Descriptor',
+        name: 'presentationDescriptor',
+        type: 'json',
+        default: '{}',
+        required: true,
+        displayOptions: {
+            show: { inputMode: ['form'], operation: operations, cardDataMode: ['presentation'] },
+        },
+        description: 'Versioned presentation descriptor mapped to the documented template variables',
+    },
     {
         displayName: 'Request Body',
         name: 'requestBody',
@@ -95,6 +107,7 @@ const properties = [
         options: [
             { name: 'Form', value: 'form' },
             { name: 'JSON', value: 'json' },
+            { name: 'Presentation', value: 'presentation' },
         ],
         displayOptions: { show: { inputMode: ['form'], operation: operations } },
     },
@@ -304,9 +317,11 @@ class DingTalkCard {
                 else {
                     body.outTrackId = this.getNodeParameter('outTrackId', i);
                     if (operations.includes(operation)) {
-                        body.cardData =
-                            this.getNodeParameter('cardDataMode', i) === 'json'
-                                ? (0, payload_1.jsonObject)(this.getNodeParameter('cardData', i), 'Card Data')
+                        const cardDataMode = this.getNodeParameter('cardDataMode', i);
+                        body.cardData = cardDataMode === 'json'
+                            ? (0, payload_1.jsonObject)(this.getNodeParameter('cardData', i), 'Card Data')
+                            : cardDataMode === 'presentation'
+                                ? (0, presentation_1.presentationCardData)((0, payload_1.jsonObject)(this.getNodeParameter('presentationDescriptor', i), 'Presentation Descriptor'))
                                 : (0, payload_1.formCardData)(this.getNodeParameter('cardParameters.parameters', i, []));
                         if (operation === 'createAndDeliver') {
                             body.cardTemplateId = this.getNodeParameter('cardTemplateId', i);

package/dist/nodes/DingTalkCard/presentation.js

@@ -0,0 +1,114 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.presentationCardData = presentationCardData;
+const transport_1 = require("./transport");
+const tones = ['neutral', 'info', 'success', 'warning', 'danger'];
+const states = ['idle', 'running', 'success', 'failed', 'cancelled'];
+function record(value, label) {
+    if (!(0, transport_1.object)(value))
+        throw new transport_1.CardError(`Presentation ${label} must be an object.`);
+    return value;
+}
+function fields(value, allowed, label) {
+    for (const key of Object.keys(value))
+        if (!allowed.includes(key))
+            throw new transport_1.CardError(`Unknown Presentation ${label} field "${key}".`);
+}
+function string(value, label, max = 1000) {
+    if (typeof value !== 'string' || !value.trim() || value.length > max)
+        throw new transport_1.CardError(`Presentation ${label} must be a non-empty string of at most ${max} characters.`);
+    return value;
+}
+function optionalString(value, label, max = 1000) {
+    return value === undefined ? undefined : string(value, label, max);
+}
+function tone(value) {
+    if (typeof value !== 'string' || !tones.includes(value))
+        throw new transport_1.CardError(`Presentation tone must be one of: ${tones.join(', ')}.`);
+    return value;
+}
+function list(value, label) {
+    if (!Array.isArray(value) || value.length < 1 || value.length > 20)
+        throw new transport_1.CardError(`Presentation ${label} must contain between 1 and 20 items.`);
+    return value;
+}
+function json(value) {
+    return JSON.stringify(value);
+}
+function presentationCardData(input) {
+    const d = record(input, 'descriptor');
+    if (d.version !== '1')
+        throw new transport_1.CardError('Unsupported Presentation version. Supported version: "1".');
+    const family = d.family;
+    if (!['alert', 'status', 'digest', 'action', 'report'].includes(String(family)))
+        throw new transport_1.CardError('Unsupported Presentation family.');
+    const common = ['version', 'family', 'title', 'summary', 'tone'];
+    const map = Object.create(null);
+    map.presentationVersion = '1';
+    map.presentationFamily = family;
+    map.flowStatus = '3';
+    map.title = string(d.title, 'title', 200);
+    const summary = optionalString(d.summary, 'summary');
+    if (summary !== undefined)
+        map.summary = summary;
+    map.tone = tone(d.tone);
+    const familyFields = {
+        alert: ['source', 'occurredAt'],
+        status: ['state', 'details'],
+        digest: ['items'],
+        action: ['label', 'description'],
+        report: ['sections'],
+    };
+    fields(d, [...common, ...familyFields[family]], 'descriptor');
+    switch (family) {
+        case 'alert': {
+            const source = optionalString(d.source, 'source', 200);
+            const occurredAt = optionalString(d.occurredAt, 'occurredAt', 100);
+            if (source !== undefined)
+                map.source = source;
+            if (occurredAt !== undefined)
+                map.occurredAt = occurredAt;
+            break;
+        }
+        case 'status':
+            if (typeof d.state !== 'string' || !states.includes(d.state))
+                throw new transport_1.CardError(`Presentation state must be one of: ${states.join(', ')}.`);
+            map.state = d.state;
+            if (d.details !== undefined)
+                map.details = string(d.details, 'details');
+            break;
+        case 'digest': {
+            const items = list(d.items, 'items').map((raw, i) => {
+                const item = record(raw, `items[${i}]`);
+                fields(item, ['title', 'summary', 'tone'], `items[${i}]`);
+                const entry = { title: string(item.title, `items[${i}].title`, 200) };
+                const itemSummary = optionalString(item.summary, `items[${i}].summary`);
+                if (itemSummary !== undefined)
+                    entry.summary = itemSummary;
+                if (item.tone !== undefined)
+                    entry.tone = tone(item.tone);
+                return entry;
+            });
+            map.items = json(items);
+            break;
+        }
+        case 'action':
+            map.label = string(d.label, 'label', 100);
+            if (d.description !== undefined)
+                map.description = string(d.description, 'description');
+            break;
+        case 'report': {
+            const sections = list(d.sections, 'sections').map((raw, i) => {
+                const section = record(raw, `sections[${i}]`);
+                fields(section, ['heading', 'body'], `sections[${i}]`);
+                return {
+                    heading: string(section.heading, `sections[${i}].heading`, 200),
+                    body: string(section.body, `sections[${i}].body`),
+                };
+            });
+            map.sections = json(sections);
+            break;
+        }
+    }
+    return { cardParamMap: map };
+}

package/docs/API.md

@@ -1,5 +1,9 @@
 # API contracts checked 2026-10-24
 
+## Presentation Card Data Mode (v0.4.0 development)
+
+For Form input on Create & Deliver or Update, Card Data Mode `Presentation` accepts the v1 descriptor documented in [PRESENTATION.md](PRESENTATION.md) and produces existing `cardData.cardParamMap` string values. It is opt-in; Card Data Form/JSON and whole-body Input Mode JSON contracts are unchanged. This mode is a stateless adapter and does not ship templates, render components, route actions, or enforce status transitions.
+
 Primary documentation was fetched from current DingTalk documentation pages and their published backing content at `https://icms-document.oss-cn-beijing.aliyuncs.com/zh-CN/dingtalk/{namespace}/topics/{slug}.html`. The backing URL is how the current documentation frontend renders the body; it is not an application endpoint. That documentation check did not make authenticated calls; the later connected-instance live E2E is recorded below.
 
 | Purpose | Method and path on `https://api.dingtalk.com` | Verified contract |

package/docs/PRESENTATION.md

@@ -0,0 +1,87 @@
+# Presentation descriptor v1
+
+The Presentation Card Data Mode is a stateless adapter from a small, versioned descriptor to the existing Form-mode `cardData.cardParamMap` boundary. It does not render a card or verify DingTalk template components. The package does **not** ship DingTalk platform templates. Users must create, publish, and associate templates whose variables match the mappings below.
+
+## Contract
+
+Every descriptor is a JSON object with required `version: "1"`, `family`, `title`, and `tone`. `family` is one of `alert`, `status`, `digest`, `action`, or `report`. `title` is a non-empty string up to 200 characters. Optional `summary` is a non-empty string up to 1000 characters. Unknown fields are rejected at the descriptor and nested-object levels. Strings are not interpreted as HTML, code, or template fragments. No arbitrary colors, style values, or component trees are accepted.
+
+Semantic `tone` values are `neutral`, `info`, `success`, `warning`, and `danger`. They are labels for user-authored template logic, not colors imposed by this package. Templates may choose their own visual treatment for these tokens.
+
+All list families require 1–20 entries. Digest items have required `title` (up to 200 characters), optional `summary` (up to 1000), and optional `tone`. Report sections have required `heading` (up to 200) and `body` (up to 1000). Unknown fields or malformed entries fail validation. No external schema library is used.
+
+## Families and exact variable mapping
+
+Every family maps the 13 contract variables described below. Presentation mode also adds the AI-host compatibility field `flowStatus: "3"` to the public `cardParamMap`; it is not a descriptor field or part of the Presentation contract. This fixed value cannot be overridden by descriptor input. The current DingTalk AI Card builder templates (`type=im`, `schemaVersion=3.0.0`, `extendType=AI`) require completed-state `flowStatus` for `AICardContainer` to select its completed content branch. The 13 contract variables retain their existing meanings and encodings.
+
+Every family maps these contract entries:
+
+| Descriptor value | `cardParamMap` variable | Encoding |
+| --- | --- | --- |
+| Contract identity | `presentationVersion` = `"1"` | string |
+| `family` | `presentationFamily` | string |
+| `title` | `title` | string |
+| optional `summary` | `summary` | string, omitted when absent |
+| `tone` | `tone` | symbolic string |
+
+Family-specific fields:
+
+| Family | Descriptor fields | `cardParamMap` entries |
+| --- | --- | --- |
+| `alert` | optional `source` (200 chars), `occurredAt` (100 chars) | `source`, `occurredAt`, omitted when absent |
+| `status` | required `state`; optional `details` | `state`, optional `details` |
+| `digest` | required `items` array | `items` as compact JSON string |
+| `action` | required `label` (100 chars); optional `description` | `label`, optional `description` |
+| `report` | required `sections` array | `sections` as compact JSON string |
+
+The only status states are `idle`, `running`, `success`, `failed`, and `cancelled`. Digest and report objects serialize with stable field order as shown in the schema (`title`, `summary`, `tone`; and `heading`, `body`). All resulting values are strings, as required by the existing Card Data boundary. The mapper does not reorder list entries. Thus the payload contains 13 contract variables plus one AI-host compatibility field.
+
+### Template acceptance rule
+
+A successful DingTalk Create & Deliver response proves transport acceptance only. It does not prove that the selected template defines or binds the supplied variables, or that the card renders them. Accept the template contract after inspecting rendered-card evidence or template-definition/export evidence showing the required variables are defined and bound, together with live transport through the selected published template. This establishes template-contract acceptance; it does not by itself claim client pixel-perfect visual inspection.
+
+`Action` is presentation metadata only. `label` and `description` are display strings. They do not define a callback ID, route, authorization, executable action, or platform button. Workflow routing and callback contracts are outside this version.
+
+## Status and transitions
+
+The adapter is stateless: it validates one descriptor and maps it to one `cardData` value. It does not remember prior status or enforce transitions. As workflow guidance, a task may progress from `idle` to `running`, then to `success`, `failed`, or `cancelled`. A workflow may also update a terminal card later when its business process explicitly supports retry or correction. Choose and persist transition policy in the workflow layer; the enum only bounds presentation vocabulary.
+
+## Examples
+
+Runnable descriptor JSON files and their mapped card data are in [`examples/presentation`](../examples/presentation/).
+
+### Alert
+
+```json
+{"version":"1","family":"alert","title":"Database unavailable","summary":"Primary database health check failed.","tone":"danger","source":"health-check","occurredAt":"2026-10-25T08:30:00Z"}
+```
+
+### Status
+
+```json
+{"version":"1","family":"status","title":"Nightly backup","summary":"Archive upload is running.","tone":"info","state":"running","details":"12 of 40 GB uploaded"}
+```
+
+### Digest
+
+```json
+{"version":"1","family":"digest","title":"Engineering digest","tone":"neutral","items":[{"title":"Build passed","summary":"Main branch","tone":"success"}]}
+```
+
+### Action
+
+```json
+{"version":"1","family":"action","title":"Review deployment","tone":"warning","label":"Open deployment details","description":"Display metadata only; workflow behavior is configured separately."}
+```
+
+### Report
+
+```json
+{"version":"1","family":"report","title":"Daily operations","summary":"Three services checked.","tone":"success","sections":[{"heading":"Availability","body":"All monitored services responded."}]}
+```
+
+## Compatibility and boundaries
+
+Presentation mode is opt-in under Form input for Create & Deliver and Update. Its output is passed through the existing request builder. Existing Form parameters, Card Data JSON, whole-body Input Mode JSON, request construction, and output fields retain their behavior. The template ID is always user supplied for Create & Deliver; this package does not include or publish templates.
+
+This is an adapter, not a renderer or template registry. It does not claim support for specific DingTalk components or visual behavior. v0.5 normalized callback/action contracts and v0.6 controlled A2UI/component rendering are explicitly deferred. There is no executable action routing, arbitrary HTML/code, arbitrary styling, persistent state, or general component allowlist runtime in v1.

package/docs/ROADMAP.md

@@ -2,7 +2,9 @@
 
 This roadmap is subordinate to the project's [design baseline](DESIGN.md), which governs architecture, scope, non-goals, and acceptance boundaries. Roadmap items may sequence work within those boundaries but cannot override them; resolve conflicts by updating the proposal to fit the baseline or deliberately revising the baseline first.
 
-This roadmap starts from the published **v0.3.0-beta.1** state and records **v0.3.0 stable release preparation**. v0.3.0 becomes stable once published; until then, the beta remains the latest public package version. It describes intended milestones, not released capabilities. The current release and its tested limits remain documented in the [README](../README.md), [API contracts](API.md), and [verification record](VERIFICATION.md). Dates are omitted; milestones are semantic versions, not calendar commitments.
+This roadmap starts from the published **v0.3.0** stable state, with **v0.3.0-beta.1** retained as its prerelease. It describes intended milestones, not released capabilities. The current release and its tested limits remain documented in the [README](../README.md), [API contracts](API.md), and [verification record](VERIFICATION.md). Dates are omitted; milestones are semantic versions, not calendar commitments.
+
+The repository package version is **0.4.0-beta.1**, publicly published as a beta. npm `beta` resolves to `0.4.0-beta.1`; `latest` remains stable at `0.3.0`. The v0.4.0 Presentation Contract & Template Kit is implemented and accepted, including live use of a user-published contract template. The package ships no DingTalk templates. See [final template-contract acceptance](VERIFICATION.md#v040-beta1-final-presentation-template-contract-acceptance-2026-10-25).
 
 ## Vision and product principle
 
@@ -27,7 +29,7 @@ Descriptors produced with model assistance may be considered only after determin
 
 ## Milestones
 
-### v0.3.0 — stable release (acceptance closed; publication pending)
+### v0.3.0 — stable release (released)
 
 **Objective:** Close acceptance for the existing beta surface, remove the prerelease qualifier, and establish a reliable stable baseline. No major new product surface.
 
@@ -39,28 +41,30 @@ Descriptors produced with model assistance may be considered only after determin
 - Characterize repeated Create behavior with the same `outTrackId`; do not promise deduplication or upsert.
 - Regression coverage for existing v0.1/v0.2/v0.3 behavior and n8n UI install/update lifecycle acceptance.
 
-**Acceptance gates (closed for this stable release preparation):** Scoped live and local evidence is recorded in [verification](VERIFICATION.md#v030-stable-release-preparation--2026-10-24). Robot Direct Message and whole-body JSON lifecycles passed; a real v0.3 button callback reached the trigger and asynchronous Update succeeded; repeated Create with one caller-controlled `outTrackId` was accepted in the tested path without implying deduplication/upsert. A user-performed Community Nodes UI uninstall/reinstall restored package/manifest/installed-version consistency. Stable post-publication Update-button verification remains a separate follow-up.
+**Acceptance gates (closed):** Scoped live and local evidence, release provenance, canonical artifact digest and npm update-discovery evidence are recorded in [verification](VERIFICATION.md#v030-stable-release-2026-10-24). Robot Direct Message and whole-body JSON lifecycles passed; a real v0.3 button callback reached the trigger and asynchronous Update succeeded; repeated Create with one caller-controlled `outTrackId` was accepted in the tested path without implying deduplication/upsert. A user-performed Community Nodes UI uninstall/reinstall restored package/manifest/installed-version consistency. Stable upgrade remains a user-operated supported Community Nodes UI action; the isolated update-discovery check does not claim the UI button was clicked or observed.
 
 **Non-goals / deferrals:** No new card families, generalized interaction schema, A2UI renderer, business workflow suite, or broad DingTalk API coverage.
 
 **Compatibility and migration:** Preserve existing Form/JSON behavior, callback opt-in, output fields, and saved workflow behavior. Same-ID Create semantics remain explicitly non-guaranteed.
 
-### v0.4.0 — Presentation Contract & Template Kit
+### v0.4.0 — Presentation Contract & Template Kit (published beta; acceptance complete, ready for stable promotion)
 
 **Objective:** Define how workflows describe useful card presentations independently of a particular template.
 
-**Main deliverables:**
+**Main deliverables (implemented):**
 
-- Stable high-level presentation schema and example payloads/templates.
+- Versioned presentation schema, example payloads, and a template variable contract.
 - Alert, Status, Digest, Action, and Report card families.
 - Design tokens and visual hierarchy guidance, with card state transitions.
 - Low-level raw JSON mode retained for expert API use.
 
-**Acceptance gates:** Schema validation is deterministic; examples map clearly to documented DingTalk templates; required and optional values and state transitions are documented. Do not label a component supported until current official platform behavior is verified.
+The implementation is a deterministic stateless adapter to the existing Form-mode `cardData.cardParamMap` boundary. It does not ship DingTalk templates or claim verified component support. Status transition descriptions are workflow guidance only.
+
+**Acceptance gates (complete):** Local schema validation, family examples, mapping, compatibility, and workflow-only state guidance are documented and locally verified. Production UI installation, loaded schema, adapter/API transport, and compatibility with the existing lifecycle passed on n8n/runners 2.44.6. The dedicated template definition/export established all 13 contract variables as public strings statically bound in both `editorData` and `widgetInfo`; live published-template transport passed for all five families with required and optional fields populated. Five n8n executions succeeded, with top-level DingTalk `success=true` and `deliverResults[].success=true` in every response. This is sufficient under the documented rule to pass the template contract; client pixel-perfect visual inspection was not independently performed. The beta is ready for stable promotion; stable promotion is outside this milestone's completed work.
 
 **Non-goals / deferrals:** No arbitrary UI or HTML, no automatic template authoring, and no A2UI runtime in this milestone.
 
-**Compatibility and migration:** The contract is additive and versioned. Existing Form and whole-body JSON modes continue to work; no existing request body is silently reinterpreted.
+**Compatibility and migration:** The contract is additive and versioned. Existing Form and whole-body JSON modes continue to work; no existing request body is silently reinterpreted. The beta is published and production-installed through the supported UI. Transport, lifecycle, and Presentation template-contract acceptance are complete for the documented paths.
 
 ### v0.5.0 — Interaction Contract & Normalized Trigger
 

package/docs/VERIFICATION.md

@@ -1,8 +1,60 @@
 # Release verification record — 2026-10-24
 
-## v0.3.0 stable release preparation — 2026-10-24
+## v0.4.0-beta.2 real Mac DingTalk visual acceptance — 2026-10-25
 
-Package metadata is prepared as `0.3.0`. Stable acceptance for the existing v0.3 scope is closed pending publication. The earlier beta-era records below are historical; this section records the final stable-preparation evidence and supersedes their open/remaining v0.3 acceptance statements.
+Real Mac DingTalk visual acceptance passed with the user's published AI-card template when `flowStatus=3` was supplied. All 13 Presentation contract fields and the summary rendered. The Presentation adapter supplies the fixed public `flowStatus: "3"` compatibility field while retaining the 13 contract variables. No private template IDs or group/card identifiers are recorded.
+
+## v0.4.0-beta.1 publication and production preflight — 2026-10-25 (historical)
+
+The v0.4.0-beta.1 package is publicly published as a beta. This section records release identity and the read-only production preflight state at that time. Its production-upgrade and live-acceptance statements are superseded by the subsequent acceptance section below.
+
+- Tag `v0.4.0-beta.1` points to commit `3bb7e64c5a45aa78ba82ba1547c2e037e8f89655`. GitHub Actions publish run [40110742892](https://github.com/NTLx/n8n-nodes-dingtalk-card/actions/runs/40110742892) succeeded.
+- Public npm dist-tags are `beta -> 0.4.0-beta.1` and `latest -> 0.3.0`. Trusted Publisher/OIDC publication and provenance succeeded.
+- The canonical GitHub prerelease asset matches the public npm tarball: **54,776 bytes**, SHA-256 `d906cd7e69379841655cd2c562558cf75bff622e4284ca58e1b9680f232c8870`.
+- At the time of this preflight, no live DingTalk Presentation template acceptance had occurred. The package ships no DingTalk templates.
+
+### Connected-instance production preflight
+
+On 2026-10-25, connected production n8n and its runners were healthy on version **2.44.6**. At this preflight point the installed `n8n-nodes-dingtalk-card` was **0.3.0** and its live node schema exposed `cardDataMode` values `form` and `json` only. The official `/api/v1/community-packages` route existed and required authentication. No confirmed existing Public API credential with both `communityPackage:list` and `communityPackage:update` scopes was available on-host, and `N8N_COMMUNITY_PACKAGES` environment management was not configured.
+
+At that point the existing DingTalk Card E2E workflow used the earlier template-variable pattern; it was not evidence of v0.4 Presentation acceptance. Production upgrade and live template E2E were then pending. No private IDs or secrets are recorded here.
+
+## v0.4.0-beta.1 production install and connected-instance transport acceptance — 2026-10-25
+
+Production self-hosted n8n and runners were on **2.44.6**; healthz and readiness each returned HTTP 200. The package `n8n-nodes-dingtalk-card@0.4.0-beta.1` was installed through the supported Community Nodes UI lifecycle. The host package metadata confirmed `0.4.0-beta.1`. Live `get_node_types` exposed `cardDataMode='presentation'` and `presentationDescriptor`.
+
+Connected-instance live acceptance passed the following transport paths:
+
+- A valid status Presentation Update was applied to an existing test card; DingTalk Update returned success.
+- The existing draft E2E's Create & Deliver and Update steps were switched to Presentation mode. The run then completed its existing Streaming Update, Finalize, and final whole-body JSON Update; the complete live execution succeeded.
+
+This accepts the Presentation adapter mapping, DingTalk API transport, and compatibility with the legacy lifecycle on this connected instance. The E2E used the existing legacy public AI template solely for these purposes. That template does not satisfy the v0.4 `presentationVersion`/`presentationFamily`/`title`/`tone`/... variable contract documented in [PRESENTATION.md](PRESENTATION.md). Therefore no visual Presentation rendering or matching-template acceptance is claimed. Visual/template E2E remains pending until the user publishes a template matching that contract and runs it. The package ships no DingTalk templates.
+
+The preceding prepublication development verification remains historical and records local gates only; it makes no claim of production use at that earlier point. No real organization, group, card, credential, workflow, execution, or `outTrackId` identifiers are recorded.
+
+## v0.4.0-beta.1 live Presentation template-contract probe — 2026-10-25
+
+This probe records the earlier state and is superseded by the final acceptance record below.
+
+A user-published dedicated DingTalk test template was exercised with real Create & Deliver for all five Presentation families: `alert`, `status`, `digest`, `action`, and `report`. Each descriptor populated all common fields and every family-specific optional and required field. All five API Create & Deliver calls succeeded.
+
+A negative-control Create & Deliver using Card Data JSON with one deliberately unknown `cardParamMap` key also succeeded. This demonstrates that DingTalk API success does **not** prove a template defines or binds the supplied variables. Transport acceptance and template-variable binding/rendering acceptance are separate checks.
+
+Full visual/template-contract acceptance remains pending rendered-card evidence or template-definition/export evidence. No real template, group, card, workflow, execution, credential, or `outTrackId` identifiers are recorded.
+
+## v0.4.0-beta.1 final Presentation template-contract acceptance — 2026-10-25
+
+The Presentation mapper includes the fixed public AI-host compatibility value `flowStatus: "3"` in addition to the 13 Presentation contract variables. The current AI Card builder template configuration (`type=im`, `schemaVersion=3.0.0`, `extendType=AI`) needs completed-state `flowStatus` for `AICardContainer` to select its completed content branch. The descriptor schema and 13-variable contract remain unchanged. This host compatibility behavior is covered by local unit tests; it does not constitute visual acceptance of the user's template or client rendering.
+
+The dedicated test template was rebuilt from the user-exported DingTalk JSON as a compact `NORMAL` template with three logical components: one Grid and two BaseText components. Its 13/13 v0.4 contract variables are defined as public strings and statically bound in both `editorData` and `widgetInfo`. The user imported and published this template.
+
+Final live connected-instance acceptance sent all five Presentation families (`alert`, `status`, `digest`, `action`, and `report`) through the published template. Required and optional fields were populated for each family. All five n8n executions succeeded; every DingTalk response had top-level `success=true` and `deliverResults[].success=true`.
+
+Under the documented template acceptance rule, template-definition/export evidence together with live transport through the published template is sufficient to mark the Presentation template contract **PASS**. Client pixel-perfect visual inspection was not independently performed and is not claimed. This closes v0.4.0-beta.1 acceptance; the release is ready for stable promotion. No stable release was published or relabeled as part of this acceptance. No real template, group, card, workflow, execution, credential, or `outTrackId` identifiers are recorded.
+
+## v0.3.0 stable release — 2026-10-24
+
+Stable acceptance for the existing v0.3 scope is closed and the release is published. The earlier beta-era records below are historical; this section records the final stable-release evidence and supersedes their open/remaining v0.3 acceptance statements.
 
 On the connected n8n **2.44.5** instance, the following live paths passed:
 
@@ -12,13 +64,24 @@ On the connected n8n **2.44.5** instance, the following live paths passed:
 - A newly sent v0.3 interaction card received a real button click through the DingTalk Stream callback. DingTalk Card Trigger emitted the callback and downstream asynchronous Update succeeded; the temporary test listener was then unpublished.
 - A user-performed n8n Community Nodes UI uninstall/reinstall of `0.3.0-beta.1` restored DB/manifest/installed-package version consistency. This is supported lifecycle evidence; no internal database or Community Nodes directory was directly mutated for product acceptance.
 
-The separate stable post-publication Community Nodes Update-button verification remains pending until the stable package exists. v0.3.0 becomes stable when published. This evidence closes the v0.3.0 acceptance scope; it does not certify v1.0 or untested DingTalk templates, form interactions, reconnect and failure modes, or other n8n versions. No tag, GitHub release, or npm publication is part of this preparation.
+This evidence closes the v0.3.0 acceptance scope; it does not certify v1.0 or untested DingTalk templates, form interactions, reconnect and failure modes, or other n8n versions. Stable upgrade remains a user-operated supported Community Nodes UI action. No direct internal database or Community Nodes directory mutation was used as product acceptance.
+
+### Public release identity and artifact
+
+- Stable tag `v0.3.0` targets release commit `e1510c3b0e48b83d7bea9565c20c3c6ec536d17e`; tag CI run [40105981048](https://github.com/NTLx/n8n-nodes-dingtalk-card/actions/runs/40105981048) succeeded.
+- npm Trusted Publisher/OIDC publish run [40106100176](https://github.com/NTLx/n8n-nodes-dingtalk-card/actions/runs/40106100176), attempt 1, succeeded with provenance. npm `latest` resolves to `0.3.0`; `beta` remains `0.3.0-beta.1`.
+- Public stable GitHub Release: [v0.3.0](https://github.com/NTLx/n8n-nodes-dingtalk-card/releases/tag/v0.3.0), published (`draft=false`, `prerelease=false`), with exactly one asset matching the canonical public npm tarball bytes and digest.
+- Canonical `n8n-nodes-dingtalk-card-0.3.0.tgz`: **48,313 bytes**; SHA-256 `f0776ea697f29cde5b0fe2f7b2b5574f3d029b161ee2a3c348174b1fc3f61972`; SHA-1 `c94da00b74e0af6274796b0e4242f1a457f14f8b`; SHA-512 `f47293ebe7c8c48e23cff5f86e68e3b7cf7dccba1e26c1c59c20ba40f155ba1aea60c153985d814a3f6e40ab43ad62b78f7516f8ea18da89acdc3d56624e8149`; npm integrity `sha512-9HKT6+fIxI4jz/X4bmjjt899zLoeJsHFnCC6QPFVuhrqYMFTmF2BSj9uQKtDrWK3j3UW+OoY2oms3D1WYk6BSQ==`.
+
+### Update-discovery evidence
 
-Local release gates passed on **Node 26.12.1 / npm 12.2.1**: clean `npm ci`; lint; typecheck; build; **56 tests passed / 0 failed / 0 skipped**; `verify:package` including standalone extracted class registration (**20 allowlisted files**); `npm audit --omit=dev --audit-level=high` (**0 production vulnerabilities**); and `git diff --check`. The clean install reports the existing development-tree advisories (**19 high, 4 moderate**), deprecations and five blocked install scripts; install completed successfully. These development advisories are outside the production package audit and were not changed as part of this release preparation.
+In a disposable `/tmp` package project using `https://registry.npmjs.org/`, `n8n-nodes-dingtalk-card` was installed with an exact `0.3.0-beta.1` dependency and `npm outdated --json` reported `current: 0.3.0-beta.1`, `wanted: 0.3.0-beta.1`, and `latest: 0.3.0`. The temporary project was removed. This confirms npm update discovery exposes stable as the latest version for that pinned beta install. It is not evidence that the n8n Community Nodes UI Update button was clicked or observed, and it did not access production n8n. The stable upgrade remains a user-operated supported Community Nodes UI action.
 
-`npm pack --ignore-scripts --json` produced `n8n-nodes-dingtalk-card-0.3.0.tgz` with **20 files** (48,024 compressed bytes): package metadata, README, changelog, license, compiled nodes/credential and icons, API/design/roadmap/verification docs, and five examples. The packed manifest version is `0.3.0`; no tests, source files, or unrelated repository files are included. Package verification and this tarball inspection are local; public registry metadata, provenance and tarball checks run in the publish workflow after a separately authorized publication.
+Local release gates passed on **Node 26.12.1 / npm 12.2.1**: clean `npm ci`; lint; typecheck; build; **56 tests passed / 0 failed / 0 skipped**; `verify:package` including standalone extracted class registration (**20 allowlisted files**); `npm audit --omit=dev --audit-level=high` (**0 production vulnerabilities**); and `git diff --check`. The clean install reports the existing development-tree advisories (**19 high, 4 moderate**), deprecations and five blocked install scripts; install completed successfully. These development advisories are outside the production package audit and were not changed as part of this release. These are prepublication gate results; the final public identity and digest are recorded above.
 
-The GitHub CI workflow runs the same install/lint/typecheck/build/test/package/audit gates on Node 24 for branch pushes, pull requests and tags. The npm workflow remains manually dispatched and grants only `id-token: write` for Trusted Publisher/OIDC provenance; no npm token or secret is added. Stable `v0.3.0` publishes with `latest`; beta versions publish with `beta` and may synchronize `latest` only while npm reports no stable version. Tag/version checks are exact. No tag, GitHub release, publish dispatch or npm publication was created in this preparation.
+The prepublication `npm pack --ignore-scripts --json` inspection found **20 files** in the candidate tarball (48,024 compressed bytes): package metadata, README, changelog, license, compiled nodes/credential and icons, API/design/roadmap/verification docs, and five examples. The packed manifest version was `0.3.0`; no tests, source files, or unrelated repository files were included. This candidate inspection is historical; public registry metadata, provenance and canonical tarball identity are recorded above.
+
+The GitHub CI workflow runs the same install/lint/typecheck/build/test/package/audit gates on Node 24 for branch pushes, pull requests and tags. The npm workflow grants only `id-token: write` for Trusted Publisher/OIDC provenance; no npm token or secret is added. Stable `v0.3.0` publishes with `latest`; beta versions publish with `beta` and may synchronize `latest` only while npm reports no stable version. Tag/version checks are exact. This describes the release process; the completed tag, workflow runs, GitHub Release and npm publication are identified above.
 
 ## v0.3.0-beta.1 release preparation — local verification (historical)
 
@@ -201,3 +264,8 @@ The maintainer supplied the following successful real DingTalk E2E result for do
 This validates the tested request-button callback path and immediate receipt ACK transport with asynchronous downstream execution in practice. It does not certify every template, form submission, reconnect or failure mode, establish exactly-once delivery, or add synchronous local-update ACK support. No measured ACK latency or untested recovery behavior is claimed.
 
 Only the non-sensitive result is recorded. No private organization/group/robot/user/workflow/execution identifiers, message IDs, tracking IDs, corp IDs, actual callback values or secrets are included. This closure makes no new live calls and changes only repository documentation and existing GitHub prerelease notes. The annotated tag, tagged source, package version/lockfile, release asset and npm publication remain unchanged; the immutable archive's bundled documentation predates this post-release record.
+# v0.4.0-beta.1 prepublication development verification — 2026-10-25 (historical)
+
+This records local verification before publication; its unpublished status describes that point in time only. Current publication and production preflight status is recorded in [the post-release section above](#v040-beta1-publication-and-production-preflight-2026-10-25). The v0.4.0 Presentation Contract & Template Kit was implemented. Package metadata was `0.4.0-beta.1`; release preparation allowed v0.4.0 beta tags under the established beta channel and validated exact package version/tag matches; the stable `v0.3.0` guard remained the only `latest` publish path. On the repository's configured Node/npm environment, release gates passed: clean `npm ci`; `npm run lint`; `npm run typecheck`; `npm run build`; `npm test` (**60 passed, 0 failed**); `npm run verify:package` (standalone packed class loading/registration passed; **27 allowlisted files**); `npm audit --omit=dev --audit-level=high` (**0 production vulnerabilities**); release-ref policy self-tests; YAML and inline Node.js syntax validation; and `git diff --check`. The clean install reported 23 total dependency advisories across development and production dependencies.
+
+Tests covered all five descriptor families, deterministic string mapping, contract identity fields, unknown versions/families/fields, wrong types, missing fields, invalid status values, collection bounds, and Create & Deliver/Update node mapping. Existing test coverage remained passing. No DingTalk credentials or live template were used. At prepublication verification time, no template rendering, live acceptance, npm publication, Git tag/release, or external-system mutation was claimed. The package contains no DingTalk platform templates; users must publish templates matching the documented variables.

package/examples/presentation/action.json

@@ -0,0 +1,4 @@
+{
+  "descriptor": {"version":"1","family":"action","title":"Review deployment","tone":"warning","label":"Open deployment details","description":"Display metadata only; configure workflow behavior separately."},
+  "cardData": {"cardParamMap":{"presentationVersion":"1","presentationFamily":"action","title":"Review deployment","tone":"warning","label":"Open deployment details","description":"Display metadata only; configure workflow behavior separately."}}
+}

package/examples/presentation/alert.json

@@ -0,0 +1,4 @@
+{
+  "descriptor": {"version":"1","family":"alert","title":"Disk full","summary":"Storage is above the configured threshold.","tone":"danger","source":"disk-monitor","occurredAt":"2026-10-25T08:30:00Z"},
+  "cardData": {"cardParamMap":{"presentationVersion":"1","presentationFamily":"alert","title":"Disk full","summary":"Storage is above the configured threshold.","tone":"danger","source":"disk-monitor","occurredAt":"2026-10-25T08:30:00Z"}}
+}

package/examples/presentation/digest.json

@@ -0,0 +1,4 @@
+{
+  "descriptor": {"version":"1","family":"digest","title":"Engineering digest","tone":"neutral","items":[{"title":"Build passed","summary":"Main branch","tone":"success"},{"title":"Deploy pending","tone":"warning"}]},
+  "cardData": {"cardParamMap":{"presentationVersion":"1","presentationFamily":"digest","title":"Engineering digest","tone":"neutral","items":"[{\"title\":\"Build passed\",\"summary\":\"Main branch\",\"tone\":\"success\"},{\"title\":\"Deploy pending\",\"tone\":\"warning\"}]"}}
+}

package/examples/presentation/report.json

@@ -0,0 +1,4 @@
+{
+  "descriptor": {"version":"1","family":"report","title":"Daily operations","summary":"Three services checked.","tone":"success","sections":[{"heading":"Availability","body":"All monitored services responded."},{"heading":"Follow-up","body":"Review the weekly maintenance window."}]},
+  "cardData": {"cardParamMap":{"presentationVersion":"1","presentationFamily":"report","title":"Daily operations","summary":"Three services checked.","tone":"success","sections":"[{\"heading\":\"Availability\",\"body\":\"All monitored services responded.\"},{\"heading\":\"Follow-up\",\"body\":\"Review the weekly maintenance window.\"}]"}}
+}

package/examples/presentation/status.json

@@ -0,0 +1,4 @@
+{
+  "descriptor": {"version":"1","family":"status","title":"Nightly backup","summary":"Archive upload is running.","tone":"info","state":"running","details":"12 of 40 GB uploaded"},
+  "cardData": {"cardParamMap":{"presentationVersion":"1","presentationFamily":"status","title":"Nightly backup","summary":"Archive upload is running.","tone":"info","state":"running","details":"12 of 40 GB uploaded"}}
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "n8n-nodes-dingtalk-card",
-  "version": "0.3.0",
+  "version": "0.4.0-beta.2",
   "description": "DingTalk Card Platform lifecycle nodes for n8n",
   "license": "MIT",
   "homepage": "https://github.com/NTLx/n8n-nodes-dingtalk-card#readme",