Files
slp-modular-cms/aidlc-docs/features/identity-email-notifications/aidlc-state.md
T

6.6 KiB

AI-DLC State Tracking

Project Information

  • Feature Name: E-mail notifications for identity (invitation, new activation link, password reset)
  • Feature Slug: identity-email-notifications
  • Project Type: Brownfield
  • Start Date: 2026-11-08
  • Current Stage: OPERATIONS - code complete and on ASF test and SlpSoftware test; waiting for Bryan's testing of run 635 (65ee73f) on both test environments before any merge
  • Branch: feature/identity-email-notifications (branched from feature/andreaslop-site-hosting at e9feb37; own branch, not merged anywhere)
  • Request Type: Feature (Bryan chose real e-mail over a workaround button; relayed by session "CMS & API")

Workspace State

  • Existing Code: Yes
  • Reverse Engineering Needed: No - reuse aidlc-docs/_shared/reverse-engineering/
  • Workspace Root: K:\Development\Projects\SlpModularCms

Code Location Rules

  • Application Code: Workspace root (NEVER in aidlc-docs/)
  • Feature Documentation: aidlc-docs/features/identity-email-notifications/ only

Language Configuration

  • Documentation Language: English
  • Conversation Language: User Language (Dutch)
  • Note: Inherited from the other features in this workspace.

External Requester (hand-off)

  • Session: "CMS & API", relays Bryan's decisions. Questions for Bryan go through that session. No implementation before the answers are in.
  • Reference implementation (read-only): K:\Development\Projects\SimpleDeckApp (MailKit/MimeKit SmtpEmailSender, IEmailSender.SendAsync(to, subject, htmlBody, ct), EmailOptions section "Email").

Extension Configuration

Extension Enabled Decided At
Security Baseline Yes (Q15 A) Requirements Analysis
Property-Based Testing Yes - partial PBT-02,03,07,08,09 (Q16 B) Requirements Analysis

Operations Configuration

  • Include Operations Phase: Yes (Q17 A)
  • Decided At: Requirements Analysis

Stage Progress

INCEPTION

  • Workspace Detection - Complete
  • Requirements Analysis - P1-P5 decided by Bryan (relayed); requirements.md updated
  • [~] User Stories - skipped (see execution plan)
  • Workflow Planning - approved (relayed)
  • Application Design - approved (relayed); D1 picker in invite dialog, D2 stamp in access token (U3)
  • Units Generation - U1 mail-foundation, U2 identity-mail-flows, U3 password-reset

CONSTRUCTION

  • U1 mail-foundation - Infrastructure Design (construction/mail-foundation/infrastructure-design/infrastructure-design.md), Code Generation done, build and tests green (see code-summary.md); hand-back pending
  • U2 identity-mail-flows - Code Generation done, build and tests green (see construction/identity-mail-flows/code/code-summary.md); includes D1 and D2; hand-back pending
  • U3 password-reset - Code Generation done, build and tests green (see construction/password-reset/code/code-summary.md); hand-back pending (D2, the security stamp in the access token, was built in U2)
  • [~] Build and Test - summary written (construction/build-and-test/build-and-test-summary.md); manual real test mail on ASF test pending
  • Operations (deployment, monitoring, production readiness incl. SPF/DKIM alignment checklist)
  • Hand-back written (handback.md); Operations questions issued (operations/plans/operations-questions.md), nothing executed until answered

OPERATIONS

  • Deployment Setup - approved answers Q1 A, Q2 A (ASF production separate, IIS), Q3 A, Q7 A; operations/deployment/*
  • Monitoring Setup - Q4 B (config-related mail failures at Error), Q5 A; log-level change built and tested; operations/monitoring/*
  • Production Readiness - checklist written; verdict: not yet (real test mails, Sentry rule, Bryan's approval); operations/production-readiness-checklist.md
  • Open for a later feature: ASF production on IIS (hosting assumptions listed in operations/deployment/deployment-plan.md)

Late fixes after the first test deploys (2026-11-09/10, all on the branch)

  • Mail layout: SLP red, dark-mode button, logo swap (dark variant) and white badge, site name next to the logo, dark card that stands out (page #0a0e14, card #273244, 1px border), inline card border #d1d5db and Outlook data-ogsb/data-ogsc rules, 16 px gutter around the card. Light mode unchanged. Real behaviour in the Gmail app (Gmail and non-Gmail account) and Outlook still to be confirmed by a real test mail.
  • Master/slave status: the slave's fail-open grace period now runs from the master's last contact (poll, push, registration), not from the last successful poll (a pushed "not available" fell open at the next failed poll). Poll failures log master_poll_failed reason=... detail=... (first stack frame, url_absolute, scheme, key_present; never URL, key or message).
  • Master URL: the shipped appsettings.json holds a placeholder; the hourly/start-up integrity check (no request) used it and re-registered slaves with it, so their polls failed. Now MasterUrlRules (absolute http(s), no credentials/query/fragment): the master skips background checks on an unusable value (warning), a slave refuses one (400 invalid_master_url), the poller reports invalid_master_url. The variable is MasterModule__MasterUrl (section MasterModule); an earlier note said Master__MasterUrl, which is never bound - corrected in operations/deployment/deployment-plan.md.
  • Availability gate: an expired token on a blocked route answers 401 (not 503) so the app refreshes its session and passes as admin; missing, forged, wrong-key and non-admin tokens stay 503.
  • Session at start-up: a refresh without a verdict (429/5xx/network) ends in an "unreachable" retry screen, not as a guest; Retry-After is sent (refresh 15 s) and honoured (max 15 s per wait).
  • Logout hang: with the CMS switched off (own setting or master) signing out froze the app. Cause: the AppLayout effect "NotAvailable -> go to /dashboard" also ran for a guest, which the authenticated route sent back to /login - an endless navigation loop. Fixed (only for an authenticated user); test LogoutWhileCmsOff.test.tsx never finished on the old code.
  • Not built, decisions with Bryan: own rate-limit policy for Setup/status, judge the admin token only when a request is really blocked, a visible error state with "Reload" and a fetch timeout (see ../contact-feature/contact-feature-prereqs.md, local commit 3f060a8, not pushed).
  • Merge to master: not approved. Bryan wants to test both test environments first (including run 635 / 65ee73f); the CMS session may merge later on his explicit go (Gitea PR with merge commit and green CI unless he chooses otherwise).