@seeka-labs/cli-apps 3.8.2 → 3.8.6

package/dist/init-template/README.azurefunc.md

@@ -39,7 +39,7 @@ See `AGENTS.md` for AI assistant instructions.
 #### Hydrate Seeka AI context
 Below command will download the latest context files to `.seeka/ai/context/` directory to provide guidance for your app development.
 
-`npx @seeka-labs/cli-apps ai context`
+`npx @seeka-labs/cli-apps@latest ai context`
 
 ## Local Development
 

package/dist/init-template/app/browser/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@example-org-name/example-app-name-browser",
-  "version": "3.8.1",
+  "version": "3.8.6",
   "description": "Seeka app browser plugin example-app-name",
   "author": "Seeka company <support@seeka.co>",
   "private": true,

package/dist/init-template/app/lib/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@example-org-name/example-app-name-lib",
-  "version": "3.8.1",
+  "version": "3.8.6",
   "description": "Seeka app library for example-app-name",
   "author": "Seeka <administrator@seeka.co>",
   "license": "MIT",

package/dist/init-template/app/server-azurefunc/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@example-org-name/example-app-name-server-azurefunc",
-  "version": "3.8.1",
+  "version": "3.8.6",
   "description": "Seeka Azure Serverless function app example-app-name",
   "author": "Seeka <administrator@seeka.co>",
   "license": "MIT",

package/dist/init-template/app/ui/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@example-org-name/example-app-name-ui",
-  "version": "3.8.1",
+  "version": "3.8.6",
   "description": "Seeka app UI for example-app-name",
   "author": "Seeka <administrator@seeka.co>",
   "license": "MIT",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@seeka-labs/cli-apps",
-  "version": "3.8.2",
+  "version": "3.8.6",
   "type": "module",
   "description": "Seeka - Apps CLI",
   "author": "SEEKA <platform@seeka.co>",
@@ -28,6 +28,8 @@
     "build:ci": "yarn build:templates && tsc --noEmit && esbuild src/index.ts --bundle --sourcemap --platform=node --target=node22 --outfile=dist/index.cjs",
     "build": "yarn build:templates && tsc --noEmit && esbuild src/index.ts --bundle --sourcemap --platform=node --target=node22 --outfile=dist/index.cjs",
     "build:templates": "ts-node scripts/build-templates.ts",
+    "ai:context:run": "yarn build && node dist/index.cjs ai context",
+    "cli:run": "yarn build && node dist/index.cjs",
     "watch": "tsc -w",
     "clean": "rimraf dist",
     "dev": "yarn run clean && yarn build && rimraf seeka-app-test1 && node dist/index.cjs init seeka-app-test1 --template azure-function --email 'dev@seeka.co' --developer Seeka --noDependencies --browser --npmUsername testy --npmPassword passworddd --env 'SEEKA_APP_ID=123' 'SEEKA_APP_SECRET=345' --packageManager yarn",
@@ -63,7 +65,8 @@
     "lodash-es": "^4",
     "source-map-support": "^0",
     "ts-jest": "^29",
+    "ts-node": "^10",
     "typescript": "^5"
   },
-  "gitHead": "af02a0413272e165016fcaab2e3b35579abaec9b"
+  "gitHead": "7bb14ccbd1859349c57898ff0ab5b62394cf07b1"
 }

package/dist/ai-context/internal/architecture/v1-structure.md

