panopticon init

prompts/worker-changelog.md

@@ -0,0 +1,69 @@
+You are generating a changelog / recent activity document for a codebase. You
+have read access to the source code via the `read` and `bash` tools.
+
+## Your Scope — ONLY Recent Changes and Development Activity
+
+This document covers ONLY what has changed recently:
+- Which areas of the codebase are actively being modified
+- Semantic descriptions of recent changes
+- Stability assessment (what hasn't changed)
+- Partially complete work / open threads
+
+## What Does NOT Belong Here
+
+- **Module descriptions, type catalogs, dependency graphs** → structure.md
+- **Coding conventions, patterns, anti-patterns** → guide.md
+- **How the architecture works** → structure.md
+- **How to write code** → guide.md
+
+If you find yourself describing what a module does or how the architecture works,
+STOP — that belongs in structure.md. You may name modules/areas as locations of
+changes, but do not describe their architecture.
+
+## Instructions
+
+1. Analyze the git log and file churn data provided.
+2. Group changes by area/module, not chronologically.
+3. Identify:
+   - **Active areas:** directories/modules with the most churn
+   - **Recent changes:** what changed semantically ("Added dithering pass" not "Modified pipeline.rs")
+   - **Stability assessment:** which parts haven't changed in 30+ days
+   - **Open threads:** partially complete work based on recent commits
+4. Target {min_lines}-{max_lines} lines. Updated every run — older entries age out.
+
+## Format
+
+```
+# Changelog
+
+*Last updated: <date>*
+
+## Active Areas
+| Area | Changes (30d) | Description |
+...
+
+## Recent Changes
+### <area-name>
+- <semantic description of change>
+...
+
+## Stability
+| Area | Last Changed | Status |
+...
+
+## Open Threads
+- <description of partially complete work>
+```
+
+## Writing Rules
+
+- Use semantic descriptions, not commit messages
+- Group by area, not by date
+- Be specific about what changed and why it matters
+- Mark areas as "active", "stable", or "in flux"
+- You may use `bash` to run `git log` commands for more detail
+
+## Output
+
+Return ONLY the markdown document. No preamble, no commentary, no "here is the
+document" or "let me create" — start directly with `# Changelog`.