docs(project): condense progress log, roadmap and test/infra docs

docs/smtp-configuration-concept.md

@@ -125,25 +125,7 @@ Verify mode is set in `tls_options` for port 587 (STARTTLS). For port 465 (impli
 
 ---
 
-## 12. Summary Checklist
-
-- [x] ENV: `SMTP_HOST`, `SMTP_PORT`, `SMTP_USERNAME`, `SMTP_PASSWORD`, `SMTP_PASSWORD_FILE`, `SMTP_SSL`.
-- [x] ENV: `MAIL_FROM_NAME`, `MAIL_FROM_EMAIL` for sender identity.
-- [x] Settings: attributes and UI for host, port, username, password, TLS/SSL, from-name, from-email.
-- [x] Password from file: `SMTP_PASSWORD_FILE` supported in `runtime.exs`.
-- [x] Mailer: Swoosh SMTP adapter configured from merged ENV + Settings when SMTP is configured.
-- [x] Per-request SMTP config via `Mv.Mailer.smtp_config/0` for Settings-only scenarios.
-- [x] TLS certificate validation relaxed for OTP 27 (tls_options for 587; sockopts with verify only for 465).
-- [x] Prod warning: clear message in Settings when SMTP is not configured.
-- [x] Test email: form with recipient field, translatable content, classified success/error messages.
-- [x] Join confirmation email: uses `Mailer.smtp_config/0` (same as test mail); on failure returns `{:error, :email_delivery_failed}`, error shown in JoinLive, logged for admin.
-- [x] AshAuthentication senders: graceful error handling (no crash on delivery failure).
-- [x] Gettext for all new UI strings, translated to German.
-- [x] Docs and code guidelines updated.
-
----
-
-## 13. Follow-up / Future Work
+## 12. Follow-up / Future Work
 
 - **SMTP password at-rest encryption:** The `smtp_password` attribute is currently stored in plaintext in the `settings` table. It is excluded from default reads (same pattern as `oidc_client_secret`); both are read only via explicit select when needed. For production systems at-rest encryption (e.g. with [Cloak](https://hexdocs.pm/cloak)) should be considered and tracked as a follow-up issue.
 - **Error classification:** SMTP error categorization currently uses substring matching on server messages (e.g. "535", "authentication"). A more robust approach would be to pattern-match on `gen_smtp` error tuples first where possible, and fall back to string analysis only when needed. Server wording varies; consider extending patterns as new providers are used.