Workflows first run: apply the saved Email brand on Make it yours #267

Map: Map: build the Workflows first run, from template gallery to first send
Spec: Spec: Workflows first run

Cast: Opus 5.5 (UI)

Waits on: Make it yours (native blocker), and the saved Email brand layer of the consolidated stack on PostHog#111479 (see the consolidation note on #198; it replaces PostHog#111060). The conductor dispatches this ticket only once that layer has merged. Reuse the one branded starter builder, brandedStarter.ts from PostHog#111479.

Question

When the project has a saved Email brand, does Make it yours show the template's emails in that brand from the start?

Delivers end to end. Added by Michael (2026-10-05) as a later slice.

• When the project has a saved Email brand, Make it yours applies it to every email of the picked template when the screen opens: logo, colors and font, the way the Email brand work builds its branded starter template. Reuse that code; do not add a second brand-to-design mapping.
• A short line says the brand was applied, with a link to edit the Email brand.
• Without a saved Email brand, nothing changes. Optionally a quiet link to set one up, if the Email brand flow has an entry point to link to.
• Applying is a snapshot: the created workflow keeps the emails as they were when created.

Test seams. A kea logic test with the API mocked at the HTTP layer: with and without a saved Email brand, the designs loaded into Make it yours and the create payload. Stories for both states at full width and 520px.

Write scope. The first-run folder under products/workflows/frontend/, and tests and stories. Overlap: the Email brand code from PostHog#111060; use it as it is.

Acceptance criteria

• A project with a saved Email brand sees every email of the template in its brand on Make it yours, and the created workflow keeps it.
• A project without one sees the template's own design.
• Screenshots on this ticket.

How to build (map #253)

• /implement + /tdd red-green-refactor, outside-in, at the seams named above. Mock only what is external.
• Repo skills apply where the diff touches their area: /writing-tests, /writing-ui-components, /writing-kea-logics, /adopting-generated-api-types, /writing-user-facing-copy, /writing-code-comments.
• Branch from upstream/master, push to the fork, open a draft PR on PostHog/posthog against master. A stacked PR carries its parent's commits and a "Stacked on" note.
• Then /qa-swarm. Shipped means a draft PR it handed off. Never mark ready, enqueue or merge.