chore: task management - moves 87,88,89 to 90,91,92

tasks/task_090.txt

@@ -1,4 +1,4 @@
-# Task ID: 87
+# Task ID: 90
 # Title: Implement Comprehensive Telemetry Improvements for Task Master
 # Status: in-progress
 # Dependencies: 2, 3, 17

tasks/task_091.txt

@@ -1,4 +1,4 @@
-# Task ID: 88
+# Task ID: 91
 # Title: Integrate Gateway AI Service Mode into ai-services-unified.js
 # Status: pending
 # Dependencies: 2, 3, 17
@@ -32,25 +32,25 @@
 Implement a configuration option that allows users to select between BYOK (Bring Your Own Key) and hosted gateway modes during system initialization. Create appropriate configuration parameters and storage mechanisms to persist this selection. Ensure the configuration is accessible throughout the application, particularly in ai-services-unified.js.
 
 ## 2. Implement gateway mode detection in ai-services-unified.js [pending]
-### Dependencies: 88.1
+### Dependencies: 91.1
 ### Description: Add logic to detect when the hosted gateway mode is active and prepare the system for gateway-specific processing.
 ### Details:
 Modify ai-services-unified.js to check the configuration and determine if the system is operating in gateway mode. Create helper functions to facilitate gateway-specific operations. Ensure this detection happens early in the processing flow to properly route subsequent operations.
 
 ## 3. Refactor AI call flow for gateway integration [pending]
-### Dependencies: 88.2
+### Dependencies: 91.2
 ### Description: Modify the AI call flow to intercept requests and route them to the gateway endpoint when in gateway mode.
 ### Details:
 Refactor the existing AI call flow to intercept requests before _resolveApiKey and _attemptProviderCallWithRetries methods are called. When gateway mode is active, construct appropriate gateway requests containing the full messages array, modelId, roleParams, and commandName. Implement the routing logic to direct these requests to the gateway endpoint instead of directly to the provider.
 
 ## 4. Implement gateway response handling and telemetry [pending]
-### Dependencies: 88.3
+### Dependencies: 91.3
 ### Description: Develop logic to parse gateway responses, extract AI results, and handle gateway-specific telemetry data.
 ### Details:
 Create functions to parse responses from the gateway, extracting the AI result and handling telemetry fields for credits used/remaining instead of tokens/costs. Update the internal telemetry handling system to support both gateway and traditional formats. Ensure all relevant metrics are captured and properly stored.
 
 ## 5. Implement error handling, logging, and documentation [pending]
-### Dependencies: 88.4
+### Dependencies: 91.4
 ### Description: Add comprehensive logging, error handling, and update documentation for the gateway integration.
 ### Details:
 Implement robust error handling and fallback logic for gateway failures. Add detailed logging for gateway interactions, including request/response payloads and credit telemetry, using the existing logging system. Update documentation to describe the new gateway mode, configuration options, and how the system behaves differently when in gateway mode versus BYOK mode. Ensure the command structure and response handling remain compatible with existing provider integrations.

tasks/task_092.txt

@@ -1,4 +1,4 @@
-# Task ID: 89
+# Task ID: 92
 # Title: Task Master Gateway Integration
 # Status: pending
 # Dependencies: None

tasks/tasks.json

