One drift report, three destinations

Two sibling web apps share one Figma library: one on Tailwind v3 with years of hand-picked palette classes, the other on Tailwind v4 with its own token block. The question the design system owner kept asking was how far either codebase had drifted from the design system, and whether the two apps still looked like siblings. The answer is to stop thinking of the report as something you open and start treating it as a file the pipeline routes. Dembrandt writes JSON with --json-only, a self-contained HTML report with --html and exits 1 when --compare finds drift, so every destination a pipeline can write to is a destination for the report. Three drift views feed three destinations. A source scan per app counts colour uses that bypass the tokens. A cross-app comparison resolves every colour in both apps to hex and matches it to the nearest token of the same role. Dembrandt supplies the third view: what the browser actually paints per route, compared against a snapshot of an approved release, which catches colours inherited from component libraries, chart palettes that inline their own colours, runtime-computed styles and dark mode that was never wired. Where the reports go depends on who reads them. The wiki is the record, updated on every push to main. The PR comment is the nudge, naming the exact off-token classes a change added. The Figma comment fires only when drift grows, so designers see regressions and never noise. The first run found all 17 shared roles differing between the two apps, including the same wrong shadcn accent colour in both.