@walwal-harness/cli 7.1.32 → 7.1.33

package/HR-Resource/cdo/SKILL.md

@@ -25,6 +25,10 @@ Before design work, read `.harness/conventions/shared.md`, `.harness/conventions
 8. Select the final direction and write a CDO preview artifact at `.harness/documents/{mission_name}/cdo/preview.html`.
 9. Report to CEO and CTO with a concise preview summary and mention that the visual sample is available in the dashboard by clicking harness-cdo.
 
+## Worker Activity Telemetry
+
+Before launching any fresh worker session, update `.harness/progress.json` with `scripts/harness-progress-set.sh` so dashboards can show the worker as active. Record the worker name, owning CXX, report path, and `status:"running"` under `company_state.workers`, increment `company_state.active_workers`, and set `conductor.current_action` to `spawn:{worker-name}`. After the worker report is accepted, update that worker to `status:"complete"` and decrement `active_workers`. Do not leave `active_workers:0` while a worker session is running.
+
 ## Rule
 
 Design output must be usable by implementation teams, not just descriptive.

package/HR-Resource/coo/SKILL.md

@@ -35,6 +35,10 @@ During planning, COO must determine whether the active runtime exposes MCP serve
 7. Review worker reports against the goal.
 8. Reassign work or report to CEO.
 
+## Worker Activity Telemetry
+
+Before launching any fresh worker session, update `.harness/progress.json` with `scripts/harness-progress-set.sh` so dashboards can show the worker as active. Record the worker name, owning CXX, report path, and `status:"running"` under `company_state.workers`, increment `company_state.active_workers`, and set `conductor.current_action` to `spawn:{worker-name}`. After the worker report is accepted, update that worker to `status:"complete"` and decrement `active_workers`. Do not leave `active_workers:0` while a worker session is running.
+
 ## Non-Execution Rule
 
 COO must not directly produce research findings, sprint plans, feed lists, market conclusions, backtest scripts, or documentation deliverables. COO may only frame the question, select and brief workers, evaluate worker output, and record the accepted decision.

package/HR-Resource/cqo/SKILL.md

@@ -24,6 +24,10 @@ Before quality work, read `.harness/conventions/shared.md`, `.harness/convention
 7. Monitor repeated issues and promote verified lessons to `.harness/conventions`, `.harness/gotchas`, `.harness/memories`, or `.harness/shared`.
 8. Approve or reject archive based solely on worker-provided evidence and OPS runtime/watch evidence when the mission uses a runnable environment.
 
+## Worker Activity Telemetry
+
+Before launching any fresh worker session, update `.harness/progress.json` with `scripts/harness-progress-set.sh` so dashboards can show the worker as active. Record the worker name, owning CXX, report path, and `status:"running"` under `company_state.workers`, increment `company_state.active_workers`, and set `conductor.current_action` to `spawn:{worker-name}`. After the worker report is accepted, update that worker to `status:"complete"` and decrement `active_workers`. Do not leave `active_workers:0` while a worker session is running.
+
 ## Hard Rules
 
 CQO must not directly execute QA, visual review, security review, performance testing, or regression checks. CQO may only define gates, select evaluators, review evidence, decide archive eligibility, and document worker names and report paths.

package/HR-Resource/cto/SKILL.md

@@ -26,6 +26,10 @@ Before engineering work, read `.harness/conventions/shared.md`, `.harness/conven
 9. Delegate all implementation and technical deliverables to hired workers in fresh sessions.
 10. Collect reports, resolve blockers, and hand completed work to CQO.
 
+## Worker Activity Telemetry
+
+Before launching any fresh worker session, update `.harness/progress.json` with `scripts/harness-progress-set.sh` so dashboards can show the worker as active. Record the worker name, owning CXX, report path, and `status:"running"` under `company_state.workers`, increment `company_state.active_workers`, and set `conductor.current_action` to `spawn:{worker-name}`. After the worker report is accepted, update that worker to `status:"complete"` and decrement `active_workers`. Do not leave `active_workers:0` while a worker session is running.
+
 ## Hard Rules
 
 CTO must not directly write code, create build scripts, choose detailed implementation content, run technical QA as the evaluator, or produce final implementation artifacts. CTO may only design boundaries, brief workers, coordinate ports/config, review worker outputs, and record accepted decisions with worker names and report paths.

package/HR-Resource/ops/SKILL.md

@@ -66,6 +66,10 @@ After service launch, OPS continues the same monitoring duty against `runtime.pr
 10. Classify exceptions as verification, build, backend, frontend, platform, external API, infrastructure, owner-config, production, or unknown.
 11. Raise emergency events to CEO/CTO/CQO with evidence and the mapped environment record.
 
+## Worker Activity Telemetry
+
+Before launching any fresh worker session, update `.harness/progress.json` with `scripts/harness-progress-set.sh` so dashboards can show the worker as active. Record the worker name, owning CXX, report path, and `status:"running"` under `company_state.workers`, increment `company_state.active_workers`, and set `conductor.current_action` to `spawn:{worker-name}`. After the worker report is accepted, update that worker to `status:"complete"` and decrement `active_workers`. Do not leave `active_workers:0` while a worker session is running.
+
 ## Required Output Sections
 
 1. Worker Task Briefs — monitoring/recovery task, capability needed, selected worker or hiring request, acceptance criteria.

package/README.md

@@ -283,6 +283,7 @@ harness-hiring           → register and onboard worker
 
 | Version | Summary |
 |---|---|
