docs: clear shipped plans and closed work out of the documents

Owner, 2026-10-18: "Надо почистить документы от устаревшего и сделанного."

- Deleted, shipped: plans/delivery-log-storage, from-header-binding,
  inbound-antispam-panel, inbound-upstream-result, panel-dkim-signing,
  panel-notifications, and the own-mta-builds analysis (its three rows
  shipped as 2.6.1, 2.7.0, 2.8.0). What outlived them moved first: when a
  filter-list counter is worth a migration, and the notifications' "when"
  table, into architecture.md; the sender check's own-process trigger into
  security.md. Code comments that cited them point at architecture.md or
  security.md; CHANGELOG keeps their names, unlinked.
- Kept, marked closed: audit-2026-10-12, assumptions-2026-10-14 and
  security-audit-2026-10-17 - the code cites their finding ids in 50-84
  files. Their file:line refs are of the tree each audited.
- roadmap.md: open work only - stage H of the security audit (the owner's),
  go-milter-upstream (the owner posts), and queue-table, which the
  redesign left undecided and only its own shipped section still named;
  Dropped and Ideas as they were. 2.x versioning instead of 1.x.
- development.md: the 47-row planned-version-cuts table (history, in the
  CHANGELOG) gone; a stage's last step now removes its roadmap item and
  plan. Docs map lists the closed audits.
- panel-redesign.md: the done checklist out; Room for roadmap items says
  which drawn screens are unbuilt and why.
- Stale facts fixed: schema-migrations.md and architecture.md at schema 14
  (0013's users columns and user_links, 0014's secure TLS mode);
  security.md's accepted risk "profile saved without the password" - the
  e-mail asks for it since 2.14.0.

Tests: go build, go vet; go test of cmd and the touched internal packages
pass except logtail's three Windows-bound rotation tests (rename of an open
file; CI is Linux). Only comments changed in Go.

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

internal/inbound/lists.go

@@ -340,9 +340,9 @@ type Usage struct {
 // counts for every entry of the deciding list that fits it: the journal does
 // not say which of two fitting entries the filter met first.
 //
-// A counter kept with each entry would not depend on the journal; the plan
-// (docs/plans/inbound-antispam-panel.md, Filter list usage) says when that is
-// worth a migration.
+// A counter kept with each entry would not depend on the journal;
+// docs/architecture.md (the antispam filter lists) says when that is worth a
+// migration.
 func (l *Lists) Usage() (map[int64]Usage, error) {
 	entries, err := l.store.ListSpamListEntries()
 	if err != nil {

internal/logtail/sendercheck.go

@@ -8,7 +8,7 @@ import (
 )
 
 // The sender check is attached to Postfix strictly: while the panel does not
-// answer on its socket, mail is deferred (docs/plans/from-header-binding.md).
+// answer on its socket, mail is deferred (docs/architecture.md § Sender check).
 // How many submissions that happened to is read here, from what Postfix
 // writes about it, and shown on Server > Health. It is the figure that also
 // sees a panel which is running and not answering.

internal/milter/sender.go

@@ -22,7 +22,7 @@ import (
 
 // The sender check: a message's From: line is held against the application
 // that sends it, under the rule Postfix holds the envelope sender to
-// (docs/plans/from-header-binding.md). The signer signs with the key of the
+// (docs/architecture.md § Sender check). The signer signs with the key of the
 // domain the login belongs to (sign.go), and a receiver holds that signature
 // to the domain of this line (DMARC, RFC 7489 § 3.1.1), so without the check
 // an application could send under the server's signature as another domain

internal/milter/sign.go

@@ -1,6 +1,6 @@
 package milter
 
-// The DKIM signer (docs/plans/panel-dkim-signing.md): the panel's own milter
+// The DKIM signer (docs/architecture.md § DKIM signing): the panel's own milter
 // that signs what applications send on 465/587 with the key of the domain
 // their login belongs to, and what the panel itself sends with the key of
 // the server's name. Each of the two is a socket of its own, so the socket a

internal/notify/notify.go

@@ -5,7 +5,7 @@
 //
 // Each subject has a row of state in the database, so a thing is said once and
 // a restart says nothing again. The rules of when a message goes out are the
-// owner's (docs/plans/panel-notifications.md § When a message is sent) and
+// owner's (docs/architecture.md § Notifications) and
 // live in this file; what the messages say is in text.go, how they leave in
 // mailer.go.
 package notify

internal/web/handlers/handlers_notifications_test.go

@@ -13,7 +13,7 @@ import (
 	"github.com/mixeme/selfpost/internal/web/auth"
 )
 
-// The panel pages of notifications (plans/panel-notifications.md): the user's
+// The panel pages of notifications (docs/architecture.md § Notifications): the user's
 // checkbox on Account, the instance's switch and the DNS records of the server's
 // own name on Server › Settings, and the state of those records on Server ›
 // Health. What is sent and when is internal/notify's and tested there.