@elevasis/core 0.7.0 → 0.8.0

package/src/operations/triggers/webhook/definitions/instantly-lead-unsubscribed.ts

@@ -1,45 +1,45 @@
-/**
- * Instantly Lead Unsubscribed Trigger Definition
- *
- * Webhook trigger for Instantly lead unsubscribe events.
- * Uses Instantly's native snake_case format - no transformation needed.
- */
-
-import type { TriggerDefinition, WebhookTriggerConfig } from '../../../../platform/registry/types'
-
-/**
- * Instantly lead unsubscribed webhook payload structure
- *
- * Uses snake_case matching Instantly's API. Workflows receive this directly.
- */
-export interface InstantlyLeadUnsubscribedPayload {
-  timestamp: string
-  event_type: 'lead_unsubscribed'
-  workspace: string
-  campaign_id: string
-  campaign_name?: string
-  lead_email: string
-  email_account: string
-}
-
-/**
- * Instantly Lead Unsubscribed Trigger Definition
- *
- * Trigger type: webhook
- * Provider: instantly
- * Event: lead_unsubscribed
- */
-export const instantlyLeadUnsubscribedTrigger: TriggerDefinition = {
-  resourceId: 'trigger-instantly-lead-unsubscribed',
-  type: 'trigger',
-  triggerType: 'webhook',
-  name: 'Instantly Lead Unsubscribed',
-  description: 'Webhook fired when a lead unsubscribes from an Instantly email campaign',
-  version: '1.0.0',
-  status: 'dev',
-  webhookPath: '/webhooks/instantly/lead-unsubscribed',
-  config: {
-    provider: 'instantly',
-    event: 'lead_unsubscribed'
-  } as WebhookTriggerConfig
-}
+/**
+ * Instantly Lead Unsubscribed Trigger Definition
+ *
+ * Webhook trigger for Instantly lead unsubscribe events.
+ * Uses Instantly's native snake_case format - no transformation needed.
+ */
+
+import type { TriggerDefinition, WebhookTriggerConfig } from '../../../../platform/registry/types'
+
+/**
+ * Instantly lead unsubscribed webhook payload structure
+ *
+ * Uses snake_case matching Instantly's API. Workflows receive this directly.
+ */
+export interface InstantlyLeadUnsubscribedPayload {
+  timestamp: string
+  event_type: 'lead_unsubscribed'
+  workspace: string
+  campaign_id: string
+  campaign_name?: string
+  lead_email: string
+  email_account: string
+}
+
+/**
+ * Instantly Lead Unsubscribed Trigger Definition
+ *
+ * Trigger type: webhook
+ * Provider: instantly
+ * Event: lead_unsubscribed
+ */
+export const instantlyLeadUnsubscribedTrigger: TriggerDefinition = {
+  resourceId: 'trigger-instantly-lead-unsubscribed',
+  type: 'trigger',
+  triggerType: 'webhook',
+  name: 'Instantly Lead Unsubscribed',
+  description: 'Webhook fired when a lead unsubscribes from an Instantly email campaign',
+  version: '1.0.0',
+  status: 'dev',
+  webhookPath: '/webhooks/instantly/lead-unsubscribed',
+  config: {
+    provider: 'instantly',
+    event: 'lead_unsubscribed'
+  } as WebhookTriggerConfig
+}

package/src/operations/triggers/webhook/definitions/instantly-reply-received.ts

