release: 1.1.0: Domain-admin role and internal/web package split

The first MINOR after 1.0.0: send-only DMARC guidance in the panel, AGPL packaging on every page, and an internal split of `internal/web` ahead of domain-admin work. Upgrading runs one SQLite migration (empty defaults; existing DNS guidance is unchanged until you set a report address).
Changed:
  - `internal/web` split into subpackages (`web/view`, `web/auth`, `web/validate`,
Added:
  - panel: DMARC guidance for send-only relays — the suggested `_dmarc` record
  - AGPL packaging hygiene: [NOTICE](NOTICE) names the copyright holder and the
  - [docs/roadmap.md](docs/roadmap.md) — candidate item **visual-style** (panel

Full detail: CHANGELOG.md (1.1.0).

docs/roadmap.md

@@ -26,15 +26,15 @@ in `git log` and [CHANGELOG.md](../CHANGELOG.md).
 
 | ID | Topic | Status | Plan |
 |---|---|---|---|
-| web-split | Splitting `internal/web` | **agreed** | [plans/web-split.md](plans/web-split.md) |
 | domain-admin | Domain administrator role | **agreed** | [plans/domain-admin.md](plans/domain-admin.md) |
 | inbound-relay | Inbound relay (backup-MX / forwarding) | **agreed** | [plans/inbound-relay.md](plans/inbound-relay.md) |
 | contributing | `CONTRIBUTING.md` | candidate | — |
+| visual-style | Обновление визуального стиля | candidate | — |
+| dmarc-reports | DMARC aggregate report ingestion and panel UI | candidate | [plans/dmarc-reports.md](plans/dmarc-reports.md) |
 
-**Recommended order** (not binding): **web-split → domain-admin →
-inbound-relay** — first the package split, then role-wide authorisation, then
-the new vertical slice of the inbound relay. Deviating is allowed; there are no
-hard phases here.
+**Recommended order** (not binding): **domain-admin →
+inbound-relay** — role-wide authorisation first, then the inbound relay vertical
+slice. Deviating is allowed; there are no hard phases here.
 
 After a context reset, pick an item marked `agreed` or `in progress`, then work
 the checklist in its linked plan.
@@ -57,8 +57,7 @@ engine stays outside the image, only the attachment point is provided.
 
 **Dependencies / risks:** a finished outbound path; open relay and backscatter;
 a wider attack surface (port 25 accepting mail).
-**Order:** recommended after [web-split](plans/web-split.md) and
-[domain-admin](plans/domain-admin.md).
+**Order:** recommended after [domain-admin](plans/domain-admin.md).
 **Version:** target bump `1.x`; `2.x` possible — to be settled once the
 implementation lands.
 
@@ -78,32 +77,13 @@ assigned domains (one or several).
 **Done when:** see [plans/domain-admin.md](plans/domain-admin.md).
 
 **Dependencies / risks:** a users table, the role in the session, authorisation
-in every handler, setup and backup. **Order:** recommended after
-[web-split](plans/web-split.md), before
+in every handler, setup and backup. **Order:** recommended **before**
 [inbound-relay](plans/inbound-relay.md).
 **Version:** `1.x` MINOR, given a compatible migration of the current
 administrator into a global one.
 
 ---
 
-## web-split
-
-**Goal:** deliberately split `internal/web` (or settle on keeping the package
-flat) before it grows under inbound-relay and domain-admin.
-
-**Boundary:** an internal refactor; the panel's behaviour for the operator does
-not change.
-
-**Done when:** the package is split along the chosen scheme, or it is settled
-that it stays flat — see [plans/web-split.md](plans/web-split.md).
-
-**Dependencies / risks:** exporting a package-private API. **Order:**
-recommended **first** among the agreed features (before domain-admin and
-inbound-relay).
-**Version:** `1.x`; on its own it does not force a break.
-
----
-
 ## contributing
 
 **Goal:** `CONTRIBUTING.md` in the root — the dev loop, the checks to run
@@ -119,3 +99,52 @@ it.
 **Dependencies / risks:** with a single developer and no PRs, this is low
 priority.
 **Version:** no bearing on semver.
+
+---
+
+## visual-style
+
+**Goal:** refresh the control panel's visual design — typography, colour tokens,
+spacing, and component styling — without changing operator workflows or panel
+behaviour.
+
+**Boundary:** presentation only (`panel.css`, templates, static assets); no new
+features. Styling must stay compatible with the panel CSP — rules live in
+`panel.css`, not inline (see [security.md](security.md) and the stylesheet
+header).
+
+**Done when:** the panel reflects an agreed visual direction (starting
+reference: [assets/selfpost-proof.html](assets/selfpost-proof.html)); light and
+dark schemes remain supported; readability and contrast are preserved.
+
+**Dependencies / risks:** CSP constraints on how styles are applied; visual
+regression across pages; low priority relative to functional work — take up
+after explicit agreement, independently of the feature roadmap order.
+**Version:** no bearing on semver.
+
+---
+
+## dmarc-reports
+
+**Goal:** SelfPost receives DMARC aggregate reports (RFC 7489) on SMTP,
+parses the gzip/XML payloads, and shows pass/fail summaries in the panel — so
+the operator does not need an external DMARC service or a separate mailbox
+workflow.
+
+**Boundary:** an extension of v1.0 — not IMAP/webmail and not a general
+inbound relay. A dedicated inbound path for report messages only; forensic
+reports (`ruf=`) out of scope for v1.
+
+**Done when:** see [plans/dmarc-reports.md](plans/dmarc-reports.md).
+
+**Dependencies / risks:** inbound SMTP in the image (may share infrastructure
+with [inbound-relay](plans/inbound-relay.md) but must not require backup-MX);
+storage and retention of parsed summaries; the `admin.dmarc_report_email` and
+`domains.dmarc_rua` settings added in the DMARC template work must stay the
+source of truth for `rua=` in DNS guidance.
+
+**Order:** after the DMARC `rua=` settings ship; may follow or overlap with
+inbound-relay depending on how port 25 acceptance is structured.
+
+**Version:** `1.x` MINOR.
+