queue-table: Outbound › Queue as the drawn table, Inbound › Queue built

Owner, 2026-10-18: "Фиаско, что очередь не была сделана. Как мы это
допустили? Исправляем!" The mockups out-queue and in-queue (design 629de5e,
guards 8525e8e).

- postfix: postqueue -j gives each message's size and each recipient's
  delay_reason (src/postqueue/showq_json.c, format_json(): "delay_reason"
  only when LEN(why) > 0); QueueListing reads it with the page's 5 s,
  QueueMessages keeps the notifier's 30 s.
- view: one Queue page type for both directions (queue.go), one polled box
  (queue_body.html): a row per recipient, oldest first, cut at 200 with a
  foot; the head "N messages · size", "Refreshes on its own" while empty;
  Last reply is the delay reason, or where the message is (active, hold,
  incoming) before there was one. Inbound has no Details: an inbound
  message has no page of its own.
- handlers: one read of the queue, split by the recipient's domain against
  the inbound domains; an outbound recipient is linked to its send-log row
  (store.SendLogRefsByQueueID, through idx_send_log_queue_id, plan pinned in
  TestSendLogQueriesUseTheirIndexes), matched without regard to case, else
  the message's first row. Both pages are the global role's; the inbound
  one 404s with the relay off. Routes /inbound/queue (+ /fragment), menu,
  touch menu and sibling strip.
- Overview: Queues · Both empty · outbound and inbound with the relay on.
- Help: the queue topic rewritten, an Inbound queue topic (word for word with
  the mockup; domain administrators do not see it, as with the lists).
- TestUnbuiltScreensAreOnTheRoadmap and its rule in development.md: an
  exempted screen must be named in roadmap.md; queue-table leaves the
  roadmap; guide, architecture, panel-redesign.md updated.

Tests: go vet; go test ./internal/web/... ./internal/store ./internal/postfix
./internal/notify pass.

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

docs/plans/panel-redesign.md

@@ -95,7 +95,7 @@ only.
 | Outbound: domain, applications, settings, log, DMARC | all domains | assigned outbound domains |
 | Inbound: domain (upstream, recipients), log | all domains | assigned inbound domains |
 | Add / delete a domain, either direction | yes | no |
-| Queues, either direction | yes | no, until the queue is a filterable table |
+| Queues, either direction | yes | no — the queue is the instance's; a domain's rows for its administrator would be a decision of its own |
 | Inbound › Quarantine | all domains | assigned inbound domains |
 | Inbound › Filter lists, Server › Preflight | yes | no — the lists are instance-wide |
 | Account, Help | yes | yes |
@@ -215,8 +215,10 @@ Rules that come with the rename:
 **Needs its own roadmap decision before it is built** (the mockups show the
 target; none of this is smuggled in with the restyle):
 
-- Queue as a table — parse `postqueue -j` instead of printing `postqueue -p`.
-- Inbound queue — the same queue filtered by recipient domain.
+- Queue as a table — parse `postqueue -j` instead of printing `postqueue -p`
+  (built in `2.16.0`).
+- Inbound queue — the same queue filtered by recipient domain (built in
+  `2.16.0`).
 - Inbound log — rides on `inbound-antispam-panel` (`2.1.0`).
 - Server › Health — a route for the tables removed from Overview, and the
   home of *Reload configuration* (today a card on `/status`).
@@ -236,7 +238,6 @@ Drawn and not built (`deferredScreens` in the guard tests):
 
 | Screen | Item | State |
 |---|---|---|
-| `in-queue` | [queue-table](../roadmap.md#queue-table): the queue as a table from `postqueue -j`, and an Inbound › Queue | undecided; Outbound › Queue shows postqueue's listing in a log pane (`outlineExempt`) |
 | `in-quarantine`, `in-quarantine-message` | inbound-quarantine, an idea off the roadmap ([its notes](inbound-quarantine.md)) | its open questions stay open; the mockup assumes SelfPost-held mail, release to upstream, 14 days, delegated like the rest of Inbound |
 
 The sibling strip under the navbar holds five or six entries per group without