@synap-core/workspace-templates 0.9.4 → 0.10.0

package/dist/index.d.ts

@@ -138,6 +138,28 @@ interface TemplateEntityLink {
     type: string;
     label?: string;
 }
+/**
+ * A domain-level relation TYPE definition — a `relation_defs` row, the workspace's
+ * relation vocabulary. Distinct from {@link TemplateEntityLink}, which is a
+ * profile→profile EDGE (and only carries `type` + `label`). A relation def stands
+ * alone: it has no source/target profile pairing and it carries the rich metadata
+ * (`description`, `isDirectional`, `uiHints`) that the entity-link path drops.
+ *
+ * Mirrors `DefaultRelationDef` in synap-backend
+ * `packages/database/src/utils/default-relation-defs.ts` VERBATIM — the door
+ * find-or-creates a `relation_defs` row from each entry (idempotent by
+ * `slug` within the workspace), which is `ensureDefaultRelationDefs`'s body.
+ */
+interface TemplateRelationDef {
+    slug: string;
+    displayName: string;
+    description?: string;
+    isDirectional?: boolean;
+    uiHints?: {
+        category?: "workflow" | "social" | "reference" | "hierarchy";
+        inverseLabel?: string;
+    };
+}
 interface TemplateSeedEntity {
     profileSlug: string;
     title: string;
@@ -352,6 +374,22 @@ interface TemplateAutomation {
     };
     status?: "draft" | "active" | "paused";
 }
