Docs: aidlc-state, audit en production-readiness-checklist bijgewerkt met de fixes en bevindingen van 9-10 nov (o.a. MasterModule__MasterUrl)

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-10 00:12:27 +01:00
co-authored by Claude Sonnet 5.5
parent 3f060a89fc
commit d8d150e10d
3 changed files with 33 additions and 2 deletions
@@ -11,6 +11,9 @@ Scope: ASF test and SlpSoftware test now; SlpSoftware production after Bryan's a
- **Status**: Configured in code (log levels), alert rule documented and still to be created in Sentry by a person
- **Approach**: journal plus Sentry Error events for configuration-related mail failures; no threshold, no dashboard (Q4 B)
## Master host setting (added 2026-11-10)
- **`MasterModule__MasterUrl` is required on every master host** (SlpSoftware test and production): https, no path. The shipped `appsettings.json` only holds a placeholder. Without a valid value the master logs `MasterModule:MasterUrl is not an absolute http(s) address` and skips its background checks (before the fix it overwrote slaves with the placeholder and their polls failed). The variable is NOT `Master__MasterUrl`. Production readiness item: set and verify it, then restart the master and watch the slaves' `master_poll_recovered`.
## Additional Readiness Items
- **Deliverability (Q6 A)**, before SlpSoftware production: send test mails to a Gmail and an Outlook mailbox and check in "show original" that SPF, DKIM and DMARC pass and are ALIGNED with the From domain (the From domain, the SPF-authorised server and the DKIM signing domain must match); DMARC stays `p=none` for now. Facts at 2026-11-08: both `slpsoftware.nl` and `andreaslop.nl` publish `v=spf1 a mx include:smtp.spf.ziggo.nl ~all`, a `dkim._domainkey` record and DMARC `p=none`. For ASF the sender `no-reply@andreaslop.nl` through `mail.andreaslop.nl` is expected to align (the host is the domain's own `a`/`mx`); to be proven by the real test mail.
- **Real test mails (Q8 A)**: one per site on test (invitation, new link by mail, password reset, a notice) to an address of Bryan; the approval of this feature depends on them.
@@ -29,8 +32,11 @@ Scope: ASF test and SlpSoftware test now; SlpSoftware production after Bryan's a
1. **ASF production on IIS** (decided 2026-11-09): not worked out here. The Pi-specific assumptions (systemd unit, `shared/env`, journalctl, scp deploy, reverse-proxy Pi) and what changes on IIS are listed in `deployment/deployment-plan.md`; a later ASF-production feature must settle them (environment variables and secrets, restart, logs, deploy path, hosting model, database and mail-server reachability).
2. Sentry alert rule to be created (monitoring setup).
3. Real test mails on ASF test and SlpSoftware test.
4. Merge to master / SlpSoftware production: not approved yet (the branch is already on ASF test and SlpSoftware test).
4. Merge to master / SlpSoftware production: not approved yet (the branch is already on ASF test and SlpSoftware test). Bryan first tests both test environments including run 635 (65ee73f: logout hang, mail card gutter); the merge then happens on his explicit go.
5. Per-site DMARC tightening later (stays `p=none` now).
6. Confirm the dark-mode mail card in the Gmail app (Gmail and non-Gmail account) and Outlook with a real test mail; the layout uses inline styles and Outlook selectors but the clients' own colour conversion cannot be tested in code.
7. Decisions left to Bryan (not built): own rate-limit policy for `Setup/status`, judging the admin token only on a real block (log noise), a visible error state with "Reload" and a fetch timeout; the contact-feature gate change is in `features/contact-feature/contact-feature-prereqs.md`.
8. CI of run 635 (65ee73f) was not confirmed green when this was written.
## Overall Readiness
- **Ready for Production**: Not yet. SlpSoftware production needs the real test mails, the alert rule and Bryan's approval; ASF production is a separate piece of work.