fix: Ensure we broadcast test results on github

Author: Quenty

docs/testing/testing.md

@@ -257,4 +257,5 @@ For CI, set `ROBLOSECURITY` as a repository or Codespace secret. The `.github/wo
 - **Workflows should be thin.** All logic lives in `nevermore-cli` commands — GitHub Actions workflows just call them. This keeps CI debuggable locally.
 - **Rate limiting** is shared across concurrent workers via the `OpenCloudClient` instance. The `RateLimiter` serializes all Open Cloud API requests (one in-flight at a time) and reads `x-ratelimit-remaining` / `x-ratelimit-reset` headers.
 - **Post results via CLI**: `nevermore tools post-test-results <file>` posts or updates a PR comment with test results and writes to the GitHub Actions job summary. Requires `GITHUB_TOKEN` for PR comments; job summaries are written automatically when `GITHUB_STEP_SUMMARY` is set.
-- **Job summaries**: Results are automatically written to the [GitHub Actions job summary](https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-commands#adding-a-job-summary) when running in CI. This makes results visible on the workflow run summary page, complementing the PR comment.
+- **Live comment updates during the run**: When `nevermore batch test` detects a CI environment, it also updates the PR comment as packages transition between phases (throttled to ~10s). The `post-test-results` step still writes the final snapshot, but reviewers see progress without waiting for the full run to finish. In `--aggregated` mode every package shares one execution, so they move through `uploading` → `scheduling` → `executing` in lock-step — that's expected, not a bug.
+- **Job summaries**: Results are automatically written to the [GitHub Actions job summary](https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-commands#adding-a-job-summary) when running in CI. This makes results visible on the workflow run summary page, complementing the PR comment. The job summary is only written by `post-test-results` (not by the live batch run) to avoid duplicate entries on the workflow summary page.

tools/nevermore-cli/src/commands/batch-command/batch-test-command.ts

@@ -26,10 +26,12 @@ import {
   type BatchTestResult,
   type BatchTestSummary,
   CompositeReporter,
+  GithubCommentTableReporter,
   GroupedReporter,
   JsonFileReporter,
   SpinnerReporter,
   SummaryTableReporter,
+  createTestCommentConfig,
 } from '../../utils/testing/reporting/index.js';
 import {
   runSingleTestAsync,
@@ -174,6 +176,15 @@ async function _runAsync(args: BatchTestArgs): Promise<void> {
       if (args.output) {
         reporters.push(new JsonFileReporter(state, args.output));
       }
+      if (isCI()) {
+        reporters.push(
+          new GithubCommentTableReporter(
+            state,
+            createTestCommentConfig(),
+            concurrency
+          )
+        );
+      }
       return reporters;
     }
   );
@@ -273,17 +284,28 @@ function _createBroadcastReporter(
   target: Reporter,
   packageNames: string[]
 ): Reporter {
+  // Phases from the inner context apply to the whole batch in aggregated mode.
+  // The cloud poll loop re-fires 'executing' on every poll tick, and we don't
+  // want that to keep flushing identical updates downstream — dedupe on the
+  // last broadcast phase so each transition is reported exactly once.
+  let lastBroadcastPhase: JobPhase | undefined;
   return {
     startAsync: async () => {},
     stopAsync: async () => {},
     onPackageStart: () => {},
     onPackageResult: () => {},
     onPackagePhaseChange: (_name: string, phase: JobPhase) => {
+      if (lastBroadcastPhase === phase) return;
+      lastBroadcastPhase = phase;
       for (const name of packageNames) {
         target.onPackagePhaseChange(name, phase);
       }
     },
     onPackageProgressUpdate: (_name: string, progress: ProgressSummary) => {
+      // Upload progress (byte transfer) is genuinely informative when fanned
+      // out. Poll progress during 'executing' is just an incrementing counter
+      // duplicated across every row, so skip it once we're in lock-step.
+      if (lastBroadcastPhase === 'executing') return;
       for (const name of packageNames) {
         target.onPackageProgressUpdate(name, progress);
       }