zzstoatzz.io
+28
-17
.github/workflows/status-maintenance.yml
+28
-17
.github/workflows/status-maintenance.yml
···
80
80
81
81
IMPORTANT: the time window for this maintenance run is from the last merged status-maintenance PR until now. if the last PR was merged on Dec 2nd and today is Dec 8th, you should focus on everything from Dec 3rd onwards, NOT just "the last week".
82
82
83
-
## task 2: archive old sections (MANDATORY if over 250 lines)
83
+
## task 2: archive old month sections
84
+
85
+
**line count targets**:
86
+
- ideal: ~200 lines (concise overview)
87
+
- acceptable: 300-450 lines
88
+
- maximum: 500 lines (MUST NOT exceed)
89
+
90
+
**when to archive**: if STATUS.md > 400 lines OR contains detailed sections from previous months
91
+
92
+
**what to archive**: content from months BEFORE the current month
93
+
- if today is January 2026, move December 2025 sections to .status_history/2025-12.md
94
+
- if today is February 2026, move January 2026 sections to .status_history/2026-01.md
95
+
- current month content stays in STATUS.md
84
96
85
-
if STATUS.md > 500 lines:
97
+
**how to archive** (this means MOVING content, not summarizing):
86
98
1. create .status_history/ directory if it doesn't exist
87
-
2. identify section boundaries (look for "---" separators and "### " headers with dates)
88
-
3. move OLDEST sections to .status_history/YYYY-MM.md (grouped by month)
89
-
4. compact the meaning of the original entire STATUS.md into about 500 lines or less
90
-
5. generally preserve the document structure (keep "## recent work" header, "## immediate priorities", etc)
91
-
6. do NOT summarize archived content - move it verbatim and organize it chronologically
92
-
93
-
ARCHIVE FILE NAMING - CRITICAL:
94
-
- archive files are organized BY MONTH: .status_history/YYYY-MM.md
95
-
- if today is December 2025, archived December content goes to .status_history/2025-12.md
96
-
- if today is January 2026, archived January content goes to .status_history/2026-01.md
97
-
- check what files already exist in .status_history/ and ADD to the appropriate month file if it exists
98
-
- each month gets ONE file - append to existing month files, don't create duplicates
99
+
2. identify "### Month Year" sections from previous months in STATUS.md
100
+
3. CUT the full section content (headers, bullet points, everything)
101
+
4. PASTE/APPEND to .status_history/YYYY-MM.md
102
+
- if archive file exists: append to end of file
103
+
- if archive file doesn't exist: create with header "# plyr.fm Status History - Month Year"
104
+
5. REPLACE the moved section in STATUS.md with a brief cross-reference:
105
+
```
106
+
### December 2025
99
107
100
-
so STATUS.md is the living overview, slightly recency biased, but a good general overview of the project.
108
+
See `.status_history/2025-12.md` for detailed history.
109
+
```
110
+
6. preserve document structure (keep "## recent work", "## priorities", "## technical state" headers)
101
111
102
-
.status_history/ is the archive of temporally specific sections of STATUS.md that are worth preserving for historical context, but not significant enough to be stated literally in STATUS.md in perpetuity.
112
+
CRITICAL: "archiving" = moving actual content to archive files, NOT condensing or summarizing in place.
113
+
the detailed write-ups must be preserved in .status_history/, not deleted.
103
114
104
-
VERIFY: run `wc -l STATUS.md` after archiving. it MUST be under 500 lines.
115
+
VERIFY: run `wc -l STATUS.md` after archiving. target 300-450 lines, must be under 500.
105
116
106
117
## task 3: generate audio overview (if skip_audio is false)
107
118