chore: process home consolidation handoffs and file follow-ups

1 files changed, 10 insertions, 0 deletions

diff --git a/todo.org b/todo.org
index 85e676e..03fd971 100644
--- a/todo.org
+++ b/todo.org
@@ -34,6 +34,16 @@ Tags are assigned and refreshed by =task-audit=; =task-review= keeps them honest
 
 * Rulesets Open Work
 
+** TODO [#B] todo-cleanup.el per-area Open Work / Resolved pairs :feature:
+:PROPERTIES:
+:CREATED: [2026-06-11 Thu]
+:LAST_REVIEWED: 2026-06-11
+:END:
+=--archive-done= assumes exactly one level-1 "Open Work" and one "Resolved" heading per todo.org. Home's consolidated file now carries per-area pairs (Home Open Work / Home Resolved, Clipper Open Work / Clipper Resolved, more arriving per fold) and the pass skips with "more than one level-1 heading contains Open Work". Suggested fix from home's 2026-06-11 addendum handoff: match each =* <Area> Open Work= with its =* <Area> Resolved= sibling and archive within the pair, falling back to current single-pair behavior. Home archives manually at wrap-up until this lands, so every fold widens the manual gap. ERT tests first (multi-pair, single-pair regression, unpaired-area error).
+
+** VERIFY Should new personal projects start as areas inside home rather than standalone ~/projects entries?
+Home's consolidation (2026-06-11) leaves ~/projects with home and work only. The open template question: when Craig starts a new personal project, does =first-session.org= / =install-ai.sh= guidance now say "create an area in home" by default, with standalone reserved for code projects in ~/code? Affects first-session.org, install-ai.sh docs, and the triggers.md "Launch project X" resolution (folded names like "finances" no longer resolve as projects; an area-aware launch could map them to home).
+
 ** DOING [#C] Check that memories are sync'd across machines via git :spec:
 :PROPERTIES:
 :LAST_REVIEWED: 2026-06-10