chore: triage inbox (park Phase E proposal, file KB-encouragement task)

I processed two .emacs.d handoffs and one roam item. The inbox-zero Phase E proposal (autonomous task execution in a synced template) arrived in a no-approvals session, so it parks as a [#B] VERIFY with the prepared diff under working/, not self-applied. The roam item to wire KB-contribution encouragement into four workflows is filed as a [#C] design task. I dropped its :next: tag because curating the best-practices content needs a decision, not a loop auto-implement.

1 files changed, 65 insertions, 0 deletions

diff --git a/working/inbox-zero-phase-e/proposed.diff b/working/inbox-zero-phase-e/proposed.diff
new file mode 100644
index 0000000..e3d8ee8
--- /dev/null
+++ b/working/inbox-zero-phase-e/proposed.diff
@@ -0,0 +1,65 @@
+--- claude-templates/.ai/workflows/inbox-zero.org	2026-06-13 13:18:35.988799778 -0500
++++ /proc/self/fd/12	2026-06-16 00:18:07.592944696 -0500
+@@ -1,6 +1,3 @@
+-#+TITLE: Inbox Zero Workflow
+-#+AUTHOR: Craig Jennings & Claude
+-#+DATE: 2026-06-13
+ 
+ * Overview
+ 
+@@ -19,7 +16,7 @@
+ Reused from three callers so the steps live in one place:
+ - *Startup* (read-only nudge) — count the items, identify which appear related to this project, surface both numbers, offer processing as one of the startup options. Never auto-files.
+ - *Wrap-up* (Step 3 sub-step) — sweep items that belong here before the cleanup scripts, so imported tasks lint and ride the wrap commit.
+-- *On demand* — "inbox zero", "empty the inbox", "process the roam inbox", "triage my roam inbox".
++- *On demand* — "inbox zero", "empty the inbox", "process the roam inbox", "triage my roam inbox". The on-demand caller (and the recurring loop that invokes it) also runs *Phase E* below: after routing the inbox, it works the project's actionable backlog, implementing eligible =:next:= / =:quick:+:solo:= tasks. Startup and wrap-up skip Phase E.
+ 
+ Each project touches the roam inbox at least twice a session this way: once at startup, once at wrap-up.
+ 
+@@ -69,6 +66,46 @@
+ 
+ Report: moved (with their new priorities and tags), folded, dropped-as-done. Then the residue: foreign items (left for their owners, count only) and unowned items (count plus the headings that appear related to this project, for manual claim or prefix). Same "summarize what we kept" shape.
+ 
++* Phase E — Execute actionable tagged tasks (autonomous; on-demand / loop caller only)
++
++After routing the inbox, the on-demand and loop callers work the project's actionable backlog. *Startup (read-only) and wrap-up (winding down) skip this phase entirely* — it runs only when a human or the recurring loop invokes the workflow to make progress, never as a side effect of session bookkeeping.
++
++** Eligibility gate
++
++Scan =todo.org= (both items freshly filed in Phase B and the existing backlog). A task is a candidate when ALL hold:
++
++1. Status is =TODO= — not =VERIFY=, =DOING=, =DONE=, or =CANCELLED=. =VERIFY= means "awaiting Craig's manual confirmation"; never auto-implement a VERIFY. Those are the manual-testing verifications this phase deliberately leaves alone.
++2. Tagged =:next:=, OR tagged BOTH =:quick:= AND =:solo:=.
++3. Implementable solo — no input or undecided judgment call from Craig.
++4. Estimated at roughly 30 minutes or less of focused work.
++
++** Act-vs-file decision
++
++For each candidate, after a quick scope read of the relevant code:
++
++- *Clear, bounded, solo, ≤ ~30 min* → implement it now (below).
++- *Needs Craig's input, a decision, or design discussion* → do NOT implement. Leave it filed, add a one-line note on the task naming the input it needs, and surface it.
++- *An hour or more* → do NOT implement. Leave it filed and surface it as a larger task for a dedicated =/start-work= session.
++
++When unsure which side a task falls on, file rather than implement. A wrong auto-implement costs more than a deferred task.
++
++** Implementing a candidate
++
++Per task, follow the project's commit discipline — the per-project waiver: no approval gate, but TDD + =/review-code= + =/voice personal= on every commit, no AI attribution:
++
++1. Trace to root cause; write the failing test first (Red → Green → Refactor).
++2. Live-reload into the running daemon and verify per the emacs reload-and-verify loop.
++3. Close the task per =todo-format.md= (top-level → =DONE= + =CLOSED:=; sub-task → dated log rewrite). When the only residue is Craig's manual check, file a =VERIFY= child under "Manual testing and validation" and close the originating task (the codified manual-verification-handoff pattern).
++4. =/review-code --staged= → fix all Critical/Important → =/voice personal= on the message → commit individually. Push per the project's flow.
++
++** Bounding the run
++
++Default to one task per run: implement the highest-priority eligible candidate (=[#A]= before =[#B]= before =[#C]=), commit, then stop and let the next tick or the next on-demand invocation continue. A caller may work more than one in a run when the eligible tasks are small and clearly independent — but each gets its own test and its own commit, and the run stays reviewable. Never batch unrelated changes into one commit.
++
++** Surface
++
++Report what was implemented (task + commit), what was deferred and why (needs-input / too-large), and what stays filed.
++
+ * Skip conditions
+ 
+ - No =~/org/roam/inbox.org= → silent no-op.