+| 7.1.33 | Dashboard keeps recently written worker reports active even when docmeta is present, and CXX skills now record worker activity telemetry for live dashboard state |
 | 7.1.31 | Persist dashboard heatmap activity to 7-day JSONL logs, load persisted samples in the dashboard, and backfill activity during migrate from existing mission docs/progress logs |
 | 7.1.29 | Idempotent AGENTS/CLAUDE doc merge with marked harness sections, mission lifecycle backfill for init/migrate, completion closes todos and mission-state, and Layer Activity now lists CXX/worker rows sorted by remaining work |
 | 7.1.28 | Dashboard APM rewrite: top header consolidation, Knowledge Base panel (gotchas/conventions), Layer Activity (CEO/CXX/Worker TODO·DONE·Remain via goal-scope inference), Recent Report list (worker mtime desc), Cadence strip with click-to-prompt tooltip in local timezone, heatmap click-tooltip with empty-cell guard, Document Viewer expand-to-50vw with docmeta hidden, Command Log bubble popover |

package/apps/harness-dashboard/lib/__tests__/harness-state.test.ts

@@ -381,4 +381,30 @@ describe("readHarnessState", () => {
       active: false,
     });
   });
+
+  it("keeps recently written docmeta worker reports active without an explicit COMPLETE marker", () => {
+    const harnessDir = path.join(dir, ".harness");
+    const missionDir = path.join(harnessDir, "documents", "goal-1-dashboard");
+    mkdirSync(path.join(missionDir, "cto", "workers"), { recursive: true });
+    writeFileSync(path.join(missionDir, "ceo.md"), "# Dashboard\n");
+    writeFileSync(
+      path.join(missionDir, "cto", "workers", "frontend-worker.md"),
+      "---\ndocmeta:\n  id: frontend-worker\n---\n\n# Worker Report\n\nEvidence is still being appended.\n"
+    );
+    writeFileSync(
+      path.join(harnessDir, "progress.json"),
+      JSON.stringify({
+        current_agent: "ceo",
+        agent_status: "running",
+        company_state: { active_workers: 0, workers: [] },
+      })
+    );
+
+    const workers = readHarnessState(dir).missions[0].workers;
+    expect(workers[0]).toMatchObject({
+      name: "frontend-worker",
+      status: "IN_PROGRESS",
+      active: true,
+    });
+  });
 });

package/apps/harness-dashboard/lib/harness-state.ts

@@ -1220,16 +1220,6 @@ function readMissions(rootDir: string, progress: RawProgress | null = null, limi
             if (!f.endsWith(".md")) continue;
             const reportAbs = path.join(missionPath, relDir, f);
             const content = readMd(`${relDir}/${f}`) ?? "";
-            const statusMatch = content.match(/##\s*Status\s*\n+([A-Z_]+)/);
-            // Worker docs sometimes omit the "## Status" block but always carry a
-            // docmeta frontmatter when the worker submitted its output. Treat the
-            // presence of a docmeta block (or a non-empty body) as COMPLETE.
-            const hasDocmeta = /^---[\s\S]*?docmeta:[\s\S]*?---/.test(content);
-            const status: WorkerDocEntry["status"] = statusMatch
-              ? (statusMatch[1] as WorkerDocEntry["status"])
-              : hasDocmeta
-              ? "COMPLETE"
-              : "unknown";
             const name = normalizeWorkerName(f);
             const hired = hiredForMission(hiredWorkers, name, owner, rel);
             let updatedAt: string | null = null;
@@ -1239,6 +1229,18 @@ function readMissions(rootDir: string, progress: RawProgress | null = null, limi
               updatedAt = mtime.toISOString();
               recentlyTouched = Date.now() - mtime.getTime() < RECENT_WORKER_ACTIVE_MS;
             } catch { /* ignore */ }
+            const statusMatch = content.match(/##\s*Status\s*\n+([A-Z_]+)/);
+            const hasDocmeta = /^---[\s\S]*?docmeta:[\s\S]*?---/.test(content);
+            // Worker docs often write docmeta before appending final evidence.
+            // Without an explicit COMPLETE marker, keep recent writes visible as
+            // active; after the activity window they become historical reports.
+            const status: WorkerDocEntry["status"] = statusMatch
+              ? (statusMatch[1] as WorkerDocEntry["status"])
+              : hasDocmeta && recentlyTouched && !runtimeIdle
+              ? "IN_PROGRESS"
+              : hasDocmeta
+              ? "COMPLETE"
+              : "unknown";
             const entry: WorkerDocEntry = {
               name,
               displayName: workerDisplayName(content, hired, name),
@@ -1246,7 +1248,7 @@ function readMissions(rootDir: string, progress: RawProgress | null = null, limi
               status,
               owner: hired?.owner ?? owner,
               hired: !!hired,
-              active: !runtimeIdle && (activeWorkers.has(name) || (recentlyTouched && status !== "COMPLETE")),
+              active: !runtimeIdle && (activeWorkers.has(name) || status === "IN_PROGRESS"),
               sourcePath: hired?.sourcePath ?? null,
               reportPath: path.relative(rootDir, reportAbs),
               updatedAt,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@walwal-harness/cli",
-  "version": "7.1.32",
+  "version": "7.1.33",
   "description": "Company-style AI agent harness for Claude and Codex. Installs commands, CXX agents, skills, HR-Resource hiring pool, and project-local .harness runtime state.",
   "bin": {
     "walwal-harness": "bin/init.js"