chore: cancel the multi-pair archive task per the single-queue decision

1 files changed, 4 insertions, 7 deletions

diff --git a/todo.org b/todo.org
index 281aa7a..912155b 100644
--- a/todo.org
+++ b/todo.org
@@ -34,14 +34,11 @@ 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).
+** CANCELLED [#B] todo-cleanup.el per-area Open Work / Resolved pairs :feature:
+CLOSED: [2026-06-11 Thu]
+=--archive-done= assumes exactly one level-1 "Open Work" and one "Resolved" heading per todo.org. Home's consolidated file briefly carried per-area pairs and the pass skipped. Filed from home's 2026-06-11 addendum, then held the same evening when Craig flagged that he expected a single pair.
 
-HELD 2026-06-11 evening: Craig expected the consolidated todo.org to be a single Home Open Work / Home Resolved pair, not per-area pairs. Sent home that correction + reasoning (inbox reply 17:16); home is checking for complications. If single-pair wins, this task gets killed (existing tooling works unmodified). Build only if home keeps per-area sections.
+Cancelled 2026-06-11: Craig confirmed the decision — one todo queue with a single Open Work / Resolved pair. Home reshapes its consolidated file to that form, and the existing single-pair tooling works unmodified. No code change needed.
 
 ** 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).