panel-notifications: agreed, taken into work

The owner, 2026-10-12: "Делаем". Roadmap status agreed, 0/10; planned cut
2.3.0. The first step is the mockups, shown to him before any code.

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

docs/development.md

@@ -127,6 +127,7 @@ than the default «meaningful step» rule in [§ Commits and release build](#com
 | 14 | DMARC ingest drops and bounds, full backup from the panel, no queue in a backup | `2.0.1` (PATCH) |
 | 15 | inbound-antispam-panel | `2.1.0` (was `1.10.0`, reordered 2026-10-09) |
 | 16 | delivery-log-storage | `2.2.0` |
+| 17 | panel-notifications | `2.3.0` |
 
 Docs-only prep (checklists in plans, no product code) uses the same per-step
 commit rule but **no** version cut until the next product stage ships.

docs/plans/panel-notifications.md

@@ -1,6 +1,6 @@
 # Plan: panel-notifications
 
-**Status:** candidate - the design questions are closed with the owner (2026-10-12); taking it into work still needs his word  
+**Status:** agreed 2026-10-12 - the design questions were closed with the owner and he took it into work ("Делаем")  
 **Date:** 2026-10-12  
 **Version:** `2.3.0` MINOR (one migration; opt-out by a switch).
 
@@ -92,7 +92,7 @@ Server › Settings, the SPF check on Server › Health - is the first step, sho
 to the owner before any code ([panel-redesign.md](panel-redesign.md)
 § Enforcement).
 
-## Implementation checklist (draft; counted from the day the item is agreed)
+## Implementation checklist
 
 - [ ] Mockups: Account checkbox, Settings switch, Health SPF check, help topic; accepted by the owner (`design:` commit)
 - [ ] Migration and store: user flag, instance switch, event state

docs/roadmap.md

@@ -35,7 +35,7 @@ in `git log` and [CHANGELOG.md](../CHANGELOG.md).
 | template-data-typing | Typed structs for template data instead of `map[string]any` | candidate | — | — |
 | structured-logging | `log/slog` with levels and fields | candidate | — | — |
 | review-2026-08-followups | Remaining findings of the 2026-08-19 code review | candidate | — | — |
-| panel-notifications | E-mail notifications about important events | candidate, design closed | — | [plans/panel-notifications.md](plans/panel-notifications.md) |
+| panel-notifications | E-mail notifications about important events | agreed | 0/10 | [plans/panel-notifications.md](plans/panel-notifications.md) |
 | delivery-log-storage | Keep a message's `mail.log` lines with its send-log row | shipped `2.2.0` | 8/8 | [plans/delivery-log-storage.md](plans/delivery-log-storage.md) |
 | password-reset | Password reset by e-mail | candidate | — | — |
 | phone-desktop-mode | A phone browser in "desktop site" mode gets the phone navigation | candidate | — | — |
@@ -46,7 +46,8 @@ in `git log` and [CHANGELOG.md](../CHANGELOG.md).
 development convenience): **panel-redesign** shipped as `2.0.0` (2026-10-11) and
 **inbound-antispam-panel** as `2.1.0` (2026-10-12), built in the new component
 kit — styling its two screens once instead of twice. **delivery-log-storage**
-shipped as `2.2.0` the same day. Nothing is agreed after it: every remaining
+shipped as `2.2.0` the same day. Agreed after it: **panel-notifications**
+(`2.3.0`); every other remaining
 item is a candidate. panel-docs shipped in
 [CHANGELOG.md](../CHANGELOG.md) `[1.8.0]`; dmarc-reports in `[1.7.0]`
 (its ingest path first ran in `2.0.0` and was reviewed on 2026-10-11, see
@@ -363,10 +364,10 @@ restarts so a reboot does not re-announce everything. The screens are not
 drawn: the Notifications box was taken out of `account` and `settings` on
 2026-10-10 and is redrawn as the first step.
 
-**Version:** `2.3.0` MINOR; `candidate` - the design questions were closed
+**Version:** `2.3.0` MINOR; agreed 2026-10-12 - the design questions were closed
 with the owner on 2026-10-12
-([plans/panel-notifications.md](plans/panel-notifications.md)); taking it into
+([plans/panel-notifications.md](plans/panel-notifications.md)) and he took it into
-work still needs his word.
+work the same day.
 
 ---