9e18f6ebb6
The planner output frequently contains BOTH `styleGuideName` (catalog pick) and `styleGuide.palette` (AI's hallucinated palette) — and the two often disagree. Empirically MiniMax / GLM gravitate to indigo `#6366F1` for the accent regardless of what catalog snippet they were just shown: the model picks 'warm-food-mobile-light' (orange catalog), copies the cream background `#FFF8F0` correctly, then invents `accent: #6366F1` for `plan.styleGuide.palette`. The previous seedDocVariablesFromStyleGuide preferred `plan.styleGuide.palette` first and only fell back to `plan.selectedStyleGuideContent` when the AI palette was missing — so the catalog accent was always overridden by the AI's invented one. Result: every brief seeded indigo, no matter how good the ranking and catalog match upstream were. Swap the priority: catalog content (designed by humans, high confidence) wins; AI-generated palette is the fallback when no catalog content was attached. The planner's catalog choice is preserved (`plan.styleGuideName`) so visible UX is unchanged for that signal — just the COLORS now come from the catalog rather than the model's bias. |
||
|---|---|---|
| .. | ||
| cli | ||
| desktop | ||
| web | ||