Doghouse 2.0: build the PR flight recorder under Draft Punks

[flyingrobots]

Why

Draft Punks already solves the adjudication problem well: harvest the comments, force a decision, preserve the rationale.

What it does not yet solve well is the state reconstruction problem across pushes:

• what changed since the last meaningful PR sortie?
• what is actually blocking merge now?
• what should happen next?
• what is CodeRabbit doing right now, exactly?

Doghouse 2.0 should become the black box recorder underneath Draft Punks.

Draft Punks remains the conductor's score.
Doghouse becomes the recorder in the doghouse.

Seed Material

I seeded a first design bay on branch feat/doghouse-2-seed in commit fe78107.

Files:

• doghouse/README.md
• doghouse/flight-recorder-brief.md
• doghouse/playbacks.md
• README.md note
• planning hooks in docs/IDEAS.md, docs/FEATURES.md, and docs/TECH-SPEC.md

Build This

Please build Doghouse 2.0 as an agent-native PR flight recorder:

• local snapshot artifacts
• meaningful sortie episodes
• semantic delta comparisons against the last meaningful baseline
• machine-usable next_action verdicts
• reviewer-aware state, including CodeRabbit weirdness, without eclipsing human reviewers
• JSONL plumbing first, prettier porcelain later

Keep The Flavor

Do not flatten this into generic enterprise GitHub analytics mush.

Keep:

• BunBun
• PhiedBach
• the ritual feeling
• the worksheet system as the adjudication / conductor layer

But give that ritual a stronger mechanic underneath it.

Non-Goals

• not a full replacement for the worksheet flow
• not org-wide analytics
• not a boring dashboard farm
• not a replacement for GitHub itself

First Success Condition

A Draft Punks operator should be able to answer, in under a minute:

• what changed since the last push
• which complaints are actually new
• whether the PR is waiting on checks, waiting on review, or actually merge-ready