feat: add CLI reporter plugin

[thalesraymond]

Implemented the add-cli-reporter change to introduce a real-time, structured CLI reporting utility as an installable TaskRunner plugin. Includes fully passing vitest coverage and satisfies all original proposal specifications.

---

PR created automatically by Jules for task 18189689605612180723 started by @thalesraymond

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[gemini-code-assist]

Code Review

This pull request introduces the CLIReporterPlugin, which provides real-time CLI reporting for task execution progress and a final summary of results. The plugin is integrated into the main package exports and includes comprehensive unit tests. Feedback focuses on improving state management within the plugin to prevent stale data during concurrent or repeated executions by moving state variables into the method scope. Additionally, it is recommended to replace process.nextTick with Promise.resolve() in tests to improve portability and consistency with the microtask queue.

[gemini-code-assist]

The plugin currently stores execution state as class members. To prevent stale data across multiple initializations or concurrent executions, ensure all state-holding members are cleared or move state into the method scope. This aligns with the repository rule regarding stateful class initialization.

  public install(context: PluginContext<TContext>): void {
    let startTime = 0;

    context.events.on("workflowStart", () => {
      startTime = performance.now();
      console.log("\n🚀 Starting TaskRunner workflow...");
    });

    context.events.on("taskStart", ({ step }) => {
      console.log(`⏳ Starting: ${step.name}`);
    });

    context.events.on("taskEnd", ({ step, result }) => {
      if (result.status === "success") {
        console.log(`✅ Success: ${step.name}`);
      } else {
        console.log(`❌ Failed:  ${step.name}${result.error ? ` - ${result.error}` : ""}`);
      }
    });

    context.events.on("taskSkipped", ({ step, result }) => {
      const reason = result.error ? ` - ${result.error}` : "";
      console.log(`⏭️  Skipped: ${step.name}${reason}`);
    });

    context.events.on("workflowEnd", ({ results }) => {
      const duration = performance.now() - startTime;
      let successCount = 0;
      let failureCount = 0;
      let skippedCount = 0;

      for (const result of results.values()) {
        if (result.status === "success") successCount++;
        else if (result.status === "failure") failureCount++;
        else if (result.status === "skipped") skippedCount++;
      }

      console.log(`\n🏁 Workflow Completed in ${duration.toFixed(2)}ms`);
      console.log("📊 Summary:");
      console.log(`   ✅ Success: ${successCount}`);
      console.log(`   ❌ Failed:  ${failureCount}`);
      console.log(`   ⏭️  Skipped: ${skippedCount}\n`);
    });
  }

References

1. When implementing an initialize or reset method in a stateful class, ensure all state-holding members are cleared to prevent stale data across multiple initializations.

[gemini-code-assist]

Using process.nextTick in tests makes them dependent on the Node.js environment. Since the EventBus uses queueMicrotask, it is better to use await Promise.resolve() to wait for the microtask queue to flush. This improves test portability.

Suggested change

	await new Promise(process.nextTick);
	await Promise.resolve();