+interface TemplateCommandDerivedInput {
+    name: string;
+    label?: string;
+    /** Mirrors `DerivedInput.type` (text | number | entity | view | choice). */
+    type?: string;
+}
+interface TemplateCommand {
+    title: string;
+    promptTemplate: string;
+    derivedInputs?: TemplateCommandDerivedInput[];
+    /** text | proposal | view */
+    outputMode?: string;
+    canCreateViews?: boolean;
+    /** read_only | propose_writes */
+    permissionsProfile?: string;
+}
 interface TemplateActionPlacement {
     /** Entity kind whose detail surface this action appears on. */
     profileSlug: string;
@@ -537,6 +575,19 @@ interface WorkspaceYaml {
     views?: TemplateView[];
     /** Schema-level links between entity types */
     entityLinks?: TemplateEntityLink[];
+    /**
+     * Domain-level relation TYPE vocabulary seeded into the workspace's
+     * `relation_defs`. Distinct from `entityLinks` (profile→profile edges): a
+     * relation def stands alone and carries `description`/`isDirectional`/`uiHints`.
+     * The `base` template carries the universal defaults. See {@link TemplateRelationDef}.
+     */
+    relationDefs?: TemplateRelationDef[];
+    /**
+     * Workspace-scoped intelligence commands (prompt-template "Default Command
+     * Pack") seeded with the workspace. The `base` template carries the universal
+     * pack. See {@link TemplateCommand}.
+     */
+    commands?: TemplateCommand[];
     /** Initial data to seed on workspace creation */
     seedEntities?: TemplateSeedEntity[];
     /** Relations between seed entities, created on provisioning */
@@ -977,9 +1028,11 @@ declare function layerTemplateGraph(input: LayerTemplateGraphInput): Composition
  * Cross-template CONCEPT guard — catches vocabulary forks between templates.
  *
  * WHY THIS EXISTS (read before weakening or deleting it):
- * `business-developer.yaml` introduced workspace-scoped `crm-lead`/`crm-client`
- * for the same real-world concept that `foundation.yaml`/`crm.yaml` declare as
- * pod-wide shared `lead`/`client`. Nothing failed. Three reasons:
+ * `business-developer.yaml` once introduced workspace-scoped
+ * `crm-lead`/`crm-client` for the same real-world concept that
+ * `foundation.yaml`/`crm.yaml` declare as pod-wide shared `lead`/`client` (that
+ * fork has since been collapsed back onto the shared slugs). Nothing failed at
+ * the time. Three reasons:
  *
  *   1. `build.mjs`'s `validate()` runs PER FILE, inside the read loop, so it
  *      structurally cannot see that another template already owns `lead`.
@@ -1017,6 +1070,13 @@ interface ConceptViolation {
  * list cannot rot into a graveyard.
  *
  * Key = the two colliding profile slugs, sorted, joined by "|".
+ *
+ * Currently EMPTY, and that is the healthy state. The two entries this list was
+ * born for — `crm-lead|lead` and `client|crm-client` — were RESOLVED rather
+ * than kept: business-developer.yaml now re-declares the shared `lead`/`client`
+ * roles and carries its business-development fields as workspace-overlay
+ * PROPERTIES. One concept, one slug, workspace-specific fields. Rule 3 below
+ * would have failed CI had the entries been left behind.
  */
 declare const DECLARED_DIVERGENCES: Record<string, string>;
 /**
@@ -1029,7 +1089,14 @@ declare const DECLARED_DIVERGENCES: Record<string, string>;
  * is honest: no guard can know they mean the same thing.
  */
 declare function conceptTerm(semanticSlug: string): string;
-declare function findConceptViolations(templates?: Record<string, WorkspaceYaml>): ConceptViolation[];
+declare function findConceptViolations(templates?: Record<string, WorkspaceYaml>, 
+/**
+ * The declared-divergence allowlist to enforce against. Defaults to the real
+ * one; injectable so the escape-hatch semantics (rule 1 suppression, rule 3
+ * staleness) stay testable now that the shipped list is empty — previously
+ * those tests could only be written because a live entry happened to exist.
+ */
+declaredDivergences?: Record<string, string>): ConceptViolation[];
 declare function formatConceptViolations(violations: ConceptViolation[]): string;
 
 /**
@@ -1262,18 +1329,18 @@ declare function validateTemplate(tpl: WorkspaceYaml, opts?: ValidateOptions): V
  * Until then: keep the constant arrays below identical to `@synap/database`
  * `schema/automations.ts`.
  */
-/** The 21 node types — `AutomationNodeBase.type` union (schema/automations.ts). */
-declare const FLOW_NODE_TYPES: readonly ["trigger", "command", "condition", "delay", "output", "loop", "transform", "fetch", "query", "entity_read", "related_entities", "guard", "compute", "select", "claim", "messages_query", "switch", "skill", "capability", "sub_automation", "playbook_run"];
+/** The 23 node types — `AutomationNodeBase.type` union (schema/automations.ts). */
+declare const FLOW_NODE_TYPES: readonly ["trigger", "command", "condition", "delay", "output", "loop", "transform", "fetch", "query", "entity_read", "related_entities", "guard", "compute", "select", "claim", "messages_query", "runs_query", "proposals_query", "switch", "skill", "capability", "sub_automation", "playbook_run"];
 /** The 11 output types — `OutputNodeDef.data.outputType` (schema/automations.ts). */
 declare const FLOW_OUTPUT_TYPES: readonly ["notification", "entity_create", "entity_update", "facet_attach", "facet_update", "facet_detach", "relation_create", "webhook", "channel_message", "session_update", "set_state"];
 /**
  * The known `config.channelType` values for a `channel_message` output. Mirrors
  * the executor's channel_message resolution (automation-executor.ts). The output
- * channel is CONTEXT-DERIVED — a channel_message is valid with `channelId`, OR
- * `channelEntityRef` (an entity-id expression → that entity's internal channel),
- * OR a `channelType` from this set, OR NOTHING (the executor defaults a targetless
- * channel_message to the automation's own run channel). A `channelType` that is
- * PRESENT but not one of these is still a typo → still an error.
+ * channel is now CONTEXT-DERIVED — a channel_message is valid with `channelId`,
+ * OR `channelEntityRef` (an entity-id expression → that entity's internal
+ * channel), OR a `channelType` from this set, OR NOTHING (the executor defaults a
+ * targetless channel_message to the automation's own run channel). A `channelType`
+ * that is PRESENT but not one of these is still a typo → still an error.
  */
 declare const CHANNEL_MESSAGE_CHANNEL_TYPES: readonly ["personal_thread", "proactive", "subjectEntity"];
 interface FlowValidationError {
@@ -1390,6 +1457,19 @@ interface WorkspaceDefinitionInput {
     seedEntities: NonNullable<WorkspaceYaml['seedEntities']>;
     suggestedRelations?: WorkspaceYaml['suggestedRelations'];
     displayTemplates?: WorkspaceYaml['displayTemplates'];
+    /**
+     * Domain-level relation TYPE vocabulary — the door find-or-creates a
+     * `relation_defs` row per entry (idempotent by slug within the workspace). NOT
+     * `entityLinks` (those are profile→profile edges and drop the rich metadata).
+     * Carried verbatim; the authored form IS the wire form.
+     */
+    relationDefs?: WorkspaceYaml['relationDefs'];
+    /**
+     * Workspace intelligence commands — the door find-or-creates an
+     * `intelligence_commands` row per entry (idempotent by title). Carried
+     * verbatim; the authored form IS the wire form.
+     */
+    commands?: WorkspaceYaml['commands'];
     layoutConfig: WorkspaceYaml['layout'] | undefined;
     bentoViewName?: string;
     /**
@@ -1494,6 +1574,10 @@ interface PackageDefinitionOutput {
     suggestedRelations?: WorkspaceYaml['suggestedRelations'];
     displayTemplates?: WorkspaceYaml['displayTemplates'];
     entityLinks?: WorkspaceYaml['entityLinks'];
+    /** Relation-type vocabulary — carried verbatim (authored form IS the wire form). */
+    relationDefs?: WorkspaceYaml['relationDefs'];
+    /** Intelligence commands — carried verbatim (authored form IS the wire form). */
+    commands?: WorkspaceYaml['commands'];
     /** WIDGET half of the authored bento union — mapped by the pod via `widgetType`. */
     bentoLayout?: BentoWidgetBlockWire[];
     /**