feature adopts layout="carousel" (first Phase B adopter)Add carousel to feature's layout matches and map its feature-item collection onto the shared carousel contract — the first proof that adoption is config + contract + CSS with zero new behavior code. Per SPEC-100 Phase B.5.
Tracking started Jun 25 — check back for trends.
carousel (from the canonical const) to feature's layout matches — trivial now that the axis + data-layout emission exist (WORK-467).feature's item container/items onto the shared contract ([data-name="items"] / [data-name="item"]) so the generalised behavior binds with no per-rune behavior code.feature; wire the collapse-to="carousel" option (WORK-473) so layout="grid" collapse-to="carousel" gives grid-desktop / swipe-row-mobile.layout="carousel" is an all-viewport carousel (graceful degradation); an explicit desktop carousel shows the JS nav affordances (via the shared behavior).feature accepts layout="carousel", emits the shared contract, and styles the track.feature.feature [data-layout="carousel"] selectors.feature's layout axis + emission.feature binds to.plugins/marketing/src/tags/feature.ts, plugins/marketing/src/config.ts (Feature).