@synap-core/workspace-templates 0.6.1 → 0.6.3

package/dist/index.d.ts

@@ -150,13 +150,6 @@ interface TemplateProfileEntityBentoTemplates {
         blocks: Array<Record<string, unknown>>;
     };
 }
-interface TemplateAutomation {
-    name: string;
-    description?: string;
-    trigger: string;
-    action: string;
-    config?: Record<string, unknown>;
-}
 /** Mirrors `WorkspaceSourceRole` in synap-backend `schema/workspaces.ts`. */
 type TemplateSourceRole = 'provider' | 'consumer' | 'provider-consumer';
 /** Mirrors `WorkspaceDefaultSource` in synap-backend `schema/workspaces.ts`. */
@@ -238,6 +231,16 @@ interface TemplatePlaybook {
     } | null;
     /** tool/skill keys this playbook grants. */
     grants?: string[];
+    /**
+     * The entity kind this playbook operates over, persisted to
+     * `playbooks.subject_profile`. Makes the playbook matchable by
+     * `playbooks.matchForEntity` (filters `subject_profile->>'profileSlug'`), so a
+     * captured entity of this kind can auto-launch the playbook as a session.
+     */
+    subjectProfile?: {
+        profileSlug: string;
+        filter?: Record<string, unknown>;
+    };
     status?: 'draft' | 'active' | 'paused';
 }
 interface TemplateIntegration {
@@ -401,8 +404,6 @@ interface WorkspaceYaml {
     };
     /** Per-profile entity bento layouts */
     profileEntityBentoTemplates?: TemplateProfileEntityBentoTemplates;
-    /** Automations to install on workspace creation */
-    automations?: TemplateAutomation[];
     /** Playbooks (session templates) seeded with the workspace */
     playbooks?: TemplatePlaybook[];
     /** Capability templates (tools/connectors) to install on provisioning */
@@ -536,6 +537,42 @@ interface MergeCatalogInput {
      */
     remoteStatus?: RemoteSourceStatus;
 }
+/**
+ * A control-plane package LIST row, as returned by `GET /api/packages` and
+ * `GET /api/packages/mine`. This is the raw JSON shape BEFORE it is projected
+ * into a `RemoteEntry`. Both list routes STRIP `definition`, so it is absent
+ * here (the install path fetches the full row per-slug on demand).
+ *
+ * `isPublic` is present ONLY on `/mine` rows (`false` ⇒ private). Public browse
+ * rows omit it BY CONSTRUCTION (the list route hard-filters `WHERE is_public =
+ * true`), so its absence means "public", never "unknown".
+ *
+ * Consumers used to hand-copy this shape + `rowToRemoteEntry` (browser
+ * `useMarketplaceCatalog`, CLI `cp-packages`); this is the ONE canonical copy.
+ */
+interface CpPackageRow {
+    slug: string;
+    displayName: string;
+    description?: string | null;
+    /** CP package category / type (e.g. `"workspace"`, `"view"`). */
+    category?: string;
+    tags?: string[] | null;
+    icon?: string | null;
+    /** Present only on `/mine` rows. `false` ⇒ private. Browse rows omit it. */
+    isPublic?: boolean;
+}
+/**
+ * Map a CP list row into the merge door's `RemoteEntry`. THE canonical mapping —
+ * browser + CLI import this instead of hand-copying it (the two copies had
+ * already drifted in `description`/`isPrivate` handling).
+ *
+ * `isPrivate` is passed EXPLICITLY by the caller because it depends on WHICH
+ * route the row came from: browse rows are all-public (pass `undefined`), `/mine`
+ * rows carry the real flag (pass `row.isPublic === false`). Keeping it a param —
+ * not derived here — lets a caller that fetches the two routes separately control
+ * it per-source; `assembleCatalog` derives it from the row for the common case.
+ */
+declare function rowToRemoteEntry(row: CpPackageRow, isPrivate?: boolean): RemoteEntry;
 interface CatalogEntryBase {
     slug: string;
     name: string;
@@ -592,6 +629,29 @@ interface MergeCatalogResult {
  * entry (a private or third-party package) and is always kept.
  */
 declare function mergeCatalog(input: MergeCatalogInput): MergeCatalogResult;
+interface AssembleCatalogInput {
+    /** Bundled templates (this package). Always in-process. */
+    bundled: BundledEntry[];
+    /**
+     * Raw CP list rows (browse and/or `/mine`, concatenated). Mapped to
+     * `RemoteEntry` via `rowToRemoteEntry`; `isPrivate` is DERIVED per-row from
+     * `isPublic` (`false` ⇒ private; absent/`true` ⇒ public), which handles both
+     * browse rows (no `isPublic`) and `/mine` rows uniformly.
+     */
+    remoteRows?: CpPackageRow[];
+    /** This client's bundled-package version (the winner signal vs each row). */
+    bundleVersion: string;
+    /** The transport's verdict on the remote fetch. Default `"ok"`. */
+    remoteStatus?: RemoteSourceStatus;
+}
+/**
+ * Convenience wrapper over `mergeCatalog`: maps raw CP rows through the canonical
+ * `rowToRemoteEntry` and merges them with the bundled templates. Still PURE — the
+ * caller fetches the rows (its own transport/auth) and passes them in; this only
+ * maps + merges. Use `mergeCatalog` + `rowToRemoteEntry` directly when you need
+ * per-source `isPrivate` control (e.g. keeping browse and `/mine` distinct).
+ */
+declare function assembleCatalog(input: AssembleCatalogInput): MergeCatalogResult;
 
 /**
  * @synap-core/workspace-templates — Definition adapter
@@ -647,6 +707,18 @@ interface WorkspaceDefinitionInput {
     /** VIEW half of the authored bento union — resolved against the viewMap. */
     bentoViewBlocks?: BentoViewBlockWire[];
     profileEntityBentoTemplates?: WorkspaceYaml['profileEntityBentoTemplates'];
+    /**
+     * Capability integrations (→ tools + skills + vault + capability-embedded
+     * automations/playbooks). Emitted from the template's `integrations:` list —
+     * IDENTICAL to what `toPackageDefinition` puts in its `capabilities` field. The
+     * tRPC door (`workspaces.createFromDefinition`) now declares `capabilities` in
+     * its zod input and installs them via the SHARED `applyPackagePostWorkspace`
+     * door (same as Hub `/packages/apply`). It was missing from this interface, so
+     * `toWorkspaceDefinition` had nowhere to put integrations and the browser
+     * BUNDLED install path carried NO capabilities — every capability's
+     * tools/skills/automations silently dropped on that door.
+     */
+    capabilities?: WorkspaceYaml['integrations'];
     workspaceSubtype?: string;
     workspaceType?: NonNullable<WorkspaceYaml['workspace']>['workspaceType'];
     workspaceVisibility?: string;
@@ -738,4 +810,4 @@ interface PackageDefinitionOutput {
  */
 declare function toPackageDefinition(slugOrYaml: string | WorkspaceYaml): PackageDefinitionOutput;
 
-export { type BentoViewBlockWire, type BentoWidgetBlockWire, type BundledCatalogEntry, type BundledEntry, type CatalogEntry, type MergeCatalogInput, type MergeCatalogResult, PACKAGE_DEPENDENCY_KINDS, type PackageDefinitionOutput, type PackageDependencyKind, type RemoteCatalogEntry, type RemoteEntry, type RemoteSourceStatus, type SplitBentoBlocks, type TemplateAppKind, type TemplateAppRef, type TemplateAutomation, type TemplateBentoBlock, type TemplateDefaultSource, type TemplateDependency, type TemplateDisplayTemplate, type TemplateEntityLink, type TemplateExtendsRef, type TemplateIntegration, type TemplateLayoutConfig, type TemplateMeta, type TemplateOnboarding, type TemplateOnboardingCollectTarget, type TemplatePlaybook, type TemplatePlaybookParam, type TemplateProfile, type TemplateProfileEntityBentoTemplates, type TemplateProperty, type TemplateSeedEntity, type TemplateSidebarItem, type TemplateSidebarSurface, type TemplateSourceRole, type TemplateSuggestedRelation, type TemplateView, type ToDefinitionResult, WORKSPACE_TEMPLATES, type WorkspaceDefinitionInput, type WorkspaceTemplateSlug, type WorkspaceYaml, getWorkspaceTemplate, listPublicTemplates, listWorkspaceTemplates, mergeCatalog, splitBentoBlocks, toPackageDefinition, toWorkspaceDefinition };
+export { type AssembleCatalogInput, type BentoViewBlockWire, type BentoWidgetBlockWire, type BundledCatalogEntry, type BundledEntry, type CatalogEntry, type CpPackageRow, type MergeCatalogInput, type MergeCatalogResult, PACKAGE_DEPENDENCY_KINDS, type PackageDefinitionOutput, type PackageDependencyKind, type RemoteCatalogEntry, type RemoteEntry, type RemoteSourceStatus, type SplitBentoBlocks, type TemplateAppKind, type TemplateAppRef, type TemplateBentoBlock, type TemplateDefaultSource, type TemplateDependency, type TemplateDisplayTemplate, type TemplateEntityLink, type TemplateExtendsRef, type TemplateIntegration, type TemplateLayoutConfig, type TemplateMeta, type TemplateOnboarding, type TemplateOnboardingCollectTarget, type TemplatePlaybook, type TemplatePlaybookParam, type TemplateProfile, type TemplateProfileEntityBentoTemplates, type TemplateProperty, type TemplateSeedEntity, type TemplateSidebarItem, type TemplateSidebarSurface, type TemplateSourceRole, type TemplateSuggestedRelation, type TemplateView, type ToDefinitionResult, WORKSPACE_TEMPLATES, type WorkspaceDefinitionInput, type WorkspaceTemplateSlug, type WorkspaceYaml, assembleCatalog, getWorkspaceTemplate, listPublicTemplates, listWorkspaceTemplates, mergeCatalog, rowToRemoteEntry, splitBentoBlocks, toPackageDefinition, toWorkspaceDefinition };

package/dist/index.js

@@ -6518,6 +6518,26 @@ var DATA = {
         "label": "Depends on"
       }
     ],
+    "playbooks": [
+      {
+        "name": "Evaluate Feature",
+        "description": "Assess a feature \u2014 its current state, whether it's worth building, and how it fits the rest of the system.",
+        "goalTemplate": "Evaluate this feature ({feature}): where it stands today (its status, progress, and any blockers), whether it is actually useful (the problem it solves and for whom), and how it integrates with the existing apps, packages, services, and environments in this workspace. Finish with a clear recommendation \u2014 continue, cut, or reshape \u2014 and the reasoning behind it.",
+        "subjectProfile": {
+          "profileSlug": "devplane_feature"
+        },
+        "params": [
+          {
+            "name": "feature",
+            "type": "entity",
+            "label": "Feature",
+            "required": true
+          }
+        ],
+        "executor": "is-agent",
+        "status": "active"
+      }
+    ],
     "onboarding": {
       "goal": "Capture the real engineering surface \u2014 the apps that are shipped, where their code lives, what runs behind them, where they deploy, and what's in flight \u2014 so the workspace mirrors what the team actually builds and runs, not a generic template.",
       "framing": "THE STAFF ENGINEER: Act as a pragmatic, precise staff/platform engineer standing up a developer command center. Tease out what's actually shipped vs. planned, where the code lives (repos + local paths), what runs behind each app, where it deploys, and what's on the bench right now. Prefer concrete over aspirational \u2014 a repo URL beats a wish. Tie the roadmap back to the Foundation's mission and audiences: the surface exists to serve them.\n",
@@ -8465,6 +8485,16 @@ var DATA = {
         "groupBy": "post-status",
         "description": "Content posts by status."
       },
+      {
+        "name": "Content Calendar",
+        "slug": "content-calendar",
+        "type": "calendar",
+        "scopeProfileSlug": "post",
+        "description": "Your editorial calendar \u2014 every post on the day it publishes.",
+        "config": {
+          "dateField": "properties.publish-date"
+        }
+      },
       {
         "name": "Pillars",
         "slug": "content-pillars",
@@ -8506,6 +8536,12 @@ var DATA = {
           "label": "Posts",
           "icon": "file-edit"
         },
+        {
+          "kind": "view",
+          "viewName": "Content Calendar",
+          "label": "Calendar",
+          "icon": "calendar"
+        },
         {
           "kind": "view",
           "viewName": "Pillars",
@@ -8531,10 +8567,20 @@ var DATA = {
       "blocks": [
         {
           "kind": "view",
-          "viewName": "Pillars",
+          "viewName": "Content Calendar",
           "pos": {
             "x": 0,
             "y": 0,
+            "w": 12,
+            "h": 6
+          }
+        },
+        {
+          "kind": "view",
+          "viewName": "Pillars",
+          "pos": {
+            "x": 0,
+            "y": 6,
             "w": 6,
             "h": 5
           }
@@ -8544,7 +8590,7 @@ var DATA = {
           "viewName": "Newsletters",
           "pos": {
             "x": 6,
-            "y": 0,
+            "y": 6,
             "w": 6,
             "h": 5
           }
@@ -8571,6 +8617,37 @@ var DATA = {
         "label": "Sponsor"
       }
     ],
+    "playbooks": [
+      {
+        "name": "Produce Content",
+        "description": "Take a captured post idea and carry it from spark to a scheduled, platform-ready draft.",
+        "goalTemplate": "Produce content for {platform} from this idea ({post}). Take the raw idea, shape it into a {format} draft with a scroll-stopping hook and a clear CTA, keep it aligned to the post's pillar and the operator's brand voice, then move it to Scheduled with a publish date.",
+        "subjectProfile": {
+          "profileSlug": "post"
+        },
+        "params": [
+          {
+            "name": "post",
+            "type": "entity",
+            "label": "Post",
+            "required": true
+          },
+          {
+            "name": "platform",
+            "type": "text",
+            "label": "Platform",
+            "required": true
+          },
+          {
+            "name": "format",
+            "type": "text",
+            "label": "Format"
+          }
+        ],
+        "executor": "is-agent",
+        "status": "active"
+      }
+    ],
     "onboarding": {
       "goal": "Stand up the editorial engine \u2014 the pillars you're known for, the platforms you publish on, the cadence you can actually sustain, and a first post placed in the system \u2014 so the workspace mirrors how you turn thinking into published content, not a blank calendar.\n",
       "framing": `THE EDITOR-IN-CHIEF: Act as a seasoned content strategist who has grown owned audiences from zero. Anchor everything on PILLARS \u2014 the two-to-four recurring themes an audience comes to you for \u2014 because pillars are what make a content engine compound instead of drift. Pull voice and identity from Brand and the target audience from Foundation so every piece lands on-strategy. Push for a cadence they can hold for a year, not a heroic month. Be concrete: real platforms, real formats, a real first post \u2014 a fuzzy "I'll post more" helps no one.
@@ -9693,6 +9770,62 @@ var DATA = {
         "targetProfileSlug": "deal",
         "type": "linked_to_deal"
       }
+    ],
+    "playbooks": [
+      {
+        "name": "Enrich this lead",
+        "description": "Take a thin, freshly-captured lead and fill it out \u2014 company, title, LinkedIn, and the relationships around it.",
+        "goalTemplate": "Enrich this lead ({lead}). Starting from whatever is known, fill out the missing detail \u2014 company, job title, LinkedIn URL, location, and the people and companies around them \u2014 and record it on the lead. Draw on whatever enrichment capability this workspace has connected (e.g. an Apify or Unipile/LinkedIn tool); if none is available, enrich from the public web and what is already in the pod. Link the lead to its company and any related contacts, and note where information is still missing.",
+        "subjectProfile": {
+          "profileSlug": "lead"
+        },
+        "params": [
+          {
+            "name": "lead",
+            "type": "entity",
+            "label": "Lead",
+            "required": true
+          }
+        ],
+        "executor": "is-agent",
+        "status": "active"
+      },
+      {
+        "name": "Qualify this lead",
+        "description": "Assess a lead against the ICP, score the fit, and decide the next step \u2014 advance, nurture, or disqualify.",
+        "goalTemplate": "Qualify this lead ({lead}). Assess how well they fit our ideal customer profile \u2014 company, role, industry, size, and the signals of intent or need \u2014 and set an ICP score. Decide the next step: advance them toward a deal, keep nurturing, or disqualify. Write the reasoning and the decision back onto the lead (its stage, score, and next step) so the call is auditable.",
+        "subjectProfile": {
+          "profileSlug": "lead"
+        },
+        "params": [
+          {
+            "name": "lead",
+            "type": "entity",
+            "label": "Lead",
+            "required": true
+          }
+        ],
+        "executor": "is-agent",
+        "status": "active"
+      },
+      {
+        "name": "Work this deal",
+        "description": "Move a deal toward Won \u2014 read the current stage, find the blocker, and propose the next step and owner.",
+        "goalTemplate": "Work this deal ({deal}) toward Won. Assess where it stands \u2014 its current stage, value, and close date \u2014 and identify the single thing blocking it from advancing. Propose the concrete next step, who owns it, and by when, and update the deal's next step accordingly. If the stage should change, say so and why.",
+        "subjectProfile": {
+          "profileSlug": "deal"
+        },
+        "params": [
+          {
+            "name": "deal",
+            "type": "entity",
+            "label": "Deal",
+            "required": true
+          }
+        ],
+        "executor": "is-agent",
+        "status": "active"
+      }
     ]
   },
   "dev-dashboard": {
@@ -11941,6 +12074,79 @@ var DATA = {
         "label": "Involves"
       }
     ],
+    "playbooks": [
+      {
+        "name": "Research Competitor",
+        "description": "Deep-research a competitor and position it against us \u2014 strengths, weaknesses, pricing, and the gaps we can exploit.",
+        "goalTemplate": "Research this competitor ({competitor}) and compare them to us. Investigate their {focus}: positioning, strengths, weaknesses, pricing, and recent moves. Use the provided company context where relevant: {companyContext}. Produce: {outputTypes}. Update the competitor entity with what you find and make clear where we win and where we are exposed.",
+        "subjectProfile": {
+          "profileSlug": "competitor"
+        },
+        "params": [
+          {
+            "name": "competitor",
+            "type": "entity",
+            "label": "Competitor",
+            "required": true
+          },
+          {
+            "name": "focus",
+            "type": "text",
+            "label": "Focus area",
+            "defaultValue": "product, pricing, and positioning"
+          },
+          {
+            "name": "companyContext",
+            "type": "text",
+            "label": "Our company context"
+          },
+          {
+            "name": "outputTypes",
+            "type": "text",
+            "label": "Outputs",
+            "defaultValue": "a head-to-head comparison summary and an updated competitor profile"
+          }
+        ],
+        "executor": "is-agent",
+        "schedule": {
+          "cron": "0 9 * * 1",
+          "enabled": false
+        },
+        "grants": [
+          "Web Search",
+          "Entity Creator"
+        ],
+        "status": "active"
+      },
+      {
+        "name": "Discover Competitors",
+        "description": "Scan the market for competitors we don't track yet and add them to the ecosystem \u2014 the self-generating half of the radar.",
+        "goalTemplate": 'Find companies that compete with us in {ourSpace}. Use neural web search (the exa_search skill with category "company") to surface real, named companies \u2014 direct competitors, adjacent tools that solve the same job a different way, and emerging players. For each genuinely NEW one (not already a competitor in our ecosystem), propose it as a `competitor` entity and ALWAYS include its `website` (its canonical URL) so it de-duplicates against what we already track \u2014 never create a company that already exists. Skip anything already known. Report what you added and why each one matters.',
+        "schedule": {
+          "cron": "0 9 * * 1",
+          "enabled": false
+        },
+        "params": [
+          {
+            "name": "ourSpace",
+            "type": "text",
+            "label": "Our market / category",
+            "required": true
+          }
+        ],
+        "executor": "is-agent",
+        "grants": [
+          "exa_search",
+          "Entity Creator"
+        ],
+        "status": "active"
+      }
+    ],
+    "integrations": [
+      {
+        "templateKey": "exa"
+      }
+    ],
     "onboarding": {
       "goal": 'Map the real ecosystem \u2014 the key players (companies and people), who partners and competes with whom, and the segments and trends that matter \u2014 so strategy is grounded in the actual market, not a vague "the market".\n',
       "framing": 'THE ECOSYSTEM LEAD: Act as a sharp ecosystem lead who maps the market\nlandscape AND the relationships inside it. Push for REAL named players \u2014 not\n"the incumbents", but the actual companies \u2014 and for the concrete edges\nbetween them: who partners with whom, who competes, who invested in whom.\nA map with no edges is just a list; the value is in the relationships.\n',
@@ -12116,6 +12322,12 @@ var DATA = {
         "kind": "workspace",
         "relation": "require",
         "reason": "The pipeline \u2014 contacts, leads, clients, and deals."
+      },
+      {
+        "slug": "content-os",
+        "kind": "workspace",
+        "relation": "require",
+        "reason": "The editorial engine \u2014 pillars, posts, platforms, and newsletters \u2014 so the company's content operation is part of the operating core."
       }
     ],
     "workspace": {
@@ -24826,6 +25038,19 @@ function listPublicTemplates() {
 }
 
 // src/catalog.ts
+function rowToRemoteEntry(row, isPrivate) {
+  return {
+    slug: row.slug,
+    name: row.displayName,
+    description: row.description ?? void 0,
+    category: row.category,
+    tags: row.tags ?? [],
+    icon: row.icon ?? null,
+    isPrivate
+    // Both list routes strip `definition`; absence ⇒ bundle wins a slug conflict,
+    // and the install path fetches the full definition per-slug when needed.
+  };
+}
 function parseSemver(v) {
   if (!v) return null;
   const m = /^\s*v?(\d+)\.(\d+)\.(\d+)/.exec(v);
@@ -24900,6 +25125,17 @@ function mergeCatalog(input) {
     sources: { bundled: "ok", remote: remoteStatus }
   };
 }
+function assembleCatalog(input) {
+  const remote = (input.remoteRows ?? []).map(
+    (row) => rowToRemoteEntry(row, row.isPublic === false ? true : void 0)
+  );
+  return mergeCatalog({
+    bundled: input.bundled,
+    remote,
+    bundleVersion: input.bundleVersion,
+    remoteStatus: input.remoteStatus
+  });
+}
 
 // src/define.ts
 function resolveBlockKind(block) {
@@ -24956,6 +25192,13 @@ function toWorkspaceDefinition(slugOrYaml, nameOverride) {
     bentoLayout: bento.bentoLayout,
     bentoViewBlocks: bento.bentoViewBlocks,
     profileEntityBentoTemplates: tpl.profileEntityBentoTemplates,
+    // Capability integrations — forwarded so the tRPC/UI (bundled) install door
+    // seeds the SAME operational payload (tools + skills + capability-embedded
+    // automations/playbooks) the CLI/Hub door gets via `toPackageDefinition`.
+    // `workspaces.createFromDefinition` declares `capabilities` in its zod input
+    // and routes it through the shared `applyPackagePostWorkspace` door. Omitting
+    // it here made the browser bundled-install path carry no capabilities at all.
+    capabilities: tpl.integrations,
     workspaceSubtype: ws.subtype,
     workspaceType: ws.workspaceType,
     workspaceVisibility: ws.visibility,
@@ -25020,10 +25263,12 @@ function toPackageDefinition(slugOrYaml) {
 export {
   PACKAGE_DEPENDENCY_KINDS,
   WORKSPACE_TEMPLATES,
+  assembleCatalog,
   getWorkspaceTemplate,
   listPublicTemplates,
   listWorkspaceTemplates,
   mergeCatalog,
+  rowToRemoteEntry,
   splitBentoBlocks,
   toPackageDefinition,
   toWorkspaceDefinition