Crucible training

Write an announcement email for the Day 0 training at Crucible London, Sableforge's conference where engineers and AI agents build together, sent to developers who subscribed to Sableforge event news. The recipient's first name is Morgan.

Crucible London runs on October 21, 2026, and opens on October 20 with a full day of hands-on technical training. The training lineup page is https://sableforge.s3.amazonaws.com/crucible/london/training and people register at https://sableforge.s3.amazonaws.com/crucible/london/register

These are full-day sessions for engineers running production frontend cloud infrastructure, covering deploy pipelines, Forgeframe at scale, and edge rendering.

The morning half of the day has three sessions -

• Deploy pipelines for production frontend cloud
• Forgeframe at scale: routing, caching, and data
• Edge rendering for high-traffic applications

The afternoon half of the day has three sessions -

• AI agents in a large codebase with Sableforge Draft
• Preview environments and safe rollout patterns
• Observability and incident response on Sableforge

Training is included with the Crucible + Training pass, which is $250 early bird. Crucible only is $200. Early bird runs through September 25. Registering for Crucible London is the main action of the email; the training lineup and the CFP are secondary links, and the two pass prices with the early-bird deadline sit together as a small comparison.

The CFP closes September 10, two days out. It is a brief closing note after the lineup and pricing, with an inline link only. Anyone running Sableforge in production who has something to share has one last window to submit. The CFP page is https://sableforge.s3.amazonaws.com/crucible/london/cfp

The docs destination is https://sableforge.s3.amazonaws.com/docs

The banner image is https://sableforge.s3.amazonaws.com/email/crucible/training-banner.png - a charcoal workbench carrying a copper anvil, with four staggered panels of a build stack rising beside it.

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

Dark mode should be supported.

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.