@@ -1,54 +1,54 @@
-/**
- * Instantly Reply Received Trigger Definition
- *
- * Webhook trigger for Instantly email reply events.
- * Uses Instantly's native snake_case format - no transformation needed.
- */
-
-import type { TriggerDefinition, WebhookTriggerConfig } from '../../../../platform/registry/types'
-
-/**
- * Instantly webhook payload structure
- *
- * Uses snake_case matching Instantly's API. Workflows receive this directly.
- */
-export interface InstantlyReplyWebhookPayload {
-  timestamp: string
-  event_type: 'reply_received'
-  workspace: string
-  campaign_id: string
-  campaign_name?: string
-  lead_email: string
-  email_account: string
-  unibox_url: string
-  reply_to_uuid: string
-  reply_subject: string
-  reply_text: string
-  reply_text_snippet: string
-  reply_html: string
-  step: number
-  variant: number
-  is_first: boolean
-}
-
-/**
- * Instantly Reply Received Trigger Definition
- *
- * Trigger type: webhook
- * Provider: instantly
- * Event: reply_received
- */
-export const instantlyReplyReceivedTrigger: TriggerDefinition = {
-  resourceId: 'trigger-instantly-reply-received',
-  type: 'trigger',
-  triggerType: 'webhook',
-  name: 'Instantly Reply Received',
-  description: 'Webhook fired when a lead replies to an Instantly email campaign',
-  version: '1.0.0',
-  status: 'dev',
-  webhookPath: '/webhooks/instantly/reply-received',
-  config: {
-    provider: 'instantly',
-    event: 'reply_received'
-  } as WebhookTriggerConfig
-}
+/**
+ * Instantly Reply Received Trigger Definition
+ *
+ * Webhook trigger for Instantly email reply events.
+ * Uses Instantly's native snake_case format - no transformation needed.
+ */
+
+import type { TriggerDefinition, WebhookTriggerConfig } from '../../../../platform/registry/types'
+
+/**
+ * Instantly webhook payload structure
+ *
+ * Uses snake_case matching Instantly's API. Workflows receive this directly.
+ */
+export interface InstantlyReplyWebhookPayload {
+  timestamp: string
+  event_type: 'reply_received'
+  workspace: string
+  campaign_id: string
+  campaign_name?: string
+  lead_email: string
+  email_account: string
+  unibox_url: string
+  reply_to_uuid: string
+  reply_subject: string
+  reply_text: string
+  reply_text_snippet: string
+  reply_html: string
+  step: number
+  variant: number
+  is_first: boolean
+}
+
+/**
+ * Instantly Reply Received Trigger Definition
+ *
+ * Trigger type: webhook
+ * Provider: instantly
+ * Event: reply_received
+ */
+export const instantlyReplyReceivedTrigger: TriggerDefinition = {
+  resourceId: 'trigger-instantly-reply-received',
+  type: 'trigger',
+  triggerType: 'webhook',
+  name: 'Instantly Reply Received',
+  description: 'Webhook fired when a lead replies to an Instantly email campaign',
+  version: '1.0.0',
+  status: 'dev',
+  webhookPath: '/webhooks/instantly/reply-received',
+  config: {
+    provider: 'instantly',
+    event: 'reply_received'
+  } as WebhookTriggerConfig
+}

package/src/operations/triggers/webhook/index.ts

