docs: the queues stay the global role's, by the owner's decision

Owner, 2026-10-18, asked whether a domain administrator should see their
domains' rows now that the queues are tables: "Пока только Global. Пересмотр
по необходимости." panel-redesign.md § Who sees what quotes it; roadmap.md
§ Dropped records it with the condition for return and what the work would
be.

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 — the queue is the instance's; a domain's rows for its administrator would be a decision of its own |
+| Queues, either direction | yes | no — the global role only (owner, 2026-10-18: "Пока только Global. Пересмотр по необходимости."; roadmap § Dropped) |
 | Inbound › Quarantine | all domains | assigned inbound domains |
 | Inbound › Filter lists, Server › Preflight | yes | no — the lists are instance-wide |
 | Account, Help | yes | yes |

docs/roadmap.md

@@ -138,6 +138,16 @@ without that it is not offered again.
   checks went to Server › Health (health-setup-checks, `2.11.0`) and its test
   e-mail to a form of its own (test-email, `2.12.0`). Its plan,
   `plans/preflight.md`, was removed and stays in git history.
+- **A domain administrator's rows in the queues** (decided 2026-10-18:
+  "Пока только Global. Пересмотр по необходимости."). Since `2.16.0` both
+  queues are tables split by the recipient's domain, so the rows of a
+  domain could be shown to the administrator it is assigned to, as the logs
+  are; Outbound › Queue and Inbound › Queue stay the global role's.
+  **Returns if:** the owner asks for it. The work then: the rows filtered by
+  the user's reach in the handler (outbound by the send-log row's domain or
+  the sender's, inbound by the recipient's), the menu entry and the help
+  topic shown to a `domain` user, and the per-route 404 tests turned into
+  reach tests.
 - **csrf-tokens** (decided 2026-10-13) - session-bound tokens on every form.
   Replaced by origin-strict (`2.10.4`); the conditions for building
   tokens after all are in [security.md](security.md), ADR § *CSRF via origin