@@ -5794,7 +5794,7 @@
       ]
     },
     {
-      "id": 87,
+      "id": 90,
       "title": "Implement Comprehensive Telemetry Improvements for Task Master",
       "description": "Enhance Task Master with robust telemetry capabilities, including secure capture of command arguments and outputs, remote telemetry submission, DAU and active user tracking, extension to non-AI commands, and opt-out preferences during initialization.",
       "details": "1. Instrument all CLI commands (including non-AI commands) to capture execution metadata, command arguments, and outputs, ensuring that sensitive data is never exposed in user-facing responses or logs. Use in-memory redaction and encryption techniques to protect sensitive information before transmission.\n2. Implement a telemetry client that securely sends anonymized and aggregated telemetry data to the remote endpoint (gateway.task-master.dev/telemetry) using HTTPS/TLS. Ensure data is encrypted in transit and at rest, following best practices for privacy and compliance.\n3. Track daily active users (DAU) and active user sessions by generating anonymized user/session identifiers, and aggregate usage metrics to analyze user patterns and feature adoption.\n4. Extend telemetry instrumentation to all command types, not just AI-powered commands, ensuring consistent and comprehensive observability across the application.\n5. During Task Master initialization, prompt users with clear opt-out options for telemetry collection, store their preferences securely, and respect these settings throughout the application lifecycle.\n6. Design telemetry payloads to support future analysis of user patterns, operational costs, and to provide data for potential custom AI model training, while maintaining strict privacy standards.\n7. Document the internal instrumentation policy, including guidelines for data collection, aggregation, and export, and automate as much of the instrumentation as possible to ensure consistency and minimize manual errors.\n8. Ensure minimal performance impact by implementing efficient sampling, aggregation, and rate limiting strategies within the telemetry pipeline.",
@@ -5814,7 +5814,7 @@
           "details": "Update ai-services-unified.js to capture the initial args passed to the AI service and the full output. Modify the telemetryData object structure to include 'commandArgs' and 'fullOutput' fields. Ensure handleApiResult in MCP and displayAiUsageSummary in CLI do not expose these fields to end users.",
           "status": "pending",
           "dependencies": [],
-          "parentTaskId": 87
+          "parentTaskId": 90
         },
         {
           "id": 2,
@@ -5823,7 +5823,7 @@
           "details": "Create a telemetry submission service that POSTs to gateway.task-master.dev/telemetry. Include all existing telemetry fields plus commandArgs and fullOutput. Implement retry logic and handle failures gracefully without blocking command execution. Respect user opt-out preferences.",
           "status": "pending",
           "dependencies": [],
-          "parentTaskId": 87
+          "parentTaskId": 90
         },
         {
           "id": 3,
@@ -5832,7 +5832,7 @@
           "details": "Ensure userId generation is consistent and persistent. Track command execution timestamps to calculate DAU. Include session tracking to understand user engagement patterns. Add fields for tracking unique daily users, command frequency, and session duration.",
           "status": "pending",
           "dependencies": [],
-          "parentTaskId": 87
+          "parentTaskId": 90
         },
         {
           "id": 4,
@@ -5841,7 +5841,7 @@
           "details": "Create a unified telemetry collection mechanism for all commands in commands.js. Track command name, execution time, success/failure status, and basic metrics. Ensure non-AI commands generate appropriate telemetry without AI-specific fields like tokens or costs.",
           "status": "pending",
           "dependencies": [],
-          "parentTaskId": 87
+          "parentTaskId": 90
         },
         {
           "id": 5,
@@ -5850,12 +5850,12 @@
           "details": "Add a prompt during task-master init that asks users if they want to opt-out of telemetry (default: no/continue with telemetry). Store the preference as 'telemetryOptOut: boolean' in .taskmasterconfig. Ensure all telemetry collection respects this setting. Include clear explanation of what data is collected and why.",
           "status": "pending",
           "dependencies": [],
-          "parentTaskId": 87
+          "parentTaskId": 90
         }
       ]
     },
     {
-      "id": 88,
+      "id": 91,
       "title": "Integrate Gateway AI Service Mode into ai-services-unified.js",
       "description": "Implement support for a hosted AI gateway service in Task Master, allowing users to select between BYOK and hosted gateway modes during initialization. Ensure gateway integration intercepts and routes AI calls appropriately, handles gateway-specific telemetry, and maintains compatibility with existing command structures.",
       "details": "1. Update the initialization logic to allow users to select between BYOK (Bring Your Own Key) and hosted gateway service modes, storing the selection in the configuration system.\n2. In ai-services-unified.js, detect when the hosted gateway mode is active.\n3. Refactor the AI call flow to intercept requests before _resolveApiKey and _attemptProviderCallWithRetries. When in gateway mode, route calls to the gateway endpoint instead of directly to the provider.\n4. Construct gateway requests with the full messages array, modelId, roleParams, and commandName, ensuring all required data is passed.\n5. Parse gateway responses, extracting the AI result and handling telemetry fields for credits used/remaining instead of tokens/costs. Update internal telemetry handling to support both formats.\n6. Ensure the command structure and response handling remain compatible with existing provider integrations, so downstream consumers are unaffected.\n7. Add comprehensive logging for gateway interactions, including request/response payloads and credit telemetry, leveraging the existing logging system.\n8. Maintain robust error handling and fallback logic for gateway failures.\n9. Update documentation to describe the new gateway mode and configuration options.",
@@ -5875,7 +5875,8 @@
           "dependencies": [],
           "details": "Implement a configuration option that allows users to select between BYOK (Bring Your Own Key) and hosted gateway modes during system initialization. Create appropriate configuration parameters and storage mechanisms to persist this selection. Ensure the configuration is accessible throughout the application, particularly in ai-services-unified.js.",
           "status": "pending",
-          "testStrategy": "Create unit tests that verify the configuration is correctly set and retrieved based on user selection. Test both BYOK and gateway mode configurations."
+          "testStrategy": "Create unit tests that verify the configuration is correctly set and retrieved based on user selection. Test both BYOK and gateway mode configurations.",
+          "parentTaskId": 91
         },
         {
           "id": 2,
@@ -5886,7 +5887,8 @@
           ],
           "details": "Modify ai-services-unified.js to check the configuration and determine if the system is operating in gateway mode. Create helper functions to facilitate gateway-specific operations. Ensure this detection happens early in the processing flow to properly route subsequent operations.",
           "status": "pending",
