Repository navigation
crm-story-reel v29: brand kit -- saved client palette on every preview and the rendered end card #7008
Closed as not planned
Description
Refs gHashTag/999-multibots-telegraf#3806 (competitor gaps: brand kit on every preview).
Law: when the client has a saved palette, every template preview and the rendered end card take it; with none, both take END_CARD_DEFAULT_*; never the host theme green #00FF88. Ties to v27 gallery_preview_field. Stacks on #7000 (v28) and #6980 (v27).
User Scenarios
- Given a client has a saved brand palette, when a template preview is generated, then the preview uses the client's saved palette colors
- Given a client has a saved brand palette, when the end card is rendered, then the rendered end card uses the client's saved palette colors
- Given a client has no saved brand palette, when a template preview or end card is generated, then both use END_CARD_DEFAULT_* values and never the host theme green #00FF88
Requirements
- FR-001: The spec MUST define that every template preview reads the client's saved palette when present
- FR-002: The spec MUST define that the rendered end card reads the client's saved palette when present
- FR-003: The spec MUST define that absent a saved palette, both preview and end card fall back to END_CARD_DEFAULT_* constants
- FR-004: The spec MUST explicitly forbid the host theme green #00FF88 as a fallback for preview or end card
Success Criteria
t27c check specs/lsp/client.t27exits 0 with no diagnostics about missing palette fallback rules- 3 tests in the v29 brand kit suite pass: preview_with_saved_palette, endcard_with_saved_palette, preview_and_endcard_without_saved_palette
grep -r "00FF88" specs/lsp/client.t27returns no matches (host green not referenced)
Boundary
- specs/lsp/client.t27
Activity
gHashTag commentedon Oct 7, 2026
Reopened 2026-10-07: the bulk close of issues without a
## Boundarysection was reverted by the owner. Nothing to do here; this comment replaces the earlier close notice.github-actions commentedon Oct 15, 2026
Re-filed as #9599.
An attempt claimed this issue on 2026-10-08 and left an empty branch. A dispatch row that has spent its retry ceiling is released once and then keeps its issue for good, which is the right rule for a third identical failure and the wrong outcome for an issue nobody ever attempted twice. The new issue carries the same work, the same boundary, and today's brief.
Closing this one so the swarm can take the work again.