@@ -1,192 +0,0 @@
-# V1 App Template Structure (Legacy)
-
-> **⚠️ Legacy Version**: V1 is no longer used for new apps. This documentation is provided for reference when examining existing V1 apps for feature implementation patterns.
-
-## Overview
-
-V1 apps were the first generation of Seeka apps. They are **single-package Azure Functions apps** (not monorepos) with all code in a flat `src/` directory structure.
-
-## Key Differences from V3
-
-| Aspect | V1 | V3 |
-|--------|----|----|
-| Structure | Single package, flat `src/` | Monorepo with `app/` workspaces |
-| Azure Functions | V4 programming model | V4 programming model |
-| Shared code | In `src/lib/` within same package | Separate `app/lib/` package |
-| Browser plugin | Nested in `src/browser/` (if present) | Separate `app/browser/` package |
-| UI component | Not present | Separate `app/ui/` package |
-| Build system | tsc | esbuild with optimizations |
-| Configuration | `host.json` at root | `host.json` in `app/server/` |
-
-## V1 Directory Structure
-
-V1 apps have two main variants:
-
-### Standard V1 (Azure Functions)
-
-Most V1 apps follow this structure:
-
-```
-your-app-name/
-├── src/
-│   ├── functions/                    # Azure Function handlers
-│   │   ├── seekaAppWebhook.ts        # Main Seeka webhook
-│   │   ├── healthCheck.ts            # Health check endpoint
-│   │   └── [platformWebhook].ts      # Platform-specific webhooks (optional)
-│   ├── lib/                          # Business logic and utilities
-│   │   ├── logging/
-│   │   │   └── index.ts              # Winston logging setup
-│   │   ├── services/
-│   │   │   └── index.ts              # Business logic services
-│   │   ├── state/
-│   │   │   ├── seeka/
-│   │   │   │   └── installations.ts  # Installation state management
-│   │   │   └── redis/
-│   │   │       └── index.ts          # Redis client setup
-│   │   ├── jobs/
-│   │   │   └── index.ts              # Background job definitions (optional)
-│   │   ├── models/
-│   │   │   └── index.ts              # TypeScript interfaces (optional)
-│   │   └── [platform-name]/          # Platform-specific API clients
-│   │       ├── api/
-│   │       │   └── index.ts
-│   │       └── [feature]/
-│   │           └── index.ts
-│   └── browser/                      # Browser plugin (optional, nested package)
-│       ├── src/
-│       │   ├── browser.ts
-│       │   └── plugin/
-│       │       └── index.ts
-│       ├── package.json
-│       ├── tsconfig.json
-│       └── README.md
-├── host.json                         # Azure Functions host configuration
-├── local.settings.json               # Local development settings (gitignored)
-├── package.json                      # Single package.json for entire app
-├── tsconfig.json
-└── README.md
-```
-
-### Express-based V1 (Alternative)
-
-Some V1 apps use Express instead of Azure Functions:
-
-```
-your-app-name/
-├── src/
-│   ├── app/
-│   │   └── index.ts                  # Express app setup
-│   ├── routes/                       # Express route handlers
-│   │   ├── seekaAppWebhook.ts
-│   │   └── [platformWebhook].ts
-│   ├── lib/                          # Same structure as above
-│   │   └── ...
-│   └── index.ts                      # Entry point
-├── package.json
-├── tsconfig.json
-└── README.md
-```
-
-## Example V1 Apps by Category
-
-### Server-only Apps (No Browser Plugin)
-- **activecampaign** - CRM integration with ActiveCampaign
-- **nowbookit** - Booking platform integration
-- **klaviyo-events** (early version pattern)
-
-### Apps with Browser Plugin
-- **complianz** - Cookie consent management
-- **sevenrooms** - Restaurant reservation platform
-- **tradable-bits** - Fan engagement platform
-- **transcend** - Privacy/consent management
-
-### Express-based Apps
-- **ivvy** - Event venue management (uses Express routes)
-
-## Key V1 Patterns
-
-### Installation State Management
-
-V1 apps typically manage installation state in `src/lib/state/seeka/installations.ts`:
-
-```typescript
-// src/lib/state/seeka/installations.ts
-import { createClient } from 'redis';
-
-export interface AppInstallContext {
-    applicationInstallId: string;
-    organisationId: string;
-    organisationBrandId: string;
-    installedAt: string;
-    installationState?: {
-        grantedPermissions: string[];
-        installationSettings: AppInstallationSettings;
-    };
-}
-
-export const getInstallation = async (installId: string): Promise<AppInstallContext | null> => {
-    // Redis-based installation lookup
-};
-
-export const saveInstallation = async (installation: AppInstallContext): Promise<void> => {
-    // Redis-based installation storage
-};
-```
-
-### Platform API Clients
-
-V1 apps organize platform-specific code in `src/lib/[platform-name]/`:
-
-```typescript
-// src/lib/active-campaign/api/index.ts
-export class ActiveCampaignClient {
-    constructor(private apiUrl: string, private apiKey: string) {}
-
-    async createContact(contact: ContactData): Promise<Contact> {
-        // API implementation
-    }
-}
-```
-
-### Browser Plugin (Nested Package)
-
-When present, the browser plugin is a nested package within `src/browser/`:
-
-```typescript
-// src/browser/src/plugin/index.ts
-export class AppBrowserPlugin {
-    constructor(config: PluginConfig) {
-        // Initialize plugin
-    }
-
-    // Plugin methods for browser-side functionality
-}
-```
-
-## When to Reference V1 Apps
-
-V1 apps contain valuable implementation patterns for:
-
-- **External API integrations**: How specific platforms (ActiveCampaign, SevenRooms, etc.) were integrated
-- **Data transformation logic**: Converting Seeka activity data to platform-specific formats
-- **Webhook handling**: Receiving and processing webhooks from external platforms
-- **Queue-based processing**: Background job patterns for async operations
-- **Redis state management**: Installation and session state patterns
-
-## Adapting V1 Patterns to V3
-
-When using V1 code as reference for a new V3 app:
-
-1. **Move shared types** from `src/lib/models/` to `app/lib/src/models/`
-2. **Move validation logic** to `app/lib/src/validation/`
-3. **Move services** from `src/lib/services/` to `app/server/src/app/services/`
-4. **Move API routes** to `app/server/src/app/api/routes/`
-5. **Use SDK utilities** from `@seeka-labs/sdk-apps-server-host` instead of custom implementations
-6. **Replace custom logging** with the SDK's winston-based logging setup
-7. **Move browser plugin** from `src/browser/` to `app/browser/`
-
-## See Also
-
-- `v2-structure.md` - V2 legacy structure (monorepo introduction)
-- `v3-structure.md` - Current template structure (use for new apps)
-- `../examples/v1/` - V1 example apps for feature reference