-          "testStrategy": "Write tests that confirm the system correctly identifies when it's in gateway mode versus BYOK mode based on the configuration set in subtask 1."
+          "testStrategy": "Write tests that confirm the system correctly identifies when it's in gateway mode versus BYOK mode based on the configuration set in subtask 1.",
+          "parentTaskId": 91
         },
         {
           "id": 3,
@@ -5897,7 +5899,8 @@
           ],
           "details": "Refactor the existing AI call flow to intercept requests before _resolveApiKey and _attemptProviderCallWithRetries methods are called. When gateway mode is active, construct appropriate gateway requests containing the full messages array, modelId, roleParams, and commandName. Implement the routing logic to direct these requests to the gateway endpoint instead of directly to the provider.",
           "status": "pending",
-          "testStrategy": "Create integration tests that verify requests are correctly intercepted and routed to the gateway endpoint when in gateway mode, and to the provider directly when in BYOK mode."
+          "testStrategy": "Create integration tests that verify requests are correctly intercepted and routed to the gateway endpoint when in gateway mode, and to the provider directly when in BYOK mode.",
+          "parentTaskId": 91
         },
         {
           "id": 4,
@@ -5908,7 +5911,8 @@
           ],
           "details": "Create functions to parse responses from the gateway, extracting the AI result and handling telemetry fields for credits used/remaining instead of tokens/costs. Update the internal telemetry handling system to support both gateway and traditional formats. Ensure all relevant metrics are captured and properly stored.",
           "status": "pending",
-          "testStrategy": "Test the response parsing with various mock gateway responses, verifying that AI results are correctly extracted and telemetry data is properly processed for both gateway and traditional formats."
+          "testStrategy": "Test the response parsing with various mock gateway responses, verifying that AI results are correctly extracted and telemetry data is properly processed for both gateway and traditional formats.",
+          "parentTaskId": 91
         },
         {
           "id": 5,
@@ -5919,12 +5923,13 @@
           ],
           "details": "Implement robust error handling and fallback logic for gateway failures. Add detailed logging for gateway interactions, including request/response payloads and credit telemetry, using the existing logging system. Update documentation to describe the new gateway mode, configuration options, and how the system behaves differently when in gateway mode versus BYOK mode. Ensure the command structure and response handling remain compatible with existing provider integrations.",
           "status": "pending",