@@ -1,35 +1,35 @@
-/**
- * Webhook Triggers Module
- *
- * Webhooks are a type of trigger that start workflow executions
- * when external services send HTTP requests to Elevasis.
- *
- * This module contains:
- * - Provider interface for webhook signature validation (types only)
- * - Trigger definitions for specific webhook events
- *
- * Note: Provider IMPLEMENTATIONS live in apps/api/src/webhooks/providers/
- */
-
-// Provider interface and types (contract only - implementations in apps/api)
-export type { WebhookProvider, WebhookValidationResult } from './types'
-
-// Webhook trigger definitions
-export {
-  instantlyReplyReceivedTrigger,
-  type InstantlyReplyWebhookPayload
-} from './definitions/instantly-reply-received'
-export { instantlyEmailBouncedTrigger, type InstantlyEmailBouncedPayload } from './definitions/instantly-email-bounced'
-export {
-  instantlyLeadUnsubscribedTrigger,
-  type InstantlyLeadUnsubscribedPayload
-} from './definitions/instantly-lead-unsubscribed'
-export {
-  instantlyCampaignCompletedTrigger,
-  type InstantlyCampaignCompletedPayload
-} from './definitions/instantly-campaign-completed'
-export { instantlyAccountErrorTrigger, type InstantlyAccountErrorPayload } from './definitions/instantly-account-error'
-export {
-  instantlyAutoReplyReceivedTrigger,
-  type InstantlyAutoReplyReceivedPayload
-} from './definitions/instantly-auto-reply-received'
+/**
+ * Webhook Triggers Module
+ *
+ * Webhooks are a type of trigger that start workflow executions
+ * when external services send HTTP requests to Elevasis.
+ *
+ * This module contains:
+ * - Provider interface for webhook signature validation (types only)
+ * - Trigger definitions for specific webhook events
+ *
+ * Note: Provider IMPLEMENTATIONS live in apps/api/src/webhooks/providers/
+ */
+
+// Provider interface and types (contract only - implementations in apps/api)
+export type { WebhookProvider, WebhookValidationResult } from './types'
+
+// Webhook trigger definitions
+export {
+  instantlyReplyReceivedTrigger,
+  type InstantlyReplyWebhookPayload
+} from './definitions/instantly-reply-received'
+export { instantlyEmailBouncedTrigger, type InstantlyEmailBouncedPayload } from './definitions/instantly-email-bounced'
+export {
+  instantlyLeadUnsubscribedTrigger,
+  type InstantlyLeadUnsubscribedPayload
+} from './definitions/instantly-lead-unsubscribed'
+export {
+  instantlyCampaignCompletedTrigger,
+  type InstantlyCampaignCompletedPayload
+} from './definitions/instantly-campaign-completed'
+export { instantlyAccountErrorTrigger, type InstantlyAccountErrorPayload } from './definitions/instantly-account-error'
+export {
+  instantlyAutoReplyReceivedTrigger,
+  type InstantlyAutoReplyReceivedPayload
+} from './definitions/instantly-auto-reply-received'

package/src/operations/triggers/webhook/types.ts

