chore: release prep — design-system changelog - #17
Closed
mrhegemon wants to merge 1 commit into
Closed
Conversation
Document the merged CI design-system theme refactor for release: - CHANGELOG.md (Keep a Changelog) with an Unreleased "Changed — Design system" entry covering the canonical teal --primary (#0f717a / #abd4d8), self-hosted Abel + Source Code Pro fonts, enriched design tokens v0.2.0, the design-canon lint gate (scripts/lint-canon.mjs + style-canon-lint.yml), and refreshed light/dark UI screenshots. - Safe polish: define --gradient-brand and --gradient-hero in the default (:root) dark theme so the enriched gradient tokens exist in both themes. Additive only, no component consumes them yet; lint-canon passes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Member
Author
|
Closing — CHANGELOG.md approach reverted per owner (not the intended release-prep artifact). |
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
1 participant
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.
Release-prep for the merged design-system theme refactor (PRs #14–#16, all on
main).What's in this PR
CHANGELOG.md (new, Keep-a-Changelog style) — an
## [Unreleased]→### Changed — Design systementry that factually documents what landed for thepublic/web UI:--primary— light#0f717a/ dark#abd4d8(dark is default), theme toggle persisted tolocalStorage.--success/--warning/--info), brand/hero/aurora gradients, radius scale, elevation scale — inlined intostyle.css, mirroring the CI canon (@companionintelligence/tokens/ CI-Hubglobals.css). Note: tokens are inlined CSS custom properties, not an npm dependency.scripts/lint-canon.mjs+style-canon-lint.yml(fails on non-teal--primaryin any notation; warns on hardcoded hex).docs/ui/, referenced from the README.Safe polish — defined
--gradient-brandand--gradient-heroin the default (:root) dark theme so the enriched gradient tokens exist in both themes (previously only in[data-theme="light"]). Purely additive: no component consumes these tokens yet, so nothing renders differently.node scripts/lint-canon.mjs .passes; braces balanced.Release readiness
main: green — latest push (PR feat: adopt CI enriched palette v0.2.0 tokens #16 merge) shows CI, Publish container, Style canon lint, and CodeQL allsuccess.JIC_VERSION "0.3.0"(src/config.h). A minor bump (→0.4.0) is reasonable to mark the design-system release, but is not applied here — recommendation only.See agent report for full release-readiness detail.