Documents build and test, operations and the approved privacy wording

Adds the build and test summary and instructions, the deployment and
monitoring plans, the production readiness checklist with the go-live
conditions, and the approved privacy draft (retention, controller).

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-10 23:40:11 +01:00
co-authored by Claude Sonnet 5.5
parent a1444b7b2a
commit d8847d8c3b
12 changed files with 136 additions and 20 deletions
@@ -0,0 +1,7 @@
# Monitoring plan: contact-form-cms
- **Events (Umami)**: only `contact-sent` and `contact-failed`, names only. No field values, token, idempotency key or captcha response anywhere in analytics, logs or Sentry.
- **Sentry**: the existing browser setup stays; the form logs nothing itself. Check once on the test site that a failed send does not put form values into a breadcrumb or event (Build and Test of the next deploy).
- **Server side (CMS)**: the contact module's message list (status, mail status, attempts) is the operational view; failed mails and spam counts are watched there. Owner: CMS sessions.
- **Watch after go-live**: ratio `contact-failed` to `contact-sent` in Umami; messages with mail status `failed`; captcha problem message shown (not counted separately, visible through failed sends).
- **Alerts**: none new on the web side; mail failures are shown in the CMS admin.