docs(cryptify): document staging_mode config option that bypasses SMTP

[dobby-coder]

Cryptify added a new staging_mode boolean to CryptifyConfig. When true, send_email skips SMTP entirely and writes a single [STAGING] Email NOT sent ... log line containing the full intended recipients, sender, sender_attributes, expiry, download URL, and uuid. The upload finalize flow completes normally.

Source PR

encryption4all/cryptify#152 — feat: staging_mode that logs email instead of sending it (merged 2026-05-13). Closes encryption4all/postguard#174.

What needs documenting in docs/repos/cryptify.md

Add staging_mode to the configuration parameters table near the existing SMTP settings:

Parameter	Description	Example
staging_mode	When true, send_email skips SMTP entirely and logs the intended email metadata at info level. The upload finalize still returns Ok. Defaults to false. Intended for staging deploys where real email delivery is undesirable.	false

A short subsection (or note) should explain:

• How to enable: set staging_mode = true in the active config file (e.g. conf/config.toml).
• What gets logged: a single [STAGING] Email NOT sent (staging_mode=true). Would have notified recipients=[...] from sender=... attributes=[...] lang=... expires=... confirm=... notify_recipients=... download_url=... uuid=... line.
• SMTP settings (smtp_url, smtp_port, smtp_username, smtp_password, smtp_tls) are ignored when staging_mode is on, so they can stay unset in a staging environment.

The <small>[Source: src/config.rs#L15-L53]</small> link below the table should be updated to point at the cryptify commit that introduced the field.

Verification

• Cross-check src/config.rs and src/email.rs at the merge commit of cryptify#152 for the exact field name, default, and log format.
• Run npx vitepress build docs.
• Style: align with postguard-docs/CLAUDE.md (no em dashes, minimal bold, no banned words).

[dobby-coder]

/dobby

[dobby-coder]

The bot is on it! This agent will eagerly read cryptify#152, learn the staging_mode field, and add it to docs/repos/cryptify.md with proper source links. So happy to help with the docs, sir/madam!

[dobby-coder]

Plan

Update docs/repos/cryptify.md to document the new staging_mode config option from cryptify#152 (merge commit ca6be91).

Changes

1. Add staging_mode row to the Configuration parameters table (after session_ttl_secs, before usage_db):

   • Description: when true, send_email skips SMTP and logs the intended email metadata at info level; the upload finalize still returns Ok. Defaults to false. Intended for staging deploys where real email delivery is undesirable.
   • Example: false

2. Add a short subsection (### Staging mode) below the existing chunk_size paragraph, covering:

   • How to enable (staging_mode = true in conf/config.toml).
   • What gets logged: the exact [STAGING] Email NOT sent ... line (recipients, sender, attributes, lang, expires, confirm, notify_recipients, download_url, uuid).
   • SMTP settings are ignored when staging mode is on, so they can stay unset in staging.

3. Update the source link under the config table from the old commit to ca6be91913d0313791c5bbeb3dd16152c85855c6, pinning a line range that covers the struct (so the staging_mode field is visible at the link).

Verification

• Verified staging_mode: bool exists in src/config.rs at ca6be91 (line 35 of CryptifyConfig, line 17 of RawCryptifyConfig).
• Verified the log format in src/email.rs#L320-L333 matches the description in this issue.
• Will run npx vitepress build docs and inspect rendered HTML before opening the PR.
• Style: no banned words, no em dashes, no bold beyond what already exists.

Files touched

• docs/repos/cryptify.md only.

No tests in this repo. Risk is low (docs-only change).

[dobby-coder]

Opened #86 with the staging_mode docs. Build passes, source links verified at the cryptify#152 merge commit (ca6be91).