@sparkerp/plugin-sdk 0.1.0

package/bundle/docs/recipes/kpi-dashboard-page.md

@@ -0,0 +1,92 @@
+---
+title: A KPI dashboard page
+audience: tenant
+---
+
+# A KPI dashboard page
+
+## When you need this
+
+A page (or the top of a list page) showing several headline numbers computed
+server-side, fetched in **one** call, refreshed after writes.
+
+## The pieces
+
+### One `count` Data Service per metric
+
+```json
+{
+  "name": "oeq-equipment-count-available",
+  "definition": {
+    "operation": "count",
+    "source": { "kind": "entity", "entityName": "oeq_equipment" },
+    "filters": [ { "field": "status", "operator": "eq", "value": "AVAILABLE" } ],
+    "parameters": []
+  }
+}
+```
+
+### One `composite` Data Service wrapping them
+
+`metadata/data_service/oeq-equipment-kpis.json`
+([real file](../tutorial/example-plugin/spk-assembly/metadata/data_service/oeq-equipment-kpis.json)):
+
+```json
+{
+  "name": "oeq-equipment-kpis",
+  "definition": {
+    "operation": "composite",
+    "source": { "kind": "entity", "entityName": "oeq_equipment" },
+    "steps": [
+      { "as": "total",     "service": "oeq-equipment-count-total",     "parameters": {} },
+      { "as": "available", "service": "oeq-equipment-count-available", "parameters": {} },
+      { "as": "assigned",  "service": "oeq-equipment-count-assigned",  "parameters": {} }
+    ]
+  }
+}
+```
+
+### The page mount loader
+
+```json
+"events": { "mounted": { "source": "action-chain", "actions": [
+  { "id": "a0", "order": 0, "type": "callApi",
+    "config": { "connectionRef": "self", "path": "/api/v1/data-services/oeq-equipment-kpis/execute", "httpMethod": "POST", "params": {} }, "output": "kpi" },
+  { "id": "a1", "order": 1, "type": "setValue", "config": { "field": "page.kpiTotal",     "value": "${kpi.results.total.value}" } },
+  { "id": "a2", "order": 2, "type": "setValue", "config": { "field": "page.kpiAvailable", "value": "${kpi.results.available.value}" } },
+  { "id": "a3", "order": 3, "type": "setValue", "config": { "field": "page.kpiAssigned",  "value": "${kpi.results.assigned.value}" } }
+] } }
+```
+
+### The cards
+
+```json
+{
+  "blockType": "core.kpi-card",
+  "properties": {
+    "value": { "source": "binding", "binding": { "scope": "page", "key": "kpiTotal" } },
+    "labelKey": { "source": "static", "value": "office-equipment.equipment-register.kpi.total" },
+    "format": { "source": "static", "value": "number" },
+    "colorToken": { "source": "static", "value": "primary" }
+  }
+}
+```
+
+## The rule that bites
+
+`count` → `${out.value}`. `composite` → **`${out.results.<step>.value}`**. Never
+`.total` (that's the unrelated list-pagination envelope).
+
+Real response from the tutorial:
+
+```json
+{ "results": { "total": { "value": 0 }, "available": { "value": 0 }, "assigned": { "value": 0 } } }
+```
+
+To refresh after a write, append the same `callApi` + `setValue` steps to the
+Save action chain.
+
+## Related
+
+- [Add a KPI or aggregation](../guides/add-a-kpi.md)
+- [A cross-row aggregation into a summary entity](./cross-row-aggregation.md) — for numbers stored *back* into a table

package/bundle/docs/recipes/master-detail-page.md

@@ -0,0 +1,84 @@
+---
+title: A master-detail page with a child grid
+audience: tenant
+---
+
+# A master-detail page with a child grid
+
+## When you need this
+
+A list where clicking a row opens a panel showing that record **plus** a list of
+its children — a category and its equipment types, a maintenance record and its
+line items, a checkout and its history.
+
+## The shape
+
+1. **The master grid** — a normal `core.grid` wired via `metadata.dataSource`.
+2. **`rowClicked`** on the grid runs an action chain that:
+   - fetches the master record → `page.detailRecord`;
+   - calls a **parameterized Data Service** for the children, passing the master
+     id → `page.childItems`;
+   - opens `page.detailDialogOpen`.
+3. **A `core.dialog`** bound to `page.detailDialogOpen` containing an overview
+   card bound to `page.detailRecord.*` and a `core.list` (or nested `core.grid`)
+   bound to `page.childItems`.
+
+## The `rowClicked` chain
+
+```json
+"events": { "rowClicked": { "source": "action-chain", "actions": [
+  { "id": "a0", "order": 0, "type": "callApi",
+    "config": { "connectionRef": "self", "path": "/api/v1/entities/oeq_category/records/${event.id}", "httpMethod": "GET", "params": {} },
+    "output": "detail" },
+  { "id": "a1", "order": 1, "type": "setValue", "config": { "field": "page.detailRecord", "value": "${detail}" } },
+  { "id": "a2", "order": 2, "type": "callApi",
+    "config": { "connectionRef": "self", "path": "/api/v1/data-services/oeq-type-list/execute", "httpMethod": "POST",
+      "params": { "parameters": { "parentId": "${event.id}" } } },
+    "output": "children" },
+  { "id": "a3", "order": 3, "type": "setValue", "config": { "field": "page.childItems", "value": "${children.rows}" } },
+  { "id": "a4", "order": 4, "type": "setValue", "config": { "field": "page.detailDialogOpen", "value": true } }
+] } }
+```
+
+## The child Data Service
+
+```json
+{
+  "name": "oeq-type-list",
+  "definition": {
+    "operation": "search",
+    "source": { "kind": "entity", "entityName": "oeq_type" },
+    "filters": [ { "field": "category_id", "operator": "eq", "value": "${param.parentId}" } ],
+    "parameters": [ { "name": "parentId", "type": "string" } ]
+  }
+}
+```
+
+## The child list block
+
+```json
+{
+  "blockType": "core.list",
+  "properties": {
+    "items": { "source": "binding", "binding": { "scope": "page", "key": "childItems" } },
+    "primaryPath": { "source": "static", "value": "name" },
+    "secondaryPath": { "source": "static", "value": "code" }
+  }
+}
+```
+
+## The rules that bite
+
+- **`${event.id}`** is the clicked master row's id — available in `rowClicked`.
+- A parameterized Data Service is called with args nested under
+  **`parameters`**: `{ "params": { "parameters": { "parentId": "..." } } }`.
+- Bind the child list to `${children.rows}` (or `.items` / `.records` — check
+  the service's response envelope).
+- To let the panel **add** a child, put a small form + "Add" button in the same
+  dialog whose chain `POST`s to the child entity then re-runs the child Data
+  Service. The tutorial's Equipment Catalog page does exactly this.
+
+## Related
+
+- [Build a page](../guides/build-a-page.md)
+- [Add a data provider, data view, or data service](../guides/add-a-data-provider.md)

package/bundle/docs/recipes/n-days-before-reminder.md

@@ -0,0 +1,72 @@
+---
+title: An N-days-before reminder job
+audience: tenant
+---
+
+# An N-days-before reminder job
+
+## When you need this
+
+"Remind me N days before `<date>`." Warranty expiring in 30 days, an audit due in
+7, a checkout due back in 3. Zero Java — one `entity_status_date_sweep_config`
+row with `day_offset` set, shipped as seed data.
+
+## The file
+
+`metadata/seed-data/office-equipment-sweep-configs.json`
+([real file](../tutorial/example-plugin/spk-assembly/metadata/seed-data/office-equipment-sweep-configs.json)):
+
+```json
+{
+  "entity": "entity_status_date_sweep_config",
+  "keyFields": ["entity_name", "date_field", "set_status_to", "day_offset"],
+  "source": "office-equipment",
+  "rows": [
+    {
+      "entity_name": "oeq_checkout",
+      "status_field": "status",
+      "when_status_in": "CHECKED_OUT",
+      "date_field": "due_date",
+      "compare_op": "lte",
+      "day_offset": 3,
+      "set_status_to": "DUE_SOON",
+      "active": true,
+      "seeded_by": "office-equipment"
+    }
+  ]
+}
+```
+
+## How to read it
+
+`compare_op: "lte"` + `day_offset: 3` → the job fires for a `CHECKED_OUT`
+checkout whose `due_date` is **on or before `now + 3 days`** — i.e. "within 3
+days of due". `day_offset: 30` = "within 30 days". `day_offset: 0` (the default)
+= "the date has already passed".
+
+Use a **distinct target status per window** if you want 30/14/7-day reminders
+that are independently queryable — e.g. `DUE_IN_30`, `DUE_IN_14`, `DUE_SOON`.
+
+## The rules that bite
+
+- **Flip a status value, not a boolean flag.** The generic job passes
+  `set_status_to` as a string; writing `"true"` to a boolean column fails.
+- Include `day_offset` in `keyFields` so a 30-day and a 7-day rule for the same
+  date column are distinct on re-install.
+- Also ship `metadata/entities/entity_status_date_sweep_config.json` (additive
+  fields only). The job auto-registers on the first seeded row via a
+  platform-shipped rule — you don't ship a register rule for *this* job.
+
+## Verified
+
+```bash
+$ erp api post "/api/v1/jobs/engine-entity.status-date-sweep/execute" --body "{}"
+{ "executionId": 534 }
+$ erp api get "/api/v1/entities/oeq_checkout/records/2"
+{ "checkout_number": "CO-100", "status": "OVERDUE" }   # was CHECKED_OUT, due_date in the past
+```
+
+## Related
+
+- [Add a scheduled reminder job](../guides/add-a-reminder-job.md)
+- Tutorial chapter 7: [the return-due reminder job](../tutorial/07-return-due-reminder-job.md)

package/bundle/docs/recipes/per-row-document-generator.md

@@ -0,0 +1,65 @@
+---
+title: A per-row document artifact generator
+audience: tenant
+---
+
+# A per-row document artifact generator
+
+## When you need this
+
+"Generate a document per completed record and stash the file" — an audit report
+per finished audit, a handover certificate per completed checkout. Zero Java —
+one `entity_document_generator_config` row run by
+`engine-entity.document-generator`.
+
+## The file
+
+`metadata/seed-data/office-equipment-document-configs.json`:
+
+```json
+{
+  "entity": "entity_document_generator_config",
+  "keyFields": ["document_code"],
+  "source": "office-equipment",
+  "rows": [
+    {
+      "document_code": "equipment-audit-report",
+      "source_entity": "oeq_audit",
+      "when_status_in": "COMPLETED",
+      "target_file_field": "report_file_ref_id",
+      "format": "json",
+      "cabinet_id": 42,
+      "child_entity": "oeq_audit_item",
+      "child_match_field": "audit_id",
+      "file_name_template": "equipment-audit-${id}-${date}.json",
+      "active": true
+    }
+  ]
+}
+```
+
+## How to read it
+
+For each `oeq_audit` in status `COMPLETED` that doesn't already have a file
+reference in `report_file_ref_id` (a **text** column — its non-blank state is the
+dedupe marker), the job builds a structured document from the audit row plus its
+`oeq_audit_item` children, stores it in DMS cabinet `42`, and writes the file id
+back into `report_file_ref_id`.
+
+## The limitation to know
+
+The platform's PDF render path only renders synthetic sample data via the Studio
+app — it can't be driven headless against a real record. So this job emits a
+**structured-data artifact** (`json` or `csv`), not a rendered PDF.
+`template_ref` is reserved for when real-record binding ships.
+
+## Also ship
+
+- `cabinet_id` must be a real DMS cabinet id in your tenant.
+- The shared `entity_document_generator_config.json` (additive) and an
+  `AFTER_CREATE` register rule calling
+  `ensureEntityDocumentGeneratorJobRegistered`.
+
+## Related
+
+- `erp examples patterns --kind jobs` → `per-row-document-artifact-generation`

package/bundle/docs/recipes/related-record-lookup-field.md

@@ -0,0 +1,74 @@
+---
+title: A searchable related-record lookup field
+audience: tenant
+---
+
+# A searchable related-record lookup field
+
+## When you need this
+
+Any form field whose value is another entity's id — `category_id`,
+`equipment_id`, `employee_id`. Use a `core.lookup` block, never a plain text or
+number input that makes the user type a raw id. (An entire module built by AI
+agents once shipped every FK as a bare number input because this pattern was
+undiscoverable.)
+
+## The three files
+
+### 1. A Data View producing `{ value, label }`
+
+`metadata/data_view/oeq-category-select-options-view.json`
+([real file](../tutorial/example-plugin/spk-assembly/metadata/data_view/oeq-category-select-options-view.json)) —
+selects `t.id AS value` and a concatenated label. The output columns **must** be
+named `value` and `label`.
+
+### 2. A `search` Data Service over that view
+
+`metadata/data_service/oeq-category-search.json`
+([real file](../tutorial/example-plugin/spk-assembly/metadata/data_service/oeq-category-search.json)):
+
+```json
+{
+  "name": "oeq-category-search",
+  "definition": {
+    "operation": "search",
+    "source": { "kind": "dataView", "dataViewName": "oeq-category-select-options-view" },
+    "filters": [ { "field": "t.category_name", "operator": "contains", "value": "${param.search}" } ],
+    "parameters": [ { "name": "search", "type": "string" } ]
+  }
+}
+```
+
+### 3. The `core.lookup` block on the page
+
+```json
+{
+  "blockType": "core.lookup",
+  "properties": {
+    "value": { "source": "binding", "binding": { "scope": "page", "key": "formCategoryId" } },
+    "recordType": { "source": "static", "value": "OeqCategory" },
+    "optionsSourceKey": { "source": "static", "value": "oeq-category-search" }
+  },
+  "events": { "committed": { "source": "action-chain", "actions": [
+    { "id": "a0", "order": 0, "type": "setValue",
+      "config": { "field": "page.formCategoryId", "value": "${event.new}" } }
+  ] } }
+}
+```
+
+## The rules
+
+- `optionsSourceKey` = the `name` of the `search` Data Service. This is the real
+  wiring.
+- `recordType` = a documentation-only label; it doesn't route anything.
+- `committed` fires with **`event.new`** = the picked record's **id**. Not
+  `event.value`, not the label.
+- If the target entity has no search-shaped Data Service yet, build files 1 and 2
+  first — don't fall back to a text input.
+- For a small, static option set, `core.select` with inline `options` is simpler
+  and needs none of this.
+
+## Related
+
+- [Add a create / edit form](../guides/add-a-create-edit-form.md)
+- [A resolved reference column in a grid](./resolved-reference-grid-column.md)

package/bundle/docs/recipes/resolved-reference-grid-column.md

@@ -0,0 +1,63 @@
+---
+title: A resolved reference column in a grid
+audience: tenant
+---
+
+# A resolved reference column in a grid
+
+## When you need this
+
+A grid column (or a detail-view field) that should show a person's or record's
+**name**, but the entity only stores the **id**. Don't bind the raw `*_id` — bind
+the automatically-resolved `*_id_label` sibling.
+
+## The one line on the entity field
+
+```json
+{
+  "fieldName": "employee_id",
+  "label": "\"Employee Id\"",
+  "dataType": "long",
+  "flags": "{\"reference\":{\"entityType\":\"Employee\"}}"
+}
+```
+
+That `flags` string turns on id → display-name resolution platform-wide. From
+then on, **every** read of the entity —
+`GET .../records/query` (the grid) and `GET .../records/{id}` (single record) —
+gains a sibling key `employee_id_label`, resolved in one batched call per page
+load, not per row.
+
+**Verified live** in the tutorial:
+
+```bash
+$ erp api post "/api/v1/entities/oeq_checkout/records" --body '{"...":"...","employee_id":1,"...":"..."}'
+{ "id": 1, "employee_id": 1, "employee_id_label": "Aria Chen", ... }
+```
+
+## The grid column
+
+```json
+{ "name": "employee_id_label", "type": "string",
+  "headerKey": "office-equipment.equipment-checkout.column.employee" }
+```
+
+Bind `employee_id_label`, not `employee_id`.
+
+## The rules
+
+- `entityType` must be a **registered** provider — one that exposes a
+  `batch-names` endpoint. `"Employee"` (backed by the HCM employee plugin) is the
+  only one shipped today. An unregistered `entityType` simply produces no
+  `_label` key — no error.
+- For a foreign key to **your own** entity (no registered provider), denormalize
+  instead: store `category_name` next to `category_id` and write both on create.
+  That's what the tutorial's `oeq_equipment` does.
+- You can add the flag to a field after the fact via
+  `PUT /api/v1/entities/{id}/fields/{fieldId}` — the `_label` key appears on the
+  next read.
+
+## Related
+
+- [Add an entity](../guides/add-an-entity.md)
+- [A searchable related-record lookup field](./related-record-lookup-field.md)

package/bundle/docs/recipes/scheduled-record-generation.md

@@ -0,0 +1,68 @@
+---
+title: A scheduled record-generation cadence
+audience: tenant
+---
+
+# A scheduled record-generation cadence
+
+## When you need this
+
+"Create new records on a schedule." A quarterly audit, a monthly review, a
+follow-up task per due row. Zero Java — one `entity_cadence_config` row run by
+`engine-entity.cadence-generator`.
+
+## Standalone mode — one record per interval
+
+`metadata/seed-data/office-equipment-cadence-configs.json`
+([real file](../examples/standalone-plugin/spk-assembly/metadata/seed-data/office-equipment-cadence-configs.json)):
+
+```json
+{
+  "entity": "entity_cadence_config",
+  "keyFields": ["cadence_code"],
+  "source": "office-equipment",
+  "rows": [
+    {
+      "cadence_code": "equipment-audit-schedule",
+      "target_entity": "oeq_audit",
+      "interval_days": 90,
+      "dedupe_target_field": "cadence_marker",
+      "template_json": {
+        "audit_number": "AUDIT-${date}-${ts}",
+        "audit_name": "Scheduled Equipment Audit ${date}",
+        "status": "DRAFT"
+      },
+      "active": true
+    }
+  ]
+}
+```
+
+Every 90 days (tracked via `last_generated_at`) one `oeq_audit` row is created
+from `template_json`. String substitutions: `${date}`, `${ts}`, `${uuid}`.
+
+## Source-driven mode — one record per due source row
+
+Add:
+
+```json
+"source_entity": "oeq_equipment",
+"source_date_field": "warranty_expiry_date",
+"due_within_days": 30,
+"field_map_json": { "equipment_id": "id", "equipment_tag": "asset_tag" },
+"dedupe_target_field": "equipment_id"
+```
+
+→ for every `oeq_equipment` whose warranty expires within 30 days and which
+doesn't already have a generated row (deduped on `equipment_id`), create one,
+copying the mapped fields. `${sourceId}` is available in `template_json`.
+
+## Also ship
+
+- the target entity, the shared `entity_cadence_config.json` (additive), and
+- `metadata/rules/ensure_cadence_generator_job_registered.json`
+  (`AFTER_CREATE` → `ensureEntityCadenceGeneratorJobRegistered`).
+
+## Related
+
+- [Add a cadence-generator job](../guides/add-a-cadence-job.md)

package/bundle/docs/reference/action.md

@@ -0,0 +1,18 @@
+---
+title: action schema
+audience: tenant
+generated: true
+---
+
+# `action` schema
+
+A page-JSON/UI action-chain definition (frontend action engine — distinct from the server-side Action Engine, see ai/patterns/action-engine-server-side.md).
+
+Pull the full JSON Schema: `erp schema pull action`  ·  MCP: `erp_get_schema {"name":"action"}`
+
+_This schema's root is not a plain object (see the full schema for its shape)._
+
+## Named sub-definitions
+
+`actionDefinition`, `retryPolicy`, `errorStrategy`
+

package/bundle/docs/reference/block-definition.md

@@ -0,0 +1,35 @@
+---
+title: block-definition schema
+audience: tenant
+generated: true
+---
+
+# `block-definition` schema
+
+A block TYPE's own declared property/event contract (what core.grid, core.container, etc. accept).
+
+Pull the full JSON Schema: `erp schema pull block-definition`  ·  MCP: `erp_get_schema {"name":"block-definition"}`
+
+## Top-level properties
+
+| Property | Type | Required | Notes |
+| --- | --- | --- | --- |
+| `contractVersion` | — | yes |  |
+| `type` | string | yes | Globally unique block-type id, dot-namespaced (e.g. core.text-input, acme-hr.org-chart). |
+| `version` | string | yes | Semver. Instances pin the version they were authored against; minor/patch upgrades apply automatically, major upgrades require an explicit migration (W1-05). |
+| `publisher` | string | yes | The Phase 21 marketplace publisher id. |
+| `inputClass` | boolean |  | True for input-class blocks: the block inherits the validation-message surface (invalid state + message slot + aria-invalid/aria-describedby) from the base contract, which Phase 6's validation pipeline populates (round 2). |
+| `properties` | array | yes |  |
+| `inputs` | array |  |  |
+| `outputs` | array |  |  |
+| `events` | array | yes |  |
+| `permissions` | object | yes | Which permission hook points the block honors (W2-05). Enforcement lands in Phase 11; the hooks are in the render path from day one. |
+| `a11y` | object | yes |  |
+| `designer` | object | yes | Block-level designer metadata: what Phase 10's palette and property panel render for a block they have never seen (gap audit). |
+| `slots` | array |  | Container-class blocks only: named child slots and what they may contain. |
+| `composition` | array |  | 2026-07-18: present only on tenant-authored composite Block definitions (Studio's Block Designer) - the block's own fixed internal content, an array of frozen @erp/block-engine BlockInstanceConfig, validated against the live BlockRegistry at mount time exactly like a page item's or a container's own children. undefined for every core/plugin block. |
+
+## Named sub-definitions
+
+`identifier`, `i18nKey`, `propertyType`, `valueSourceKind`, `selectOption`, `propertySpec`, `portSpec`, `eventSpec`
+

package/bundle/docs/reference/block-instance.md

@@ -0,0 +1,33 @@
+---
+title: block-instance schema
+audience: tenant
+generated: true
+---
+
+# `block-instance` schema
+
+One block INSTANCE inside a page (instanceId/blockType/properties/events) — same shape validate-page-properties.mjs checks.
+
+Pull the full JSON Schema: `erp schema pull block-instance`  ·  MCP: `erp_get_schema {"name":"block-instance"}`
+
+## Top-level properties
+
+| Property | Type | Required | Notes |
+| --- | --- | --- | --- |
+| `contractVersion` | — | yes |  |
+| `instanceId` | string | yes | The block's instance identity - also its Phase 4 block-scope scopeKey. |
+| `blockType` | string | yes |  |
+| `blockVersion` | string | yes | The version this instance was authored against (the pin, W1-05). |
+| `properties` | object | yes |  |
+| `events` | object |  |  |
+| `outputs` | object |  | Optional output redirection: where each output port writes. Defaults to the block's own block-scope entry named after the port. |
+| `children` | object |  | Container-class blocks only: slot name to nested instance configs. |
+| `a11yLabelKey` | string |  | W10 (additive, 2026-07-16): the authored label's translation key for this placed instance (a Phase 6 field's labelKey), resolved through the runtime i18n resolver into the node's accessible name; takes precedence over the block definition's labelFrom default. |
+| `name` | string |  | 2026-07-18: an author-facing display name (e.g. "Header block"), never read at render/runtime — a Studio authoring aid only. |
+| `className` | string |  | 2026-07-17: a framework-specific class name applied to the rendered root, the universal escape hatch alongside style. |
+| `style` | object |  | 2026-07-17: raw inline style properties applied to the rendered root, the universal escape hatch alongside className. |
+
+## Named sub-definitions
+
+`boundKey`, `propertyValue`, `eventWiring`
+

package/bundle/docs/reference/composite-pack-manifest.md

@@ -0,0 +1,33 @@
+---
+title: composite-pack-manifest schema
+audience: tenant
+generated: true
+---
+
+# `composite-pack-manifest` schema
+
+The newer composite-pack / Country-or-Industry-Pack / Code-Plugin-style manifest contract (contractVersion/publisher/distribution/12 extension-point contributions) — a genuinely different artifact type from an ordinary .spk plugin.json (use 'plugin-manifest' for that).
+
+Pull the full JSON Schema: `erp schema pull composite-pack-manifest`  ·  MCP: `erp_get_schema {"name":"composite-pack-manifest"}`
+
+## Top-level properties
+
+| Property | Type | Required | Notes |
+| --- | --- | --- | --- |
+| `contractVersion` | — | yes |  |
+| `id` | `#/$defs/identifier` | yes |  |
+| `version` | `#/$defs/semver` | yes |  |
+| `publisher` | string | yes |  |
+| `displayNameKey` | string | yes |  |
+| `descriptionKey` | string | yes |  |
+| `distribution` | enum | yes | one of: `locked`, `editable` |
+| `dependencies` | array |  |  |
+| `contributions` | `#/$defs/contributions` | yes |  |
+| `hasUpgradeMigration` | boolean |  |  |
+| `hasDataErasureHook` | boolean |  |  |
+| `frontendBundle` | object |  | 2026-09-03, closes the dynamic-frontend-plugin-loading gap (ai/domains/ai-native-developer-platform-gap-analysis.md): a compiled @erp/* frontend bundle a runtime loader fetches from the real, generic engine-file content endpoint (GET /api/v1/files/{fileId}/content) and dynamically import()s, instead of the code shipping inside a host application's own build. Optional and additive - absent on every manifest that predates this field (every real plugin in the fleet today except this pass's own proof plugin), which a frontend loader must treat as a cheap, silent no-op. |
+
+## Named sub-definitions
+
+`identifier`, `semver`, `versionRange`, `dependency`, `argKind`, `actionTypeContribution`, `functionContribution`, `idDescription`, `networkScopedContribution`, `scheduledJobContribution`, `themeContribution`, `menuItemContribution`, `localeBundleContribution`, `contributions`
+