package/dist/ai-context/internal/architecture/v2-structure.md

@@ -1,261 +0,0 @@
-# V2 App Template Structure (Legacy)
-
-> **⚠️ Legacy Version**: V2 is no longer used for new apps. This documentation is provided for reference when examining existing V2 apps for feature implementation patterns.
-
-## Overview
-
-V2 apps introduced the **monorepo structure** with separate packages for server, UI, and browser components. V2 apps use Azure Functions V4 programming model (same as V3) but organize code differently.
-
-## Key Differences from V3
-
-| Aspect | V2 | V3 |
-|--------|----|----|
-| Shared library | Code in `app/server/src/lib/` | Separate `app/lib/` package |
-| Server structure | `src/functions/` + `src/lib/` | `src/functions/` + `src/app/` |
-| Business logic | Mixed in `src/lib/` | Organized in `src/app/` subdirs |
-| SDK usage | Custom implementations | Uses `@seeka-labs/sdk-apps-server-host` |
-| CLI config | Not present | `.seeka/` directory with config |
-
-## V2 Directory Structure
-
-```
-your-app-name/
-├── app/
-│   ├── browser/                          # Browser plugin (optional)
-│   │   ├── src/
-│   │   │   ├── browser.ts                # Browser entry point
-│   │   │   └── plugin/
-│   │   │       └── index.ts              # Plugin implementation
-│   │   ├── package.json
-│   │   ├── tsconfig.json
-│   │   └── README.md
-│   ├── server/                           # Azure Functions server
-│   │   ├── src/
-│   │   │   ├── functions/                # Azure Function handlers
-│   │   │   │   ├── seekaAppWebhook.ts    # Main Seeka webhook
-│   │   │   │   ├── healthCheck.ts        # Health check endpoint
-│   │   │   │   ├── ui.ts                 # UI static file serving
-│   │   │   │   ├── [platform]Webhook.ts  # Platform webhooks (optional)
-│   │   │   │   ├── [platform]Auth*.ts    # OAuth handlers (optional)
-│   │   │   │   └── *QueueHandler.ts      # Queue processors (optional)
-│   │   │   └── lib/                      # Business logic (V2 style)
-│   │   │       ├── logging/
-│   │   │       │   └── index.ts          # Winston logging setup
-│   │   │       ├── services/
-│   │   │       │   └── index.ts          # Business logic services
-│   │   │       ├── state/
-│   │   │       │   ├── seeka/
-│   │   │       │   │   └── installations.ts
-│   │   │       │   └── redis/
-│   │   │       │       └── index.ts
-│   │   │       ├── jobs/
-│   │   │       │   └── index.ts          # Background job definitions
-│   │   │       ├── models/
-│   │   │       │   └── index.ts          # TypeScript interfaces
-│   │   │       ├── browser/
-│   │   │       │   └── index.ts          # Browser plugin config
-│   │   │       ├── api/                  # REST API routes (optional)
-│   │   │       │   ├── auth.ts
-│   │   │       │   └── routes/
-│   │   │       │       └── *.ts
-│   │   │       └── [platform-name]/      # Platform-specific code
-│   │   │           └── *.ts
-│   │   ├── host.json                     # Azure Functions host config
-│   │   ├── local.settings.json           # Local dev settings (gitignored)
-│   │   ├── package.json
-│   │   ├── tsconfig.json
-│   │   └── README.md
-│   └── ui/                               # Configuration UI (optional)
-│       ├── src/
-│       │   ├── main.tsx                  # React entry point
-│       │   ├── App.tsx                   # Main App component
-│       │   ├── vite-env.d.ts
-│       │   └── seeka-labs-app-sdk-ui/    # Shared UI utilities
-│       │       ├── utils/
-│       │       └── shared/
-│       ├── public/
-│       │   └── manifest.json
-│       ├── scripts/
-│       │   └── copy-output.mjs
-│       ├── package.json
-│       ├── tsconfig.json
-│       ├── tsconfig.node.json
-│       ├── vite.config.ts
-│       └── README.md
-├── .vscode/                              # VS Code configuration (optional)
-│   ├── launch.json
-│   ├── settings.json
-│   ├── extensions.json
-│   └── tasks.json
-├── package.json                          # Root package.json (workspaces)
-├── tsconfig.json                         # Root TypeScript config
-└── README.md
-```
-
-## Example V2 Apps by Category
-
-### Full-featured Apps (Server + UI + Browser)
-- **calendly** - Calendar scheduling integration with OAuth
-- **typeform** - Form/survey integration with OAuth
-
-### Server + UI Apps (No Browser)
-- **webhook** - Generic inbound webhook handler
-- **yeastar** - Phone system CRM integration
-
-### Server-only Apps
-- **klaviyo-events** - Email marketing event tracking
-- **google-bigquery** - Data warehouse integration
-- **navitas** - Education platform integration
-
-### Browser-focused Apps
-- **clarity** - Microsoft Clarity analytics (browser + server)
-- **trustarc** - Privacy/consent management (browser + server)
-
-## Key V2 Patterns
-
-### Function Definition (V2 uses V4 programming model)
-
-V2 apps use the same Azure Functions V4 programming model as V3:
-
-```typescript
-// app/server/src/functions/seekaAppWebhook.ts
-import { app, HttpRequest, HttpResponseInit, InvocationContext } from '@azure/functions';
-
-app.http('seekaAppWebhook', {
-    methods: ['POST'],
-    authLevel: 'anonymous',
-    route: 'api/webhook/seeka/app',
-    handler: seekaAppWebhook
-});
-
-export async function seekaAppWebhook(
-    req: HttpRequest,
-    context: InvocationContext
-): Promise<HttpResponseInit> {
-    const body = JSON.parse(await req.text());
-    // Process webhook...
-    return { status: 204 };
-}
-```
-
-### Queue Handler Pattern
-
-```typescript
-// app/server/src/functions/handleSeekaActivityQueueHandler.ts
-import { app, InvocationContext } from '@azure/functions';
-
-app.storageQueue('handleSeekaActivityQueueHandler', {
-    queueName: 'seeka-activity-queue',
-    connection: 'AzureWebJobsStorage',
-    handler: async (queueItem: unknown, context: InvocationContext) => {
-        // Process queued item
-    }
-});
-```
-
-### Installation State (V2 Custom Implementation)
-
-V2 apps typically have custom installation management in `src/lib/state/`:
-
-```typescript
-// app/server/src/lib/state/seeka/installations.ts
-import { getRedisClient } from '../redis';
-
-export interface AppInstallContext {
-    applicationInstallId: string;
-    organisationId: string;
-    organisationBrandId: string;
-    installedAt: string;
-    installationState?: {
-        grantedPermissions: string[];
-        installationSettings: AppInstallationSettings;
-    };
-}
-
-export const getInstallation = async (installId: string): Promise<AppInstallContext | null> => {
-    const redis = await getRedisClient();
-    const data = await redis.get(`installation:${installId}`);
-    return data ? JSON.parse(data) : null;
-};
-```
-
-### API Routes Pattern
-
-V2 apps with UI typically have API routes in `src/lib/api/`:
-
-```typescript
-// app/server/src/lib/api/routes/setTrackingSettings.ts
-import { HttpRequest, HttpResponseInit } from '@azure/functions';
-import { getInstallation, saveInstallation } from '../../state/seeka/installations';
-
-export const setTrackingSettings = async (
-    req: HttpRequest,
-    installId: string
-): Promise<HttpResponseInit> => {
-    const body = await req.json();
-    const installation = await getInstallation(installId);
-    // Update settings...
-    await saveInstallation(installation);
-    return { status: 200, jsonBody: { success: true } };
-};
-```
-
-### UI Component Pattern
-
-V2 UIs use React with Vite and shared UI utilities:
-
-```typescript
-// app/ui/src/App.tsx
-import { useTokens } from './seeka-labs-app-sdk-ui/shared/auth/useTokens';
-
-function App() {
-    const { accessToken, installationId } = useTokens();
-
-    // Render configuration UI
-}
-```
-
-## When to Reference V2 Apps
-
-V2 apps are excellent references for:
-
-- **Monorepo organization**: How to structure multi-package apps
-- **UI configuration patterns**: React-based settings UIs with Vite
-- **OAuth integration flows**: Platform authentication (Calendly, Typeform, Google)
-- **API route patterns**: REST endpoints for UI communication
-- **Browser plugin architecture**: Plugin structure and server communication
-- **Queue-based processing**: Async activity processing patterns
-
-## Adapting V2 Patterns to V3
-
-When using V2 code as reference for a new V3 app:
-
-1. **Create `app/lib/` package** for shared code instead of keeping it in `app/server/src/lib/`
-2. **Move models** from `app/server/src/lib/models/` to `app/lib/src/models/`
-3. **Move validation** to `app/lib/src/validation/`
-4. **Reorganize server code**:
-   - Move `src/lib/services/` to `src/app/services/`
-   - Move `src/lib/api/` to `src/app/api/`
-   - Move `src/lib/jobs/` to `src/app/jobs/`
-   - Move `src/lib/logging/` to `src/app/logging/`
-5. **Use SDK utilities** from `@seeka-labs/sdk-apps-server-host`:
-   - Replace custom `getInstallation`/`saveInstallation` with SDK functions
-   - Use SDK logging setup instead of custom winston config
-6. **Add `.seeka/` directory** with `init.app.seeka.cli.config.json`
-
-## Migration Checklist: V2 → V3
-
-- [ ] Create `app/lib/` package with `package.json` and `tsconfig.json`
-- [ ] Move shared models and validation to `app/lib/src/`
-- [ ] Reorganize `app/server/src/lib/` to `app/server/src/app/`
-- [ ] Update imports to use `app/lib` package
-- [ ] Replace custom installation management with SDK utilities
-- [ ] Add `.seeka/init.app.seeka.cli.config.json`
-- [ ] Update SDK packages to latest versions
-- [ ] Test all endpoints, queue handlers, and UI
-
-## See Also
-
-- `v1-structure.md` - V1 legacy structure (single package)
-- `v3-structure.md` - Current template structure (use for new apps)
-- `../examples/v2/` - V2 example apps for feature reference