The composed cta goes live in the marketing plugin

site/staged-runes/cta.md was reviewed with the hero in WORK-689. It goes live on the path WORK-702 opens: the marketing plugin's runeDir.

changeset-release/main View source

Tracking started Nov 3 — check back for trends.

Relationships

changeset-release/main current ready

Nov 3, 08:02 PMce58f41
Content editedby Claude
plan: WORK-703, WORK-704 done; BUG-019 fixed
Nov 3, 07:39 PMfe601a4
Created (ready)by github-actions[bot]
Nov 3, 06:02 PMf91f637
Content editedby Claude
plan: v0.48.0 — compositions go live, and the rune page intro (SPEC-187)

and 2. Reviewed, and every difference explained: done in WORK-689.
The composition adds align (start | center | end), which the plugin cta does not declare; that is additive, so no existing content changes meaning. This item confirms no other attribute or content form differs, or adds the codemod and waits a release.
No dependency on a draft primitive spec: confirmed when the item starts.

cta.md moves from site/staged-runes/ into the marketing runeDir unchanged, and the staging site's runes.prefer entry for cta is removed
The plugin cta's schema, theme config entry and cta.css are removed, and the CSS coverage sets are updated
Both copies of contracts/structures.json and the SEO baseline are regenerated, and the diff is reviewed in the PR description
The cta reference page describes the rune as a composition, and every page that uses cta renders unchanged
A breaking changeset and a migration note list what authors and themes lose (rf-cta* classes) and what changed