Features retiring

Write a Halden transactional email notifying Sage workspace admins that three Sage features are being retired. Cover the facts below.

The email is addressed to the Sage admin. Three features will be gradually retired from Sage by Friday, December 11, 2026 as Halden consolidates onto its sandboxed workspace architecture. The email explains what is changing, what replaces each feature, and what the admin needs to do.

The three features, each with its retirement date and replacement path:

• Canvases. Retires Friday, December 11, 2026. Existing canvases migrate automatically to sandboxed Canvases; the migration itself needs no action. Sandboxed execution and file creation must be enabled to keep creating and using canvases. Details: https://halden-email.s3.amazonaws.com/help/sandboxed-execution
• Tones. Retires Friday, November 20, 2026. Custom tones are migrating to Playbooks; the migration itself needs no action. Sandboxed execution and file creation must be enabled to use custom tones as playbooks. Alternatively, tones can be converted to instructions, and for org-wide effect set as organization instructions. The Tutor tone becomes a playbook as well. Playbooks: https://halden-email.s3.amazonaws.com/help/playbooks Organization instructions: https://halden-email.s3.amazonaws.com/help/organization-instructions
• Project file search. Changes Friday, October 30, 2026. Halden is improving how Sage searches and uses files in Projects. From that date, project file search requires sandboxed execution and file creation to be enabled.

A closing section reassures admins that every replacement runs on sandboxed execution and that admin controls are in place. Two controls:

• Network access settings: egress is configured at the organization level as on, limited, or off, to match the security posture. Details: https://halden-email.s3.amazonaws.com/help/sandboxed-execution
• Pre-approved network domains: when egress is set to limited, traffic is restricted to a vetted allowlist. The current list: https://halden-email.s3.amazonaws.com/help/network-allowlist

Turning on sandboxed execution and file creation at https://halden-email.s3.amazonaws.com/help/sandboxed-execution is the one action the email asks for.

The footer points to the Halden help center at https://halden-email.s3.amazonaws.com/help, gives the postal address, and links to https://halden-email.s3.amazonaws.com/privacy and https://halden-email.s3.amazonaws.com/terms

Dark mode should be supported.

Use /world/halden-email for brand chrome and CSS; the transactional family fits. Use the absolute HTTPS URLs from tokens.json; do not use /world/ paths as image src.

Leave the HTML in output/email.html, a plain-text version in output/email.txt, and the subject in output/meta.json as {"subject": "..."}. Don't include From, To, or Date headers.