chore: process inbox (file fix-speedrun task, clear pearl acks)

I filed the .emacs.d "fix speedrun" proposal as a [#C] spec task, with its content preserved in docs/design for spec-create later. The two pearl acks confirmed handoffs I'd already sent, so they needed nothing back.

1 files changed, 21 insertions, 0 deletions

diff --git a/docs/design/2026-06-15-fix-speedrun-workflow-proposal.org b/docs/design/2026-06-15-fix-speedrun-workflow-proposal.org
new file mode 100644
index 0000000..c1c7077
--- /dev/null
+++ b/docs/design/2026-06-15-fix-speedrun-workflow-proposal.org
@@ -0,0 +1,21 @@
+#+TITLE: Proposed reusable workflow: "fix speedrun" mode, available t
+#+SOURCE: from .emacs.d
+#+DATE: 2026-06-15 19:22:56 -0500
+
+Proposed reusable workflow: "fix speedrun" mode, available to all coding projects.
+
+Origin: a 2026-06-15 .emacs.d theme-studio session. Craig batched a list of quick wins / small fixes and asked me to run them autonomously.
+
+The shape that worked:
+- Entry: Craig names an ordered set of tasks (or points at a tagged subset) and says "fix speedrun" / "no approvals until done".
+- Execution: work the set in order, no per-step approval gates. Each task still runs the full quality bar (TDD red->green, /review-code, /voice on the commit), and each is committed + pushed as its own logical commit when green ("always push this session" pairs naturally).
+- Ambiguity handling: if a task turns out underspecified or already-satisfied, do not guess-implement — file a VERIFY noting why and move on. (This session: "raise max spans to 5" — every cap was already 8.)
+- Exit / handoff: when the set is done, PAGE the user (proactive push notification) with the project name, the completed task(s), and a numbered list of remaining tasks. The user confirms ready + names the next project in one reply.
+
+Open questions for the canonical:
+- Where the page fires (every task vs end-of-set) and via what (push notification).
+- How it composes with the existing no-approvals + always-push session modes (is "fix speedrun" just a named preset of those plus the end page?).
+- Whether it should auto-pull the task set from a tag/priority query rather than an explicit list.
+- Guardrails: it should refuse to speedrun tasks that need design decisions or carry data-loss risk without a checkpoint (e.g. the unused-tile flag here was biased-safe deliberately).
+
+This is a rulesets-owned concept (cross-project), so sending it here rather than building it locally. No local stopgap made.