@@ -1,74 +1,74 @@
-/**
- * Webhook Trigger type definitions
- *
- * These types define the contract for webhook providers that validate
- * signatures from external services (Cal.com, Fillout, Stripe, Instantly, etc.)
- *
- * Webhooks are a type of trigger - they start workflow executions
- * when external services send HTTP requests to Elevasis.
- *
- * Note: Provider IMPLEMENTATIONS live in apps/api/src/webhooks/providers/
- * This file only contains the interface contract.
- */
-
-import type { WebhookProviderType } from '../../../platform/registry/types'
-
-/**
- * Result of webhook signature validation
- */
-export interface WebhookValidationResult {
-  /** Whether the signature is valid */
-  isValid: boolean
-  /** Parsed payload if validation succeeded */
-  payload?: unknown
-  /** Error message if validation failed */
-  error?: string
-}
-
-/**
- * Webhook provider interface
- *
- * Each provider implements signature validation specific to their
- * webhook format (e.g., HMAC-SHA256 for Cal.com and Fillout).
- *
- * @example
- * ```typescript
- * class CalComProvider implements WebhookProvider {
- *   readonly providerId = 'cal-com' as const
- *
- *   async validateSignature(rawBody, headers, secret) {
- *     // HMAC-SHA256 validation
- *   }
- *
- *   getEventType(payload) {
- *     return payload.triggerEvent // e.g., 'BOOKING_CREATED'
- *   }
- * }
- * ```
- */
-export interface WebhookProvider {
-  /** Provider identifier (e.g., 'cal-com', 'fillout', 'stripe') */
-  readonly providerId: WebhookProviderType
-
-  /**
-   * Validate webhook signature and return parsed payload
-   *
-   * @param rawBody - Raw request body as string (before JSON parsing)
-   * @param headers - Request headers (lowercase keys)
-   * @param secret - Webhook signing secret from credentials
-   * @returns Validation result with parsed payload or error
-   */
-  validateSignature(
-    rawBody: string,
-    headers: Record<string, string>,
-    secret: string
-  ): Promise<WebhookValidationResult>
-
-  /**
-   * Extract event type from validated payload
-   *
-   * @param payload - Parsed webhook payload (from validateSignature)
-   * @returns Provider-specific event type (e.g., 'BOOKING_CREATED', 'invoice.paid')
-   */
-  getEventType(payload: unknown): string
-}
+/**
+ * Webhook Trigger type definitions
+ *
+ * These types define the contract for webhook providers that validate
+ * signatures from external services (Cal.com, Fillout, Stripe, Instantly, etc.)
+ *
+ * Webhooks are a type of trigger - they start workflow executions
+ * when external services send HTTP requests to Elevasis.
+ *
+ * Note: Provider IMPLEMENTATIONS live in apps/api/src/webhooks/providers/
+ * This file only contains the interface contract.
+ */
+
+import type { WebhookProviderType } from '../../../platform/registry/types'
+
+/**
+ * Result of webhook signature validation
+ */
+export interface WebhookValidationResult {
+  /** Whether the signature is valid */
+  isValid: boolean
+  /** Parsed payload if validation succeeded */
+  payload?: unknown
+  /** Error message if validation failed */
+  error?: string
+}
+
+/**
+ * Webhook provider interface
+ *
+ * Each provider implements signature validation specific to their
+ * webhook format (e.g., HMAC-SHA256 for Cal.com and Fillout).
+ *
+ * @example
+ * ```typescript
+ * class CalComProvider implements WebhookProvider {
+ *   readonly providerId = 'cal-com' as const
+ *
+ *   async validateSignature(rawBody, headers, secret) {
+ *     // HMAC-SHA256 validation
+ *   }
+ *
+ *   getEventType(payload) {
+ *     return payload.triggerEvent // e.g., 'BOOKING_CREATED'
+ *   }
+ * }
+ * ```
+ */
+export interface WebhookProvider {
+  /** Provider identifier (e.g., 'cal-com', 'fillout', 'stripe') */
+  readonly providerId: WebhookProviderType
+
+  /**
+   * Validate webhook signature and return parsed payload
+   *
+   * @param rawBody - Raw request body as string (before JSON parsing)
+   * @param headers - Request headers (lowercase keys)
+   * @param secret - Webhook signing secret from credentials
+   * @returns Validation result with parsed payload or error
+   */
+  validateSignature(
+    rawBody: string,
+    headers: Record<string, string>,
+    secret: string
+  ): Promise<WebhookValidationResult>
+
+  /**
+   * Extract event type from validated payload
+   *
+   * @param payload - Parsed webhook payload (from validateSignature)
+   * @returns Provider-specific event type (e.g., 'BOOKING_CREATED', 'invoice.paid')
+   */
+  getEventType(payload: unknown): string
+}

package/src/organization-model/README.md

