feat: register T1 (pending, verify)

features/runtime_settings_injection.feature

@@ -15,13 +15,13 @@ Feature: Runtime settings are read once at startup
       CORS_ALLOWED_ORIGINS on every router build,
       api/handlers/auth.shouldCookieBeSecure reads ENVIRONMENT on every
       Login/Register/Logout call, internal/infrastructure/mailer.MailRepository.Send
-      reads SMTP_EMAIL, SMTP_PASSWORD, SMTP_HOST and SMTP_PORT on every call,
-      and internal/infrastructure/persistence.ImageRepository.Create and
-      .Delete read UPLOAD_DIR on every call
+      reads SMTP_LOGIN, SMTP_SENDER, SMTP_PASSWORD, SMTP_HOST and SMTP_PORT
+      on every call, and internal/infrastructure/persistence.ImageRepository.Create
+      and .Delete read UPLOAD_DIR on every call
     And this slice introduces internal/infrastructure/config.Settings, a
       plain struct with fields Environment, CorsAllowedOrigins ([]string),
       PublicURL, UploadDir, JWTSecret, DBFile, Port and an Smtp sub-struct
-      (Email, Password, Host, Port)
+      (Login, Sender, Password, Host, Port)
     And cmd/server/main.go's initEnvVariables still loads the .env file and
       applies the same defaults and required-var checks as before, then
       builds exactly one config.Settings value from the process environment,
@@ -34,9 +34,9 @@ Feature: Runtime settings are read once at startup
       the upload dir, and the router's logging and CORS setup receive the
       environment string and the CORS origins list as parameters
     And after this slice, os.Getenv (and os.LookupEnv) for ENVIRONMENT,
-      CORS_ALLOWED_ORIGINS, SMTP_EMAIL, SMTP_PASSWORD, SMTP_HOST, SMTP_PORT
-      and UPLOAD_DIR appears only inside cmd/server/main.go and
-      internal/infrastructure/config
+      CORS_ALLOWED_ORIGINS, SMTP_LOGIN, SMTP_SENDER, SMTP_PASSWORD,
+      SMTP_HOST, SMTP_PORT and UPLOAD_DIR appears only inside
+      cmd/server/main.go and internal/infrastructure/config
     And a component built from a config.Settings value keeps behaving
       according to the values it was built with even if the process
       environment changes afterwards, because it holds the captured values,
@@ -109,8 +109,9 @@ Feature: Runtime settings are read once at startup
       Secure attribute set to true
 
   Scenario: The mailer is constructed from injected SMTP settings, not the environment
-    Given a config.Settings value with Smtp.Email "notify@example.com",
-      Smtp.Host "smtp.example.com" and Smtp.Port 587
+    Given a config.Settings value with Smtp.Login "smtp-login@example.com",
+      Smtp.Sender "notify@example.com", Smtp.Host "smtp.example.com" and
+      Smtp.Port 587
     And internal/infrastructure/mailer.NewMailRepository is called with that
       Smtp settings value and no SMTP_* environment variable set
     Then constructing the MailRepository does not read any SMTP_*