@seeka-labs/cli-apps 3.8.5 → 3.8.6

package/dist/ai-context/internal/examples/v3/google-ads/_ai-summary.md

@@ -1,28 +1,33 @@
 ```markdown
-# AI Summary: Google Ads Conversion Tracking App
+# AI Summary for Google Ads Seeka App
 
 ## Purpose and Functionality
-The `google-ads` app is designed to facilitate Google Ads conversion tracking and offline conversion import. It receives activity data from Seeka and pushes conversions to Google Ads using the Google Ads API. This app is particularly useful for tracking and managing advertising conversions, both online and offline, within the Google Ads ecosystem.
+The Google Ads Seeka app is designed to facilitate conversion tracking and offline conversion imports for Google Ads. It receives activity data from Seeka and communicates these conversions to Google Ads using the Google Ads API. This integration helps advertisers track the effectiveness of their campaigns by linking offline activities to online conversions.
 
 ## Key Implementation Patterns
-- **Monorepo Structure**: The app uses a monorepo setup with Yarn workspaces, organizing the code into multiple components: browser, UI, and server.
-- **Azure Functions**: The server-side logic is deployed as Azure Functions, allowing for scalable and event-driven execution.
-- **Webhook Handling**: The app processes various webhook events from Seeka, such as app installation, uninstallation, and activity acceptance, to manage Google Ads conversions.
-- **Concurrent Development**: Utilizes `concurrently` for parallel execution of development tasks, enabling simultaneous server, UI, and browser plugin development.
+- **Monorepo Structure**: The app uses a monorepo setup with Yarn workspaces, organizing the codebase into distinct components: browser, UI, and server.
+- **Azure Functions**: The server-side logic is deployed as Azure Functions, enabling scalable and event-driven execution.
+- **Webhook Handling**: The app processes various webhook events from Seeka, such as app installation, uninstallation, and activity acceptance, to manage conversion tracking and app state.
+- **Concurrent Processes**: The app utilizes `concurrently` to run multiple processes in parallel, such as server, UI, and browser plugin development.
 
 ## External APIs/Services Integrated
-- **Google Ads API**: The app integrates with the Google Ads API to push conversion data and manage Google Ads accounts.
-- **Azure Storage Queue**: Used for queueing and processing conversion tracking jobs asynchronously.
-- **Seeka SDK**: Utilizes Seeka's SDK for handling webhook payloads and managing app installations.
+- **Google Ads API**: The core functionality of the app revolves around integrating with the Google Ads API to track and import conversions.
+- **Azure Storage Queues**: Used for managing background jobs and processing conversion data asynchronously.
+- **Seeka SDK**: Utilizes Seeka's SDK for handling app installation contexts and webhook payloads.
 
 ## Important Data Transformations
-- **Activity to Conversion Mapping**: The app transforms Seeka activity data into Google Ads conversion actions using defined mappings (`SeekaActivityToGoogleConversionActionMapping`).
-- **Webhook Payload Processing**: Webhook payloads are parsed and validated to ensure secure and accurate data handling before triggering conversion actions.
+- **Activity to Conversion Mapping**: The app defines mappings between Seeka activities and Google Ads conversion actions, enabling precise tracking of specific user activities as conversions.
+- **Webhook Payload Processing**: Incoming webhook payloads are validated and transformed into actionable tasks, such as updating installation states or triggering conversion tracking.
 
 ## Notable Code Patterns
-- **Validation with Logger**: The `validateInstallationSettings` function uses a logger to provide detailed feedback during the validation of installation settings, ensuring robust error handling.
-- **Asynchronous Job Processing**: Conversion activities are processed asynchronously using Azure Storage Queues, allowing for scalable and efficient handling of large volumes of conversion data.
-- **Environment Configuration via GitHub Actions**: Deployment configurations are managed through GitHub Actions, utilizing environment variables and secrets for secure and flexible deployment to Azure Functions.
+- **TypeScript Interfaces and Types**: The app extensively uses TypeScript for defining data models and ensuring type safety across components.
+- **Logging with Winston**: The app employs the Winston library for structured logging, facilitating easier debugging and monitoring.
+- **Environment Configuration**: The app uses environment variables and GitHub secrets for configuration, ensuring secure and flexible deployments.
 
-This app exemplifies a robust integration of cloud services, asynchronous processing, and API interactions to deliver a comprehensive solution for Google Ads conversion tracking.
-```
+## Reusable Code Patterns
+- **Webhook Signature Validation**: A reusable pattern for validating webhook signatures to ensure secure communication.
+- **Concurrent Development Scripts**: The use of `concurrently` for parallel process management can be adapted for other projects requiring simultaneous execution of multiple components.
+- **Azure Function Deployment via GitHub Actions**: The deployment workflow using GitHub Actions and Azure Functions can be a template for other serverless applications.
+
+This summary provides an overview of the Google Ads Seeka app's architecture and implementation, highlighting key patterns and integrations that could be useful for similar applications.
+```

package/dist/index.cjs

@@ -39932,7 +39932,7 @@ var os2 = __toESM(require("os"), 1);
 var path6 = __toESM(require("path"), 1);
 
 // package.json
-var version = "3.8.5";
+var version = "3.8.6";
 
 // src/helpers/index.ts
 var fs2 = __toESM(require("fs"), 1);
@@ -48774,7 +48774,7 @@ async function extractZipToDirectory(zipBuffer, destDir) {
 var aiContextCommand = async (options = {}) => {
   const targetDir = options.targetDir || process.cwd();
   const contextDestDir = path5.join(targetDir, ".seeka", "ai", "context");
-  const contextUrl = getContextPackageUrl(options.targetDir, options.contextPackageUrl);
+  const contextUrl = getContextPackageUrl(targetDir, options.contextPackageUrl);
   console.log("Seeka AI Context");
   console.log("================");
   console.log("");
@@ -52549,7 +52549,7 @@ var buildProgram = () => {
       // appSettings: options.appSettings ? map(stringArrayToMap(options.appSettings), (k, v) => { return { name: k } }) : [],
       npmUsername: options.npmUsername,
       npmPassword: options.npmPassword,
-      contextPackageUrl: options.contextPackageUrl
+      contextPackageUrl: getContextPackageUrl(void 0, options.contextPackageUrl)
     };
     await initCommandV2(initOptions);
   }).showHelpAfterError(true);