docs: draw the roadmap's screens in the panel design

Four screens for open roadmap items, all built from existing components:
Inbound > Filter lists (allow / deny, where the maps go) and an adjusted
Inbound > Log (client, decision, engine and reason, Allow / Deny sender)
for inbound-antispam-panel; Inbound > Quarantine, list and held message
with Release beside a danger-zone Discard, for inbound-quarantine; and
Server > Preflight, a verdict postmark over a table of checks with a
"what to do" column and a test e-mail form, for preflight.

A mockup is the target look, not a decision to build: each item keeps
its status, and quarantine's open questions stay open - the mockup only
assumes answers to them. The paths join the plan's Routes table, the
quarantine and preflight plans link their mockups, and the components
page maps the quarantine decision to a tag. 33 screens; lint clean.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

docs/plans/inbound-quarantine.md

@@ -22,6 +22,15 @@ so we can compare approaches before committing.
 reference to them) under `/data`, retention, release workflow, and a wider
 attack/backup surface — closer to "mini-mailbox" than pure relay.
 
+## Mockup
+
+A target look is drawn — list and detail —
+[in-quarantine](../assets/panel-redesign/panel/in-quarantine.html),
+[in-quarantine-message](../assets/panel-redesign/panel/in-quarantine-message.html)
+— under the design contract of [panel-redesign.md](panel-redesign.md). It
+assumes answers to the questions below (SelfPost holds the mail, release goes
+to the upstream, 14 days, headers only in the panel); it does not settle them.
+
 ## Open questions (to decide before a checklist)
 
 1. **Where mail lives**