docs(todo): close test harness; file Phase A inbox-scan bug

Flipped the test harness task at line 1766 to DONE (work landed in 7ef200a). Filed a new [#B] for a fold side-effect surfaced during the publish flow: Phase A's inbox check at startup.org:107 only looks at the project root, so it never scans claude-templates/inbox/ (the canonical's inbox, now in-repo after the subtree merge). This session received a cross-project handoff there at startup and missed it entirely; the drift surfaced only during commit staging.

1 files changed, 12 insertions, 1 deletions

diff --git a/todo.org b/todo.org
index aea4ab1..98d1723 100644
--- a/todo.org
+++ b/todo.org
@@ -1763,7 +1763,8 @@ The four canonical rules (=commits=, =testing=, =verification=, =subagents=) are
 
 The Elisp pair is the most suspicious — three repos using essentially the same rules. Audit: diff these across the projects, check for drift, then decide whether to canonicalize them under =~/code/rulesets/claude-rules/languages/<lang>/= and symlink, or leave them as project-local.
 
-** TODO [#C] Test harness for =make audit= + =make install-ai= edge cases :test:
+** DONE [#C] Test harness for =make audit= + =make install-ai= edge cases :test:
+CLOSED: [2026-05-15 Fri]
 
 Three edge cases from the fold-epic test plan were not exercised because they're destructive on real projects:
 
@@ -1788,6 +1789,16 @@ Options:
 
 Triggered by: 2026-05-15 fold session's refactor audit (commit =2d645fc=).
 
+** TODO [#B] Phase A startup blind to =claude-templates/inbox/= post-fold :bug:fold:
+
+Phase A's inbox check at =startup.org:107= runs =\ls -la inbox/= against the project root. Post-fold, the canonical's inbox sits inside the subtree at =claude-templates/inbox/= and never gets scanned. A 2026-05-15 cross-project handoff from a dotemacs session dropped a record there; the next rulesets session (this one) missed it at startup entirely. Picked up only when the working-tree drift surfaced during the publish flow.
+
+Fix: extend Phase A's discovery to also scan =claude-templates/inbox/= when the canonical lives in-repo (i.e., when =claude-templates/.ai/= exists alongside =./.ai/=). The Phase B/C inbox-processing flow already handles per-file routing once a file is surfaced; the gap is only in discovery.
+
+Adjacent question worth answering at the same time: should cross-project handoffs file into =./inbox/= at the project root (matching what Phase A already scans), or stay in =claude-templates/inbox/= and rely on the discovery fix? The =inbox-send= script's target-project logic is the place to settle that.
+
+Triggered by: 2026-05-15 evening session, surfaced when committing the test-harness work.
+
 ** TODO [#C] Refactor =daily-prep.org= to delegate to =triage-intake.org= for the triage section
 
 =daily-prep.org= still does its own inline triage (Gmail × 3 accounts, Slack, Linear, GHE PRs, calendars) as part of the full prep flow. Now that =triage-intake.org= exists as a standalone scan over the same source set, daily-prep could call it and consume its synthesis instead of duplicating the source-scan logic — DRYs up a 57k-line workflow and keeps both flows in sync when sources change.