Shipped recap

Write Trestle's marketing recap email, "What we shipped in H1 2026". It goes to everyone who signed up for Trestle and looks back at the first half of the year, grouped by product area. Cover the facts below, in this order.

Headline: What we shipped in H1 2026. A one-line introduction says the recap covers January through June 2026, area by area.

Quick links, a three-item list right after the introduction, each an inline text link:

• The full list of changes is in the changelog. https://trestle-email.s3.amazonaws.com/changelog
• The thinking behind the releases is on the blog. https://trestle-email.s3.amazonaws.com/blog
• Questions and requests go to the community. https://trestle-email.s3.amazonaws.com/community

Five areas follow, each with its own heading, a short bulleted list of what shipped, and a small illustration in the Trestle style. Every bullet is one sentence.

Area 1, Issues. Reference artwork: assets.illustrations.shippedIssues

• Sub-issues can be reordered by dragging, and the parent issue shows a count of completed children.
• Issue templates per team set default labels, priority, and assignee.
• Bulk edit changes up to 500 issues at once from the command menu.
• Due-date reminders arrive in the inbox 24 hours before an issue is due.

Area 2, Cycles. Reference artwork: assets.illustrations.shippedCycles

• A burn-up chart on every cycle shows scope changes alongside completed work.
• Unfinished issues roll over to the next cycle automatically when a cycle ends.
• Per-member capacity warns when someone is over-committed in a cycle.

Area 3, Projects. Reference artwork: assets.illustrations.shippedProjects

• Milestones group issues inside a project and appear on the roadmap timeline.
• Project updates carry a health status: on track, at risk, or off track.
• The roadmap timeline adds quarter and half-year zoom levels.

Area 4, Integrations. Reference artwork: assets.illustrations.shippedIntegrations

• Pull requests on GitHub and GitLab link to issues from the branch name and close them on merge.
• Slack notifications can be scoped per project instead of per workspace.
• API v2 adds webhooks for issue, cycle, and project events.

Area 5, Trestle Agent. Reference artwork: assets.illustrations.shippedAgent

• Coding sessions let a team assign an issue to Trestle Agent and receive a diff ready for review.
• Triage suggestions propose labels, a priority, and an assignee for new issues.
• The usage dashboard shows token usage and cost for every session, with spend limits per workspace and per user.

One call to action after the last area, a button labelled "Read the full changelog", linking to https://trestle-email.s3.amazonaws.com/changelog. It is the only button in the email; every other link is inline text.

Closing: Trestle publishes changes every week and the changelog carries the detail for each item above. Readers can reply to the email with what they would like to see in the second half of the year. Sign-off from the Trestle Team.

The recipient receives this because they signed up for Trestle. Use the Trestle marketing footer: it names Trestle, Inc., gives the postal address 418 Span Street, Portland, OR 97209, and links to Privacy at https://trestle-email.s3.amazonaws.com/privacy, Terms at https://trestle-email.s3.amazonaws.com/terms, and Unsubscribe at https://trestle-email.s3.amazonaws.com/unsubscribe

Use /world/trestle-email for brand chrome and CSS (the product family). 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.