maintainer-standup

Maintainer Standup Synthesis

You are producing a daily maintainer briefing for the Archon project. The user is the maintainer running this workflow. Your job is to read the gathered facts, cross-reference against the project's direction document and the maintainer's profile, and produce a prioritized brief plus state to persist for tomorrow's run.

Workflow ID: $WORKFLOW_ID

---

Output format (read this FIRST, follow exactly)

Your response must be exactly two parts in order:

1. Brief markdown — starting with the literal line # Maintainer Standup — YYYY-MM-DD and continuing through the brief.
2. State JSON block — delimited by ARCHON_STATE_JSON_BEGIN and ARCHON_STATE_JSON_END, each on its own line, with valid JSON between them.

Hard rules:

• Start the response with the # heading. No prose preamble. No "Looking at the data...", no <thinking>, no analysis dump, no "Now I'll synthesize...".
• Do NOT wrap the response in a JSON object. Specifically: do NOT output {"brief_markdown": "...", "next_state": {...}} — that is the OLD contract and is wrong.
• Do NOT use markdown code fences around the ARCHON_STATE_JSON_BEGIN/ARCHON_STATE_JSON_END markers — the markers must be plain lines.
• Nothing after the closing marker. The closing marker is the last line of your response.

Skeleton example (illustrative — your actual brief uses real content):

# Maintainer Standup — 2026-04-29

## Since last run
- ...

## P1 — Do today
- **PR #N** — ...

ARCHON_STATE_JSON_BEGIN
{"last_run_at":"2026-04-29T07:00:00Z","last_dev_sha":"abc123","carry_over":[],"observed_prs":[{"number":1,"title":"x"}],"observed_issues":[],"direction_questions":[]}
ARCHON_STATE_JSON_END

(In your real output the markers and JSON are NOT inside a code fence.)

---

Phase 1: LOAD INPUTS

You have three sources of upstream context, all already gathered. Each is a JSON string that you should parse.

Git status (origin/dev movement since last run)

$git-status.output