chore(memory): reclassify topical notes into subfolders

AGENTS.md

@@ -34,6 +34,7 @@ You wake up fresh each session. These files are your continuity:
 - **Daily notes:** `memory/YYYY-MM-DD.md` (create `memory/` if needed) — raw logs of what happened
 - **Long-term:** `MEMORY.md` — your curated memories, like a human's long-term memory
 - **Named notes:** reserve separate memory files for long-lived plans, references, or investigations that truly need their own home; otherwise prefer folding notes back into the daily file
+- **Top-level `memory/` rule:** keep top-level mostly for daily notes. Put topical files in subfolders like `memory/ops/`, `memory/incidents/`, `memory/plans/`, `memory/references/`, or `memory/archive/`.
 
 Capture what matters. Decisions, context, things to remember. Skip the secrets unless asked to keep them.
 

memory/2026-03-11.md

@@ -28,7 +28,13 @@
   - `2026-03-05-codex-error-type-error-error-t.md`
 - Rationale: these were mostly reset/greeting/test/heartbeat artifacts with little long-term value, but still worth retaining in case old session evidence is needed later.
 
+## Reclassification pass
+- Moved substantive non-daily topical notes out of top-level `memory/` into clearer buckets:
+  - `memory/ops/` for workflow/setup/operational notes
+  - `memory/incidents/` for debugging, outages, and issue investigation notes
+- Result: top-level `memory/` now contains mostly daily notes, which makes the default inbox much clearer.
+
 ## Follow-up intent
 - Be more disciplined about using the daily note as the default inbox and promoting only durable truths into `MEMORY.md`.
 - Avoid adding new one-off memory files unless the topic is truly long-lived.
-- Consider a later second-pass reclassification for remaining topical files (for example, move stable plans/references into clearer subfolders and fold tiny one-off notes back into day files where safe).
+- Keep top-level `memory/` mostly reserved for daily notes; use subfolders for topical material.