feat(telemetry): Integrate telemetry for expand-all, aggregate results
This commit implements AI usage telemetry for the `expand-all-tasks` command/tool and refactors its CLI output for clarity and consistency. Key Changes: 1. **Telemetry Integration for `expand-all-tasks` (Subtask 77.8):**\n - The `expandAllTasks` core logic (`scripts/modules/task-manager/expand-all-tasks.js`) now calls the `expandTask` function for each eligible task and collects the individual `telemetryData` returned.\n - A new helper function `_aggregateTelemetry` (in `utils.js`) is used to sum up token counts and costs from all individual expansions into a single `telemetryData` object for the entire `expand-all` operation.\n - The `expandAllTasksDirect` wrapper (`mcp-server/src/core/direct-functions/expand-all-tasks.js`) now receives and passes this aggregated `telemetryData` in the MCP response.\n - For CLI usage, `displayAiUsageSummary` is called once with the aggregated telemetry. 2. **Improved CLI Output for `expand-all`:**\n - The `expandAllTasks` core function now handles displaying a final "Expansion Summary" box (showing Attempted, Expanded, Skipped, Failed counts) directly after the aggregated telemetry summary.\n - This consolidates all summary output within the core function for better flow and removes redundant logging from the command action in `scripts/modules/commands.js`.\n - The summary box border is green for success and red if any expansions failed. 3. **Code Refinements:**\n - Ensured `chalk` and `boxen` are imported in `expand-all-tasks.js` for the new summary box.\n - Minor adjustments to logging messages for clarity.
This commit is contained in:
@@ -9,3 +9,41 @@ Update the Taskmaster installation scripts and documentation to support Bun as a
|
||||
|
||||
# Test Strategy:
|
||||
1. Install Taskmaster using Bun on macOS, Linux, and Windows (including WSL and PowerShell), following the updated documentation. 2. Run the full installation and initialization process, verifying that the directory structure, templates, and MCP config are set up identically to npm, pnpm, and Yarn. 3. Execute all CLI commands (including 'init') and confirm functional parity. 4. If a website or account setup is required, test these flows for consistency; if not, confirm and document this. 5. Check for Bun-specific issues (e.g., install hangs) and verify that troubleshooting steps are effective. 6. Ensure the documentation is clear, accurate, and up to date for all supported platforms.
|
||||
|
||||
# Subtasks:
|
||||
## 1. Research Bun compatibility requirements [pending]
|
||||
### Dependencies: None
|
||||
### Description: Investigate Bun's JavaScript runtime environment and identify key differences from Node.js that may affect Taskmaster's installation and operation.
|
||||
### Details:
|
||||
Research Bun's package management, module resolution, and API compatibility with Node.js. Document any potential issues or limitations that might affect Taskmaster. Identify required changes to make Taskmaster compatible with Bun's execution model.
|
||||
|
||||
## 2. Update installation scripts for Bun compatibility [pending]
|
||||
### Dependencies: 65.1
|
||||
### Description: Modify the existing installation scripts to detect and support Bun as a runtime environment.
|
||||
### Details:
|
||||
Add Bun detection logic to installation scripts. Update package management commands to use Bun equivalents where needed. Ensure all dependencies are compatible with Bun. Modify any Node.js-specific code to work with Bun's runtime.
|
||||
|
||||
## 3. Create Bun-specific installation path [pending]
|
||||
### Dependencies: 65.2
|
||||
### Description: Implement a dedicated installation flow for Bun users that optimizes for Bun's capabilities.
|
||||
### Details:
|
||||
Create a Bun-specific installation script that leverages Bun's performance advantages. Update any environment detection logic to properly identify Bun environments. Ensure proper path resolution and environment variable handling for Bun.
|
||||
|
||||
## 4. Test Taskmaster installation with Bun [pending]
|
||||
### Dependencies: 65.3
|
||||
### Description: Perform comprehensive testing of the installation process using Bun across different operating systems.
|
||||
### Details:
|
||||
Test installation on Windows, macOS, and Linux using Bun. Verify that all Taskmaster features work correctly when installed via Bun. Document any issues encountered and implement fixes as needed.
|
||||
|
||||
## 5. Test Taskmaster operation with Bun [pending]
|
||||
### Dependencies: 65.4
|
||||
### Description: Ensure all Taskmaster functionality works correctly when running under Bun.
|
||||
### Details:
|
||||
Test all Taskmaster commands and features when running with Bun. Compare performance metrics between Node.js and Bun. Identify and fix any runtime issues specific to Bun. Ensure all plugins and extensions are compatible.
|
||||
|
||||
## 6. Update documentation for Bun support [pending]
|
||||
### Dependencies: 65.4, 65.5
|
||||
### Description: Update all relevant documentation to include information about installing and running Taskmaster with Bun.
|
||||
### Details:
|
||||
Add Bun installation instructions to README and documentation. Document any Bun-specific considerations or limitations. Update troubleshooting guides to include Bun-specific issues. Create examples showing Bun usage with Taskmaster.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user