[MattDHill]

Bumps @start9labs/start-sdk to 3.1.0, which adds Forward Email to the SMTP provider presets in this package's SMTP settings, and bumps the revision with release notes for it.

Also maps the selected SMTP security onto Synapse's email.force_tls, for both custom and system SMTP. Without it Synapse always connected in plaintext and upgraded with STARTTLS, so a server set to TLS (implicit TLS, port 465), the new preset included, never got a TLS handshake and email notifications timed out. The release notes cover the fix, and README and instructions describe the two modes.

🤖 Generated with Claude Code

[helix-a]

[P2] Honor the SMTP security mode before exposing the new preset.

SDK 3.1.0 defaults Forward Email to TLS on port 465, but startos/main.ts copies only its host/port/credentials into Synapse's email block, discarding smtpCredentials.security. Synapse 1.163.0 defaults email.force_tls to false; require_transport_security: true requires STARTTLS, not implicit TLS. Choosing the new preset with its defaults therefore attempts plaintext SMTP against an implicit-TLS listener and times out instead of sending notifications.

The proposal sets email.force_tls from the selected security mode for both custom and system SMTP, models the field, and documents TLS/STARTTLS behavior in README and instructions. It also corrects the same existing mapping error for other TLS presets. Verified the config semantics against Synapse v1.163.0's emailconfig.py and send_email.py.

Proposed changes: e3cfff1...proposal/102

Verification: merge-tree against master passes; SDK 3.1.0 matches npm's latest; two npm installs leave the lockfile unchanged. The original head and proposal both pass make x86 (typecheck, formatting, bundle, pack), and the returned s9pk manifests were inspected. A mocked-effects check exercising the proposal's actual main function passes custom/system TLS, custom/system STARTTLS, and disabled SMTP. All three PR CI checks pass, including x86 and arm builds. Live email delivery was not tested.

Helix-Harness: pi
Helix-Model: openai-codex/gpt-6.1-sol

[helix-a]

The SMTP security issue from my previous review is resolved in 7110b62. Both custom and system SMTP now map the selected mode to email.force_tls, and the file model, README, instructions, and localized release notes agree. The implementation matches the proposal I previously checked for custom/system TLS, custom/system STARTTLS, and disabled SMTP; the documentation variation is fine.

Verified merge-tree against current master, SDK 3.1.0 against npm's latest, and git diff --check. Ran helix-build --output synapse_x86_64.s9pk -- make x86 on the updated head: typecheck, formatting, bundling, and packing pass; inspected the returned manifest. Live email delivery was not tested. CI architecture builds were still running when inspected; this approval does not claim they have passed.

Helix-Harness: pi
Helix-Model: openai-codex/gpt-6.1-sol