{ "markdown": "# Changelog\n\nAll notable changes to the Sporting Scouter design system (`ui/`, `theme.css`, and the published reference site) are documented here.\n\n## [3.5.1] - 2026-10-08\n\nConsumers: run `ds:sync`. This release changes `theme.css` (one keyframe), so a monorepo sync is needed. Two fixes for defects found by an app consuming 3.5.0 (both older than 3.5.0), and one documentation decision.\n\n### Fixed\n\n- **Dialog off-centre**: the dialog is centred with Tailwind v4 `-translate-x-1/2 -translate-y-1/2`, which sets the CSS `translate` property, while the `ss-pop-in` keyframe also centred it with `transform: translate(-50%, -50%)`. Both applied, so the dialog ended up half its width to the left and half its height up (measured: a 300x200 box ended at -150, -100 from the centre). The keyframe now animates `translate` and `scale`, and ends exactly where the recipe centres it. `theme.css` only; `dialog()` is unchanged.\n- **`ChoiceGroup` did not type-check**: it passed `error && string` and `hint && string` to `describedBy()`, which takes `string | false | null | undefined`. `error` and `hint` are `ReactNode`, so the expression can be `0` and `tsc --strict` failed (TS2345) for any app importing the `ui-react` index. It now passes `error ? ... : undefined`.\n- Guard test `dialog-motion.test.mjs`: fails on both old forms.\n\n### Changed\n\n- **Like is no longer documented as gated by a feature flag.** The review card reference page and its snippet render **Like** on every written public review (a score-only row has none). What a signed-out visitor must do to like or to report is the app's decision. No recipe change.\n\n### Notes\n\n- Copy and URLs are not defined in the design system: the wording of \"Incentivised review\", the list summary, \"How reviews are checked\" and the dispute states, and where the verification link points, belong to product and legal. The reference page's wording tables are examples.\n\n## [3.5.0] - 2026-10-08\n\nConsumers: run `ds:sync`. Additive, with one removal (`header: 'legacy'`, see Removed): no slot was removed or renamed and every default is unchanged. `bash docs/superpowers/plans/assets/review-card-recipes/check.sh` runs the real recipes (real `tailwind-variants` and `tailwind-merge`) on `main` and on this tree for the 3.4.0-era `reviewCard`, `reviewBreakdown`, `reviewList`, `reviewReply`, `scoreBar`, `ratingStars` and `button` calls: 521 slot outputs have identical class sets, with one intended exception: the review card `footer` now wraps (`flex-wrap`), so actions do not spill out of a narrow card. `theme.css` and the tokens are unchanged.\n\n### Added\n\n- **`reviewCard()` redesign** (`/review-card/`): `layout: 'row'` renders a review with no text as one compact band (the card's identity block with the date below the name, the figure and stars, and Report) instead of a near-empty box. A `headerEnd` slot holds the figure and the stars; the figure is `ratingStars().value`, so 4.6 is no longer shown as five bare stars. Padding moved from `surface` to `compoundVariants`, so a row can be shorter than a card.\n- **One action row, after the review**: every action is in `footer`, in the same place on every surface, after the body and any reply. Public: **Like** (leading, on every written public review; a `like` slot, an `aria-pressed` toggle with a constant label and a filled icon). Organiser: **Reply publicly** and **Reply in private** (trailing). **Report** is always available, on every review and every surface, for anyone who can see it, and is always the last action, at the right edge: on a score-only row too (the row's children are flat, identity, figure and stars, Report, so Report stays on the right when the row wraps).\n- **Two reply threads with different audiences**: the **public reply** (`thread`: one per review, public once the review is published) and the **private thread** (`privateThread`, `privateTitle`, `privateHint`, `privateStatus`). In the API today the private thread is the **dispute timeline** (the organiser's statement, the athlete's evidence, Sporting Scouter's decision), only while a review is held before publication, and the athlete answers from an emailed link, not a signed-in view. `reviewReply()` gains `visibility: 'public' | 'private'` (private: a chat bubble), `from: 'self' | 'other' | 'platform'` (the viewer's own messages on the right, tinted; the other party's on the left; Sporting Scouter full width with its icon) and `audience`, `attachment` and `event` slots. Who wrote what is never position or tint alone: the sender's name is always written (yours as \"{name} (you)\") with a caption of what they did. The audience and the state are written (icon plus words, `statusDot` plus words), never colour alone. While the thread is **open** the footer, right after the chat, has **Reply in private** (a \"Private message\" form that names who can see it); once it is **closed**, or the review is published, the thread stays readable and the button is gone. The public reply shows its audience in three states: only your team, public once the review is published (a held review), visible to everyone. The reference page lists the suggested wording for every dispute state and event. The package renders the private thread only where the app passes it: the API must not send it to a public payload. `ui/GAPS.md` G11 records the open product question (is \"Reply in private\" the dispute flow renamed, or new free messaging?).\n- **Incentivised-review disclosure**: a `disclosure` slot in `reviewCard()`, visible text with the `gift` icon, always the last line of the identity block (under the name and the date), on every surface and in both layouts (the same stack in a row), never a tooltip and never colour alone. It is not a new provenance component or token. The requirement (EU Omnibus Directive) and the wording are product and legal copy, to be confirmed by legal; the package ships no strings. \n- **List summary** (`reviewList().summary`, `summaryItem`): a line above every review list, outside the `