/dashboard, Harness Observability Dashboard

When to Use

• "What's happening?" / "Status?" / "What's going on?"
• "Show activity" / "Show me the dashboard"
• After returning to a project after time away
• When /do routes "status", "dashboard", "what's happening", "what's going on", "show activity"
• Directly: /dashboard

Inputs

None required. Works with whatever state exists on disk.

Protocol

Step 0: RUN DASHBOARD IMPLEMENTATION

Run the local dashboard implementation from the project root:

node scripts/dashboard.js

If the package scripts are available, this equivalent command is also valid:

npm run dashboard

The script is read-only. It renders a user-facing control-plane snapshot from .planning/, telemetry, hook config, coordination state, worktrees, and cost data. Use the manual collection protocol below only as a fallback if the script is missing or fails in the current project.

Step 1: COLLECT STATE

Read the following sources. Each is optional, if a file or directory doesn't exist, treat it as empty. Never crash on missing state.

Campaigns:

• Glob .planning/campaigns/*.md
• For each file, read the first 40 lines to extract:
  • Status: field
  • Direction: field (truncate to 60 chars)
  • Phase progress (search for Phase N of M or ## Phase headings)
  • Most recent line starting with - [ from the Decision Log
• If all phases are complete but status is still active, report needs-completion and show: node scripts/campaign.js complete <slug> --archive
• If a campaign is marked completed but still lives in .planning/campaigns/, report needs-archive and show the same archive command.
• If prior build/verify phases are complete but the review-package Exit Evidence row is still pending, missing, or points at a missing local package, report a repair before campaign completion: node scripts/package-delivery.js <slug>

Cost Data (two sources, prefer real):