From b866f8fecb3f163362d47680fb044a5a82083f4c Mon Sep 17 00:00:00 2001 From: only21mil Date: Sat, 31 Oct 2026 18:58:14 +0000 Subject: [PATCH 1/2] docs: composer banner guidance names a consumer that still exists ComposerActivityStatus.tsx was deleted in #25401, but docs/internals/web-ui.md still links it as the reference consumer and the ui-consistency review agent still names it. Point both at ComposerPlanFollowUpBanner.tsx. The review agent also stops citing ComposerStashBadge.tsx, which styles its own Root and Row and so contradicts the "no styling of their own" claim it was an example of. Co-Authored-By: Claude Opus 5.5 --- .macroscope/check-run-agents/ui-consistency.md | 2 +- docs/internals/web-ui.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.macroscope/check-run-agents/ui-consistency.md b/.macroscope/check-run-agents/ui-consistency.md index 047dafbdd4be1..ed6d5860579e9 100644 --- a/.macroscope/check-run-agents/ui-consistency.md +++ b/.macroscope/check-run-agents/ui-consistency.md @@ -44,7 +44,7 @@ The reference for how this codebase wants UI built is the composer banner system - `ComposerBanner.tsx` exports one object of small slot components (`Root`, `Row`, `Icon`, `Content`, `Actions`, `Dismiss`, `Children`, and so on). Each slot owns its own Tailwind classes, exposes a `data-slot` attribute, takes `className` and spreads the rest of its props, and uses `cn` so callers can adjust without overriding. Variants and density are props on `Root`, not ad hoc class strings at call sites. Where a slot needs a real control it renders `Button` from `ui/` rather than a styled `