@@ -1,97 +1,97 @@
-# Organization Model
-
-The organization model is the published semantic contract that maps a tenant's product shape to domain surfaces, features, and navigation.
-
-Use this module when you need to resolve or validate an organization's contract before wiring UI shells, routing, or domain-specific capability checks.
-
-## Published Exports
-
-The public entry point exposes:
-
-- `OrganizationModelSchema`
-- `DEFAULT_ORGANIZATION_MODEL`
-- `defineOrganizationModel`
-- `resolveOrganizationModel`
-- `PROJECTS_FEATURE_ID`
-- `PROJECTS_INDEX_SURFACE_ID`
-- `PROJECTS_VIEW_CAPABILITY_ID`
-- `OrganizationModel` and the supporting domain types
-
-Import it from the published subpath:
-
-```ts
-import {
-  DEFAULT_ORGANIZATION_MODEL,
-  PROJECTS_VIEW_CAPABILITY_ID,
-  defineOrganizationModel,
-  PROJECTS_FEATURE_ID,
-  PROJECTS_INDEX_SURFACE_ID,
-  resolveOrganizationModel,
-  type OrganizationModel
-} from '@elevasis/core/organization-model'
-```
-
-## Contract Shape
-
-The model is versioned and currently validates against `version: 1`.
-
-Top-level fields:
-
-- `version` - schema version for the resolved contract.
-- `branding` - organization branding defaults and overrides.
-- `features` - unified feature entries that combine enablement, labels, and semantic references.
-- `navigation` - navigation model for the product shell.
-- `sales` - sales pipeline and relationship management.
-- `prospecting` - lists, companies, and contacts.
-- `projects` - projects, milestones, and tasks.
-- `identity`, `customers`, `offerings`, `roles`, `goals` - reality domains (2026-04 expansion).
-- `statuses` - unified status registry across delivery / hitl / execution / request / schedule.
-- `operations` - catalog of stateful runtime entities (HITL queue, sessions, executions, notifications, schedules).
-- `resourceMappings` - cross-surface resource mappings (includes techStack subsection).
-
-## Default Feature Set
-
-The default model includes eight feature IDs:
-
-- `sales` - deal pipeline and relationship management.
-- `prospecting` - lists, companies, and contacts.
-- `projects` - projects, milestones, and tasks.
-- `operations` - organization graph and command-view surfaces.
-- `monitoring` - monitoring surfaces.
-- `settings` - organization settings.
-- `seo` - SEO surfaces (disabled by default).
-- `configure` - `/configure` skill entry point (external projects).
-
-## Project Bridge Constants
-
-The organization-model surface exports a narrow set of canonical IDs for the shared Projects bridge:
-
-- `PROJECTS_FEATURE_ID` -> `projects`
-- `PROJECTS_INDEX_SURFACE_ID` -> `projects.index`
-- `PROJECTS_VIEW_CAPABILITY_ID` -> `delivery.projects.view`
-
-Use these when wiring shared UI manifests, template adapters, or other consumers that need to agree on the same Projects contract without repeating raw literals.
-
-## Resolution Semantics
-
-- `defineOrganizationModel()` is a typed helper. It does not validate or merge anything by itself.
-- `resolveOrganizationModel()` deep-merges a partial override into the default model, then validates the result with `OrganizationModelSchema`.
-- Plain objects merge recursively.
-- Arrays replace the default value instead of merging element-by-element.
-- If `navigation.surfaces` is replaced without also supplying `navigation.groups`, inherited default groups are dropped when they no longer point at declared surfaces.
-- Missing fields fall back to `DEFAULT_ORGANIZATION_MODEL`.
-
-## Referential Integrity
-
-- `navigation.defaultSurfaceId` must point at a declared navigation surface.
-- Every navigation group `surfaceId` must resolve to a declared surface.
-- Feature, surface, and resource-mapping IDs must resolve to declared counterparts; dangling references fail validation.
-- Feature-to-surface and feature/surface-to-resource links are validated in both directions so one-sided declarations fail during resolution.
-- Feature-bearing surfaces validate `featureId` against the canonical feature set.
-
-## Practical Guidance
-
-- Use `resolveOrganizationModel()` when you need a runtime-safe model for rendering or policy checks.
-- Use `defineOrganizationModel()` when authoring a static partial model in source.
-- Treat feature IDs such as `sales`, `prospecting`, and `projects` as the canonical shell-level contract in new organization-model authoring.
-- Keep feature IDs, surface IDs, and capability IDs stable because downstream UI and policy code depend on them.
+# Organization Model
+
+The organization model is the published semantic contract that maps a tenant's product shape to domain surfaces, features, and navigation.
+
+Use this module when you need to resolve or validate an organization's contract before wiring UI shells, routing, or domain-specific capability checks.
+
+## Published Exports
+
+The public entry point exposes:
+
+- `OrganizationModelSchema`
+- `DEFAULT_ORGANIZATION_MODEL`
+- `defineOrganizationModel`
+- `resolveOrganizationModel`
+- `PROJECTS_FEATURE_ID`
+- `PROJECTS_INDEX_SURFACE_ID`
+- `PROJECTS_VIEW_CAPABILITY_ID`
+- `OrganizationModel` and the supporting domain types
+
+Import it from the published subpath:
+
+```ts
+import {
+  DEFAULT_ORGANIZATION_MODEL,
+  PROJECTS_VIEW_CAPABILITY_ID,
+  defineOrganizationModel,
+  PROJECTS_FEATURE_ID,
+  PROJECTS_INDEX_SURFACE_ID,
+  resolveOrganizationModel,
+  type OrganizationModel
+} from '@elevasis/core/organization-model'
+```
+
+## Contract Shape
+
+The model is versioned and currently validates against `version: 1`.
+
+Top-level fields:
+
+- `version` - schema version for the resolved contract.
+- `branding` - organization branding defaults and overrides.
+- `features` - unified feature entries that combine enablement, labels, and semantic references.
+- `navigation` - navigation model for the product shell.
+- `sales` - sales pipeline and relationship management.
+- `prospecting` - lists, companies, and contacts.
+- `projects` - projects, milestones, and tasks.
+- `identity`, `customers`, `offerings`, `roles`, `goals` - reality domains (2026-04 expansion).
+- `statuses` - unified status registry across delivery / hitl / execution / request / schedule.
+- `operations` - catalog of stateful runtime entities (HITL queue, sessions, executions, notifications, schedules).
+- `resourceMappings` - cross-surface resource mappings (includes techStack subsection).
+
+## Default Feature Set
+
+The default model includes eight feature IDs:
+
+- `sales` - deal pipeline and relationship management.
+- `prospecting` - lists, companies, and contacts.
+- `projects` - projects, milestones, and tasks.
+- `operations` - organization graph and command-view surfaces.
+- `monitoring` - monitoring surfaces.
+- `settings` - organization settings.
+- `seo` - SEO surfaces (disabled by default).
+- `configure` - `/configure` skill entry point (external projects).
+
+## Project Bridge Constants
+
+The organization-model surface exports a narrow set of canonical IDs for the shared Projects bridge:
+
+- `PROJECTS_FEATURE_ID` -> `projects`
+- `PROJECTS_INDEX_SURFACE_ID` -> `projects.index`
+- `PROJECTS_VIEW_CAPABILITY_ID` -> `delivery.projects.view`
+
+Use these when wiring shared UI manifests, template adapters, or other consumers that need to agree on the same Projects contract without repeating raw literals.
+
+## Resolution Semantics
+
+- `defineOrganizationModel()` is a typed helper. It does not validate or merge anything by itself.
+- `resolveOrganizationModel()` deep-merges a partial override into the default model, then validates the result with `OrganizationModelSchema`.
+- Plain objects merge recursively.
+- Arrays replace the default value instead of merging element-by-element.
+- If `navigation.surfaces` is replaced without also supplying `navigation.groups`, inherited default groups are dropped when they no longer point at declared surfaces.
+- Missing fields fall back to `DEFAULT_ORGANIZATION_MODEL`.
+
+## Referential Integrity
+
+- `navigation.defaultSurfaceId` must point at a declared navigation surface.
+- Every navigation group `surfaceId` must resolve to a declared surface.
+- Feature, surface, and resource-mapping IDs must resolve to declared counterparts; dangling references fail validation.
+- Feature-to-surface and feature/surface-to-resource links are validated in both directions so one-sided declarations fail during resolution.
+- Feature-bearing surfaces validate `featureId` against the canonical feature set.
+
+## Practical Guidance
+
+- Use `resolveOrganizationModel()` when you need a runtime-safe model for rendering or policy checks.
+- Use `defineOrganizationModel()` when authoring a static partial model in source.
+- Treat feature IDs such as `sales`, `prospecting`, and `projects` as the canonical shell-level contract in new organization-model authoring.
+- Keep feature IDs, surface IDs, and capability IDs stable because downstream UI and policy code depend on them.