Skip to content

Paseo work dashboard — surface the autonomous loop's runs/PRs/pass-fail (extend RFC 0016) #60

Description

@amiller

There's a fleet-of-apps console coming (RFC 0016 / #20 / PR #48), but no dashboard for the fleet of work — what the async Paseo loop is doing. Today the only surface is ad-hoc HTML dropped in reports/ (batch-latest.html, paseo-batch-staging, staging-mirror-qa). You can't see at a glance: which issues are in flight, which staging-NN PRs are open/merged, last run + pass/fail, what got built/verified on webhost-staging.

Proposal: extend the RFC 0016 console with a 'work' view (or a sibling surface):

  • open issues by label (p1/p2/ready/needs-human) ↔ the staging-NN branch/PR each maps to
  • last N loop runs: issue, branch, verify result (webhost-staging), PR link, status (open/merged/failed)
  • roll up the reports/*.html the loop already emits instead of them being loose files
  • read-only + agent-readable JSON (same shape as RFC 0016's status endpoint)

Ties to RFC 0023 (the loop) + RFC 0016 (the console). Could be folded into #48 or a follow-on. Filed per owner request; unlabeled so it's triaged before the loop picks it up.

Acceptance

A single work page lists the autonomous loops recent runs, PRs (with merge + pass/fail state), and the ready/operator-ask queue, generated from gh+ lane logs. It shows a per-section **last-run timestamp** and renders any section >24h stale in RED. It replaces the ad-hocreports/` HTML. This is folded into the one Evidence Report (paseo-batch Phase 5), not a new surface.

Metadata

Metadata

Assignees

No one assigned

    Labels

    operator-askAndrew asked for this in-session; swarm drains these first

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions