design: the queues as tables - help for both, a help link on Inbound › Queue

Owner, 2026-10-18: "Фиаско, что очередь не была сделана. ... Исправляем!" -
the queue-table row is taken into work: Outbound › Queue becomes the table
out-queue draws, and Inbound › Queue (in-queue) is built.

The two screens are drawn already; what they did not draw, drawn here first:
- Help › Queue and retries: the table, one row per recipient, with the last
  reply; mail for an inbound domain under Inbound › Queue; Details opens the
  message in the Outbound log. postqueue -p is no longer named.
- Help › Inbound queue, a topic and a menu entry of its own, and the help
  link in in-queue's Waiting head that points at it, as out-queue has.
Rebuilt; check.py --write: 31 screens, 0 violations.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/assets/panel-redesign/panel/in-queue.html

@@ -73,7 +73,7 @@
     </div>
 
     <div class="box">
-      <div class="sp-box-head"><span class="sp-no">01</span><h2>Waiting</h2><div class="sp-end">Refreshes on its own</div></div>
+      <div class="sp-box-head"><span class="sp-no">01</span><h2>Waiting</h2><div class="sp-end">Refreshes on its own</div><a class="sp-help" href="help.html#inbound-queue" title="What waits here and why"><i class="ti ti-help-circle"></i></a></div>
       <div class="sp-empty"><i class="ti ti-stack-2"></i>Nothing is waiting. Every accepted message has reached its upstream.</div>
     </div>