chore(todo): file the pre-vacation morning-review list

I swept every open task against the 2026-08-15 departure and filed the ranked list as a scheduled VERIFY for the morning. The net-scenarios timeout flake also got a dated recurrence note: it fired again under concurrent suite load and cleared standalone.

1 files changed, 44 insertions, 0 deletions

diff --git a/todo.org b/todo.org
index 67e4f6f..5daacf2 100644
--- a/todo.org
+++ b/todo.org
@@ -45,6 +45,43 @@ below):
   input-side-spec.org (DRAFT, four decisions open).
 
 * Archsetup Open Work
+** VERIFY [#A] Pre-vacation fix list — morning review
+SCHEDULED: <2026-08-08 Sat>
+:PROPERTIES:
+:LAST_REVIEWED: 2026-08-08
+:END:
+The full todo.org sweep you asked for before sleeping, ranked by what I'd fix
+before departure (~2026-08-15, velox travels). Approve, reorder, or strike;
+items needing your call say so.
+
+1. Velox reliability (the anchor — [#A] sleep/suspend, scheduled Monday).
+   Prerequisite: velox powered on and on the tailnet; it's been offline since
+   ~2026-08-05. Riders already folded in: the tlp.d radio-enable line, a
+   dotfiles pull, the touchpad-detection spot-check.
+2. Velox machine health for travel (NEW — filed nowhere else): resolve the
+   ~/code/auto-dim-other-buffers.el merge conflict (literal conflict markers
+   in a loaded .el; its emacs suite has been red since 2026-08-01), clear the
+   stale password prompt sitting on its screen since 2026-07-31, and run a
+   maint doctor pass.
+3. Remote access verified from OUTSIDE the LAN while you're still home:
+   tailscale to ratio, truenas, and truenas-kvm from a phone hotspot. Decide
+   whether the wolf WireGuard profile should also work from velox on the road
+   (it exists on ratio only, inactive). Cheap now, expensive to debug from a
+   hotel.
+4. The cgit secrets/privacy audit ([#B] below): a world-readable secret
+   standing while you're away is the worst timing. The repo-by-repo scan is
+   mine to run; the public-vs-private call per repo is yours. The archsetup
+   cgit move can wait unless the audit finds something.
+5. Already scheduled today: osbot camera (needs the camera plugged in).
+   Buildable any time: the podman socket + camera udev task (:solo:).
+6. Optional travel niceties blocked on upfront-answerable design calls in
+   their bodies (two for hotspot/metered WiFi in amber, one for network-panel
+   ordering by availability). Answer the calls and I can build both.
+7. Deliberately left off: offline LLM (you declined the vacation track),
+   night-watch/lock-watchdog (ratio stays home with no user to relock; say so
+   if you disagree). Found tonight, low priority: the orchestrator sequence
+   pin can't see an added-but-unstubbed call (it caught drops only) — worth a
+   harness hardening pass someday.
 ** TODO [#B] Podman API socket and camera-passthrough udev rule :feature:solo:
 :PROPERTIES:
 :CREATED: [2026-08-07 Fri]
@@ -277,6 +314,13 @@ The harness stubs =ssh=, =rsync= and =jq= onto =PATH=, so nothing should touch t
 
 Not graded on the bug matrix: it is test infrastructure, not the shipped codebase.
 
+*** 2026-08-08 Sat @ 05:05:00 -0500 Recurred under concurrent load, same signature
+All 5 tests hit the 20s TimeoutExpired again during a =make test-unit= run
+that overlapped two review subagents running their own suites on the box.
+Standalone immediately after: 0.095s, all pass; the following quiet-machine
+full run was clean. Confirms the load-sensitivity read — reproduce under
+deliberate load before choosing between a bigger budget and a real hang.
+
 ** VERIFY Should coredump entries group as one journal-digest row per binary? :maint:
 :PROPERTIES:
 :LAST_REVIEWED: 2026-07-24