Merge branch 'feat/discord-channel-memory'

Author: joshp123

.github/workflows/image-build.yml

@@ -29,6 +29,8 @@ jobs:
           primary-key: nix-${{ runner.os }}-${{ hashFiles('**/flake.lock') }}
           restore-prefixes-first-match: |
             nix-${{ runner.os }}-
+          paths-linux: |
+            /nix/store
 
       - name: Free disk space
         run: |

clawdinator/workspace/HEARTBEAT.md

@@ -3,28 +3,8 @@
 Hourly SITREP checklist:
 
 1. Read AGENTS.md comms rules (terse chat, details to files)
-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`
-   - 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
+2. Read `/memory/sitrep-latest.md` for previous context
+3. Run lurk skill (`skills/lurk/SKILL.md`) — read Discord channels, persist to `/memory/discord/YYYY-MM-DD.md`
+4. Run triage skill (`skills/triage/SKILL.md`) — analyze GitHub + Discord, write SITREP
+5. Post summary to chat (5-10 lines)
+6. If nothing needs attention, reply HEARTBEAT_OK

clawdinator/workspace/skills/lurk/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: lurk
+description: Monitor Discord channel activity and persist notable items to memory. Run from main session during heartbeat.
+---
+
+# Lurk Skill
+
+Monitor Discord lurk channels and persist notable activity to shared memory.
+
+## When to Use
+
+- Hourly heartbeat (step 3)
+- Manual trigger to capture current channel state
+
+## How to Run
+
+Use `discord.readMessages` to read recent messages from the **LURK channels** listed in `AGENTS.md`.
+
+- Do not read or write to any channel that is not explicitly listed there.
+- These channels are read-only (sendPolicy denies replies).
+
+## What to Capture
+
+**Persist these:**
+- Support issues / bug reports
+- Questions that indicate user confusion
+- Feature requests with discussion
+- Anything referencing GitHub issues/PRs
+- Repeated topics (multiple users, same issue)
+- Announcements or important updates
+
+**Skip these:**
+- Casual chat / banter
+- Single-word reactions
+- Bot spam
+- Already-resolved questions
+
+## Output
+
+Append to `/memory/discord/YYYY-MM-DD.md` using `memory-edit` (exclusive lock).
+
+```markdown
+## HH:MM #channel-name
+- [brief summary of notable item]
+- Links to #NNN if references GitHub issue
+- @username if relevant
+
+## HH:MM #channel-name
+- [another item]
+```
+
+## Constraints
+
+- Be selective. Only notable items.
+- Include timestamp and channel name.
+- Keep each entry to 1-2 lines.
+- Cross-reference GitHub issues when mentioned.
+- Never write to `/memory` using raw redirects (`>`, `>>`); always use `memory-edit`.
+- If nothing notable: don't write anything, reply `NO_NOTABLE_ACTIVITY`.

clawdinator/workspace/skills/triage/SKILL.md

@@ -29,9 +29,11 @@ Read these files to understand current state:
    - `/memory/project.md` — project goals and priorities
    - `/memory/architecture.md` — architecture decisions
 
-4. **Discord signals**:
-   - Recent messages in conversation context from lurk channels
+4. **Discord signals** (persisted by lurk skill):
+   - `/memory/discord/YYYY-MM-DD.md` — today's channel activity
+   - `/memory/discord/<yesterday>.md` — yesterday's (for context; use the previous date)
    - Cross-reference with GitHub issues where relevant
+   - Multiple Discord reports of same issue = elevated priority
 
 ## Your Task
 
@@ -51,7 +53,7 @@ Read these files to understand current state:
 
 ## Output Format (SITREP)
 
-Write to `/memory/sitrep-latest.md`:
+Write to `/memory/sitrep-latest.md` using `memory-write` (exclusive lock):
 
 ```markdown
 # SITREP YYYY-MM-DDTHH:MMZ
@@ -96,4 +98,5 @@ If nothing needs attention: `HEARTBEAT_OK`
 - No markdown tables (use bullet lists).
 - If data is stale (>1hr old sync), note it.
 - If something is unclear, say so — don't guess.
+- Use `memory-read` for all reads from `/memory`.
 - Advisory only: don't take actions, just recommend.

scripts/init-memory.sh

@@ -5,7 +5,7 @@ root="${1:-/memory}"
 owner="${2:-clawdinator}"
 group="${3:-clawdinator}"
 
-mkdir -p "$root/daily"
+mkdir -p "$root/daily" "$root/discord"
 
 index="$root/index.md"
 if [ ! -f "$index" ]; then
@@ -14,9 +14,10 @@ if [ ! -f "$index" ]; then
 
 - Daily notes live in /memory/daily/YYYY-MM-DD.md
 - Durable facts belong in /memory/project.md and /memory/architecture.md
+- Discord lurk snapshots live in /memory/discord/YYYY-MM-DD.md
 EOM
 fi
 
 # Ensure shared memory is writable by the service user across instances.
-chown "$owner:$group" "$root" "$root/daily"
-chmod 2770 "$root" "$root/daily"
+chown "$owner:$group" "$root" "$root/daily" "$root/discord"
+chmod 2770 "$root" "$root/daily" "$root/discord"