-          "testStrategy": "Test error scenarios by simulating gateway failures and verifying proper fallback behavior. Review logs to ensure appropriate information is captured. Conduct a documentation review to verify completeness and accuracy."
+          "testStrategy": "Test error scenarios by simulating gateway failures and verifying proper fallback behavior. Review logs to ensure appropriate information is captured. Conduct a documentation review to verify completeness and accuracy.",
+          "parentTaskId": 91
         }
       ]
     },
     {
-      "id": 89,
+      "id": 92,
       "title": "Task Master Gateway Integration",
       "description": "Integrate Task Master with premium gateway services for enhanced testing and git workflow capabilities",
       "details": "Add gateway integration to Task Master (open source) that enables users to access premium AI-powered test generation, TDD orchestration, and smart git workflows through API key authentication. Maintains local file operations while leveraging remote AI intelligence.",
@@ -5940,7 +5945,7 @@
           "details": "Implement configuration management for API keys, endpoint URLs, and feature flags. Create HTTP client wrapper with authentication, error handling, and retry logic.",
           "status": "pending",
           "dependencies": [],
-          "parentTaskId": 89
+          "parentTaskId": 92
         },
         {
           "id": 2,
@@ -5949,7 +5954,7 @@
           "details": "Create command that gathers local context (code, tasks, patterns), sends to gateway API for intelligent test generation, then writes generated tests to local filesystem with proper structure.",
           "status": "pending",
           "dependencies": [],
-          "parentTaskId": 89
+          "parentTaskId": 92
         },
         {
           "id": 3,
@@ -5958,7 +5963,7 @@
           "details": "Build TDD state machine that manages test phases, integrates with test watchers, and provides real-time feedback during development cycles.",
           "status": "pending",
           "dependencies": [],
-          "parentTaskId": 89
+          "parentTaskId": 92
         },
         {
           "id": 4,
@@ -5967,7 +5972,7 @@
           "details": "Create git workflow automation including branch management, smart commit message generation via gateway API, and PR creation with comprehensive descriptions.",
           "status": "pending",
           "dependencies": [],
-          "parentTaskId": 89
+          "parentTaskId": 92
         },
         {
           "id": 5,
@@ -5976,7 +5981,7 @@
           "details": "Add fields for test files, coverage data, git branches, commit history, and TDD phase tracking to task structure.",
           "status": "pending",
           "dependencies": [],
-          "parentTaskId": 89
+          "parentTaskId": 92
         },
         {
           "id": 6,
@@ -5985,7 +5990,7 @@
           "details": "Implement MCP tools that expose test generation and TDD workflow commands to IDEs like Cursor, enabling seamless integration with development environment.",
           "status": "pending",
           "dependencies": [],
-          "parentTaskId": 89
+          "parentTaskId": 92
         },
         {
           "id": 7,
@@ -5994,7 +5999,7 @@
           "details": "Implement pattern detection that analyzes existing test files to understand project conventions, naming patterns, and testing approaches for consistency.",
           "status": "pending",
           "dependencies": [],
-          "parentTaskId": 89
+          "parentTaskId": 92
         },
         {
           "id": 8,
@@ -6003,7 +6008,7 @@
           "details": "Connect with Jest, NYC, and other coverage tools to analyze test coverage, identify gaps, and suggest improvements through gateway API.",
           "status": "pending",
           "dependencies": [],
-          "parentTaskId": 89
+          "parentTaskId": 92
         },
         {
           "id": 9,
@@ -6012,7 +6017,7 @@
           "details": "Build test watcher that monitors test results and automatically transitions between TDD phases (red/green/refactor) based on test outcomes.",
           "status": "pending",
           "dependencies": [],
-          "parentTaskId": 89
+          "parentTaskId": 92
         },
         {
           "id": 10,
@@ -6021,7 +6026,7 @@
           "details": "Implement graceful degradation when gateway API is unavailable, falling back to local AI models or basic functionality while maintaining core Task Master features.",
           "status": "pending",
           "dependencies": [],
-          "parentTaskId": 89
+          "parentTaskId": 92
         }
       ]
     }