feat(heartbeat): add SITREP structure with delta tracking

- HEARTBEAT.md: detailed checklist with sitrep-latest.md workflow
- Triage skill: updated output format with fires/now/dashboard/changes
- Chat output: 3-5 lines with link to full sitrep
- Tracks changes since last sitrep (new/closed/updated)

Author: CLAWDINATOR

clawdinator/workspace/HEARTBEAT.md

@@ -3,11 +3,28 @@
 Hourly SITREP checklist:
 
 1. Read AGENTS.md comms rules (terse chat, details to files)
-2. Read `/memory/index.md` and today's daily file for context
-3. Persist any relevant channel updates to daily memory file
+2. Read `/memory/index.md` and `/memory/sitrep-latest.md` for context
+3. Persist any relevant channel updates to today's daily memory file
 4. Run triage skill (`skills/triage/SKILL.md`):
    - Read `/memory/github/prs.md` and `/memory/github/issues.md`
-   - Identify Now/Next/Later priorities
-5. Write detailed sitrep to today's daily memory file
-6. Post terse summary to chat (1-3 lines max, no tables)
-7. If nothing needs attention, reply HEARTBEAT_OK
+   - Compare against previous sitrep for changes
+5. Write SITREP to `/memory/sitrep-latest.md` (overwrite):
+   ```markdown
+   # SITREP YYYY-MM-DDTHH:MMZ
+
+   ## 🔥 Fires
+   - Active issues needing immediate attention
+
+   ## ⚡ NOW
+   - Single most important action to take
+
+   ## 📊 Dashboard
+   - PRs: X open (Y approved waiting)
+   - Issues: X open (Y bugs, Z features)
+
+   ## 🔄 Changes since last SITREP
+   - NEW/CLOSED/UPDATED items
+   ```
+6. Append summary to today's daily file (`/memory/daily/YYYY-MM-DD.md`)
+7. Post terse summary to chat (3-5 lines, link to sitrep-latest.md)
+8. If nothing needs attention, reply HEARTBEAT_OK

clawdinator/workspace/skills/triage/SKILL.md

@@ -12,7 +12,7 @@ You are a maintainer triage agent for the clawdbot org. Your job is to read the
 Trigger on:
 - "triage", "priorities", "what's hot", "what needs attention"
 - "status", "what's happening", "project health"
-- "what should I work on", "where do I start"
+- Hourly heartbeat SITREP
 
 ## Context Sources
 
@@ -22,20 +22,24 @@ Read these files to understand current state:
    - `/memory/github/prs.md` — all open PRs across clawdbot org
    - `/memory/github/issues.md` — all open issues across clawdbot org
 
-2. **Project context**:
+2. **Previous SITREP** (for delta):
+   - `/memory/sitrep-latest.md` — last hourly sitrep
+
+3. **Project context**:
    - `/memory/project.md` — project goals and priorities
    - `/memory/architecture.md` — architecture decisions
 
-3. **Discord signals**:
-   - Recent messages are already in your conversation context from lurk channels
+4. **Discord signals**:
+   - Recent messages in conversation context from lurk channels
    - Cross-reference with GitHub issues where relevant
 
 ## Your Task
 
-1. **Read AGENTS.md communication rules first** — they govern how you deliver output
+1. **Read AGENTS.md communication rules first** — they govern output delivery
 2. Read the raw data from memory files
-3. Reason about what's urgent, ready, blocked, or stale
-4. Produce a prioritized summary with clear recommendations
+3. Compare against previous sitrep for changes (new/closed/updated)
+4. Reason about what's urgent, ready, blocked, or stale
+5. Produce SITREP in the format below
 
 ## Priority Guidance
 
@@ -45,34 +49,51 @@ Read these files to understand current state:
 - PRs with approvals waiting to merge = quick wins
 - Issues with no activity = potential neglect
 
-## Output Format
+## Output Format (SITREP)
+
+Write to `/memory/sitrep-latest.md`:
+
+```markdown
+# SITREP YYYY-MM-DDTHH:MMZ
+
+## 🔥 Fires
+- [#NNN](<url>) brief description (age, comment count)
+
+## ⚡ NOW
+Single most important action: [describe with link]
 
-Produce a concise Now/Next/Later summary:
+## 📊 Dashboard
+- PRs: X open (Y approved waiting, Z draft)
+- Issues: X open (Y bugs, Z features)
+- Sync: [timestamp from prs.md]
 
-### NOW (needs attention today)
-- What: [item with link]
-- Why: [reason it's urgent]
-- Action: [recommended next step]
+## 🔄 Changes since last SITREP
+- NEW: #NNN description
+- CLOSED: #NNN description
+- UPDATED: #NNN significant update
 
-### NEXT (this week)
-- What: [item with link]
-- Why: [reason it's important]
-- Action: [recommended next step]
+## 📋 Queue
+- **NOW:** [#NNN](<url>) — action needed
+- **NEXT:** [#NNN](<url>) — description
+- **LATER:** [#NNN](<url>) — description
+```
 
-### LATER (backlog)
-- What: [item]
-- Notes: [any context]
+## Chat Output
 
-### Quick Wins
-- [Approved PRs ready to merge, easy fixes, etc.]
+After writing sitrep-latest.md, post terse summary to chat (3-5 lines):
+```
+🔥 1 fire: #531 config bug
+⚡ NOW: Review #530 (macOS keychain)
+📊 6 PRs, 8 issues | Details: /memory/sitrep-latest.md
+```
 
-### Signals
-- [Notable Discord mentions, patterns, community concerns]
+If nothing needs attention: `HEARTBEAT_OK`
 
 ## Constraints
 
 - Be concise. Maintainers are busy.
-- Always include links to issues/PRs.
+- Always use masked links: `[#NNN](<url>)`
+- No markdown tables (use bullet lists).
 - If data is stale (>1hr old sync), note it.
 - If something is unclear, say so — don't guess.
 - Advisory only: don't take actions, just recommend.