spec(split-reel): v10 -- a client's call is drawn in the client's colour - #6182
Merged
Merged
Conversation
What: split-reel v10 decides the colour of the closing call the way v7 decides its words. The house's gold #FFD700 is drawn only on the house's own reel. Every other reel ends in the order's colour, else hers, else a neutral #FFFFFF on #000000. Why: SplitTalkingHead passed no colour to CallToAction, and CallToAction hard-coded the house's gold. So every client's split reel closed in the house's colour. The host's ctaHighlight prop carried a word, not a colour, and nothing drew it. v10 adds: - consts HOUSE_CALL_COLOR, NEUTRAL_CALL_COLOR, CALL_GROUND, CALL_AS_IS, CALL_SHADE, CALL_REFUSED and GIVEN_CALL_COLOR_UNREADABLE_REFUSED; - call_colour_from, which picks from the same place cta_for picks the words from; - call_drawn: a colour that reads is drawn as it is. An unreadable colour the order gave is refused before the charge. Hers is drawn in its nearest shade that reads. Checked on the Mac with a fresh t27c built from master f244bd2: - `t27c test-report --verbose specs/automation/split-reel.t27`: 28 of 28 pass, FAIL 0. VERSION is 10. - spec-controls (the v9 list plus 9 v10 controls): 43 of 43 caught, rc 0. - validate-vacuity does not list split-reel. - The seal was re-saved: tests 28/28. Host: gHashTag/999-multibots-telegraf, branch fix/split-reel-v10-client-call-colour. Closes #6149 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
This was referenced Oct 4, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
split-reel v10: a client's split reel closes on the client's call colour, never the house's gold
#FFD700.call_colour_from(house_own, given, given_is_house, hers)picks the colour from wherecta_forpicks the words: the order's, else hers, elseNEUTRAL_CALL_COLOR#FFFFFFonCALL_GROUND#000000.HOUSE_CALL_COLORis drawn only on the house's own reel.call_drawn(from, readable): a colour that reads is drawn as it is. An unreadable colour the order gave is refused BEFORE the charge (GIVEN_CALL_COLOR_UNREADABLE_REFUSED = true). Hers is drawn in its nearest shade that reads.Why
SplitTalkingHeadpassed no colour toCallToAction, andCallToActionhard-coded#FFD700. So every client's reel ended in the house's colour. The host'sctaHighlightprop held a word ('PERSONA', '/START'), not a colour, and nothing drew it. The host PR removes it.Verified (on the Mac, t27c built fresh from master f244bd2 into a private target dir)
t27c test-report --verbose specs/automation/split-reel.t27: 28 of 28 pass, FAIL 0 (the table was read, not the rc).tri spec-controls(the v9 list plus 9 v10 controls): 43 of 43 caught, rc 0.t27c validate-vacuity: split-reel is not listed.t27c seal --save: tests 28/28..githooks:tri hooks pre-commitPASSED, L1 PASSED.Order
This PR merges first. The host PR in gHashTag/999-multibots-telegraf (branch
fix/split-reel-v10-client-call-colour) vendors this spec byte-for-byte.Closes #6149
🤖 Generated with Claude Code