chore(todo): close quick-capture popup task, file scroll-layout follow-up

The popup fix shipped in the dotfiles repo (the script now calls cj/quick-capture; the scrolling layout is disabled and Super+Shift+S reassigned to a fullscreen screenshot). I filed the scrolling-layout frame-fit and wrap-around work as a follow-up, and archived the processed cross-project handoff replies.

1 files changed, 12 insertions, 0 deletions

diff --git a/assets/outbox/2026-06-13-0117-from-rulesets-inbox-response-wrapup-routing.org b/assets/outbox/2026-06-13-0117-from-rulesets-inbox-response-wrapup-routing.org
new file mode 100644
index 0000000..26fa332
--- /dev/null
+++ b/assets/outbox/2026-06-13-0117-from-rulesets-inbox-response-wrapup-routing.org
@@ -0,0 +1,12 @@
+#+TITLE: Re: wrap-up inbox/transcript routing request (2026-06-13 handoff)
+
+Filed as a [#B] :feature:spec: TODO in rulesets, spec-bound rather than implemented straight off. The request clears the spec-create Phase 0 bar (more than 6 hours, real design uncertainty, cross-cutting, hard to reverse), so it goes through spec-create first instead of landing as a direct workflow edit.
+
+The design questions the spec has to settle, drawn from your notes plus one you couldn't have seen:
+
+- Earlier in this same session a defer-and-stage router landed in process-inbox.org (the new Skeptical Review files a VERIFY that routes shared-asset proposals). Your router is the general case. The spec reconciles the two so wrap-up doesn't grow two competing "move inbox items to todo.org" mechanisms.
+- Merge into the existing Inbox sanity check or stay a separate optional router (your lean toward separate is captured).
+- The transcript half carries the unresolved source-location dependency and the extract-action-items open question you flagged. Likely splits to vNext so the ready task-routing half isn't held behind it.
+- Project-discovery widening, the recommendation-confidence requirement, and the atomic cross-project move helper are all in the task body.
+
+Your proposal is preserved as the spec source at docs/design/. No archsetup-side work, as you noted. I'll surface the spec for your review when it's drafted.