Align ColorCraft’s trust-sensitive copy and analysis behavior#9
Merged
Conversation
Artsen
marked this pull request as ready for review
July 25, 2026 20:13
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.
Summary
Align ColorCraft’s production behavior, contracts, documentation, and tests so measured results are clearly separated from design guidance. This change keeps the existing Create, Review, Export, and Library workflow while correcting upload-limit, contrast, temperature, suggestion, runtime-status, and SVG-label behavior.
Base commit:
22f41e35d2bcd721e8aec3826724b49077fe14fdTrust and correctness problems corrected
Loopback onlyorLAN enabledbadge from resolved backend runtime metadata instead of displaying a static claim.Contract changes
Breaking response changes are intentional and applied across Pydantic models, Zod schemas, TypeScript consumers, tests, and documentation:
HarmonySuggestion.mood/moodis removed and replaced bycommon_associations/commonAssociations. No hidden legacy field is retained.transitional_count/transitionalCountandtransitional_ratio/transitionalRatio.balanceremovesbalancedand now permitswarm,transitional,cool,mixed, orneutral.network_mode/networkModefield withloopbackorlan.The existing extraction and analysis envelope shapes remain intact. The static dashboard manifest remains compatible; live metadata is authoritative for network exposure.
Contrast behavior changes
text,nonText, orfocusdiscriminator to each role check.Temperature behavior changes
Every meaningful chromatic hue now belongs to exactly one category:
Low-saturation colors remain excluded. Ratios use the total categorized chromatic count. A category is dominant only above 70%; otherwise the result is
mixed.neutralmeans there is no meaningful chromatic evidence.Suggestion-language changes
Suggestion descriptions now lead with measured hue, saturation, or lightness transformations. The UI uses
Common associationsandCommon applications, explains that suitability depends on context and assigned roles, and directs users to review role contrast before use.Runtime metadata changes
GET /metadatanow reportsnetworkModefrom the resolved web/API hosts, allowed origins, and configured browser API URL. The shell exposes the result accessibly asLoopback onlyorLAN enabled, with a factual unavailable fallback if metadata cannot be read.Validation
Passed the complete repository gate from the committed LF-clean tree:
Additional checks:
git diff --check: passed5174/4100; WVO5173/4000Screenshots
Review Overview and runtime status
Typed role contrast
Qualified suggestions
Remaining limitations