Skip to content

Epic: v0.8 native Code Mower Board #494

Description

@jeffhuber

Goal

Turn the v0.7 board MVP into Code Mower's native transparency layer: a local-first control room for lane activity, reviewer evidence, spend, latency, owner escalations, and historical run state.

Scope

  • Stable local board/event schema for PRs, lanes, verdicts, checks, workflow runs, spend, latency, and next actions.
  • Local event store under .code-mower/board using metadata-only JSONL or SQLite.
  • Live updates via polling or server-sent events.
  • Rich lane and PR timeline views.
  • Owner escalation queue and weekly/digest-style visibility.
  • Optional agent adapters for Claude, Codex, Cursor/Grok Bot, Antigravity, Devin, and reviewers, each metadata-only and opt-in.
  • CodeMower.com display parity for uploaded metadata, while keeping the server backward-compatible with existing beta uploads.
  • Admin tooling: board doctor, board open, safe reset, port selection, redaction controls.

Proposed Child Issues

  1. Board data contract v1 and docs/cloud-data-contract alignment for any upload shape changes.
  2. Local event store with retention and redaction rules.
  3. Live board updates from GitHub checks, labels, workflow runs, and local Code Mower artifacts.
  4. Spend/latency and reviewer verdict timeline panels.
  5. Owner queue panel for needs-owner, blocked audits, stale gates, and next action.
  6. Optional metadata-only agent adapters.
  7. CodeMower.com board mirror using the same metadata contract.
  8. Board doctor/admin commands.
  9. Public demo/rehearsal artifact for adoption announcement.

Acceptance Criteria

  • Operators can answer what is active, what is blocked, what is waiting, what it cost, and what to do next from one local board.
  • The board remains useful if GitHub is temporarily unavailable by showing local artifacts and clearly marking remote state unavailable.
  • All adapters are opt-in, metadata-only, and non-mutating unless a command explicitly says otherwise.
  • CodeMower.com consumes only documented metadata and remains backward-compatible with v0.6/v0.7 uploads.

Privacy Boundary

No source, raw diffs, transcripts, issue body text, raw stdout/stderr, auth output, browser history, or secrets. Local paths are redacted by default in shareable views.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestepicEpic tracking issuev0.8Code Mower v0.8 release line

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions