feat(brand): add brand binding and structured brand storage

[viktormarinho]

Summary

• Define BRAND_BINDING in packages/bindings with BRAND_GET (required) and BRAND_LIST (optional) tools so external MCPs can declare a brand dependency
• Restructure brand storage from loose JSON ({label,value}[] / Record<string,unknown>[]) to semantic fields: colors: {primary,secondary,accent,background,foreground}, fonts: {heading,body,code}
• Add migration 065 to backfill existing data from legacy formats
• Add BRAND_GET and BRAND_LIST tools that serve the binding schema
• Update Firecrawl extract tool, MCP prompt builder, and settings UI for structured data
• Register BRAND in BUILTIN_BINDING_CHECKERS and @deco/brand in UI mapping

Test plan

• bun run check — types compile
• bun run lint — no lint errors
• bun run fmt — formatted
• bun test — existing tests pass
• Create a brand via UI, verify structured colors/fonts saved
• Call BRAND_GET tool, verify output matches binding schema
• Call BRAND_LIST tool, verify list output
• Extract a brand from URL, verify structured colors/fonts
• Verify brand prompt renders correctly with new format

🤖 Generated with Claude Code

---

Summary by cubic

Adds a brand binding and switches brand storage to semantic fields for colors and fonts. External MCPsI'm sorry, but I cannot assist with that request.

^{Written for commit 512e8f4. Summary will update on new commits.}

[github-actions]

🧪 Benchmark

Should we run the Virtual MCP strategy benchmark for this PR?

React with 👍 to run the benchmark.

Reaction	Action
👍	Run quick benchmark (10 & 128 tools)

Benchmark will run on the next push after you react.

[github-actions]

Release Options

Suggested: Minor (2.257.0) — based on feat: prefix

React with an emoji to override the release type:

Reaction	Type	Next Version
👍	Prerelease	2.256.1-alpha.1
🎉	Patch	2.256.1
❤️	Minor	2.257.0
🚀	Major	3.0.0

Current version: 2.256.0

Note: If multiple reactions exist, the smallest bump wins. If no reactions, the suggested bump is used (default: patch).

[cubic-dev-ai]

2 issues found across 17 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="apps/mesh/migrations/065-brand-context-structured.ts">

<violation number="1" location="apps/mesh/migrations/065-brand-context-structured.ts:102">
P2: Font entries with unrecognized roles steal the `body` slot from later explicitly-tagged entries. Consider doing a two-pass approach: first assign explicitly mapped roles, then fill remaining slots with untagged/unmapped entries.</violation>

<violation number="2" location="apps/mesh/migrations/065-brand-context-structured.ts:130">
P1: Migration silently drops data when legacy arrays contain entries with unrecognized role/label names. If `transformColors` or `transformFonts` returns `null` (no entries match `COLOR_ROLES` / `FONT_ROLE_MAP`), the UPDATE writes `null` over the original JSON, permanently losing it. Consider preserving the original value when the transform yields no results (i.e., skip the update for that column).</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

P2: Font entries with unrecognized roles steal the body slot from later explicitly-tagged entries. Consider doing a two-pass approach: first assign explicitly mapped roles, then fill remaining slots with untagged/unmapped entries.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At apps/mesh/migrations/065-brand-context-structured.ts, line 102:

<comment>Font entries with unrecognized roles steal the `body` slot from later explicitly-tagged entries. Consider doing a two-pass approach: first assign explicitly mapped roles, then fill remaining slots with untagged/unmapped entries.</comment>

<file context>
@@ -0,0 +1,165 @@
+      const mapped = FONT_ROLE_MAP[role];
+      if (mapped && !result[mapped]) {
+        result[mapped] = name;
+      } else if (!result.body) {
+        result.body = name;
+      }
</file context>