From 283ce6ad5e4318d7aeb3182db44986ffd1761194 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Tue, 19 May 2026 02:02:20 -0500 Subject: chore(todo): close Phase A inbox-blind-spot task as moot The bug was real on 2026-05-15 but is moot in current state. inbox-send.py's discovery scans ~/code/* and ~/projects/* single-level, so claude-templates/ (two levels under ~/code/) is never routable as a target. The 2026-05-15 incident was a one-time manual workaround because rulesets/inbox/ didn't exist yet; 470085f added that root inbox and the same session removed claude-templates/inbox/. Nothing routes to the subtree inbox now, and the subtree inbox doesn't exist. Phase A scanning only ./inbox/ is correct given current state. No code change needed; this is just a depth-based completion flip per the todo-format convention. --- todo.org | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/todo.org b/todo.org index 6c1541b..2a0d6c3 100644 --- a/todo.org +++ b/todo.org @@ -1770,7 +1770,10 @@ 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: +** DONE [#B] Phase A startup blind to =claude-templates/inbox/= post-fold :bug:fold: +CLOSED: [2026-05-19 Tue] + +Resolved on inspection: the bug is moot in current state. =inbox-send.py='s discovery scans =~/code/*= and =~/projects/*= single-level only, so =claude-templates/= (two levels under =~/code/=) is never a routable target; the 2026-05-15 incident was a one-time manual workaround because =rulesets/inbox/= didn't exist yet, and that root inbox was added in =470085f=. =claude-templates/inbox/= was removed 2026-05-15 and is no longer on disk. 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. -- cgit v1.2.3