Skip to content

duobrain v0.1.8

Choose a tag to compare

@github-actions github-actions released this 05 Oct 06:44
· 6 commits to main since this release

duobrain v0.1.8

When the two of you build something next to duobrain — a manual for a specific task, a dashboard of what
you delivered — you can now reuse its UI without making design tokens of your own. The dashboard's look is a
published set of --duo-* tokens, and every release says whether they changed. In the product repository, run:

npx duobrain@0.1.8 install

Design tokens: introduced (73 tokens)

Added

  • tokens.css. 73 --duo-* CSS custom properties: colors by role (surfaces, text, sidebar, lime
    accent, the two people, status), type (fonts, sizes, weights, leading, tracking), a 4px spacing scale,
    radii, shadows and layout widths. Load it from .duobrain/src/dashboard/public/tokens.css,
    node_modules/duobrain/src/dashboard/public/tokens.css or a running dashboard at /tokens.css.
  • Tokens page. tokens.html (open the file, or /tokens on a running dashboard) lists every token
    with its value and the dashboard elements that use it, then draws each element with the real styles
    next to the tokens it reads. Click a name to copy var(--duo-…).
  • A promise about names. Within 0.x.y a token is never renamed or removed; renames happen only in a
    new minor version, with the old name kept as an alias for that version. The paths above stay the same.
  • A line about tokens in every release note from now on, like the one above. release:check compares
    tokens.css with the previous release and refuses a note that does not match, or a patch release that
    removes a token. node scripts/token-changes.mjs <previous-tag> prints the line.

Changed

  • The dashboard's stylesheet is built only from these tokens. Spacing moved onto the 4px scale and
    near-identical colors were unified, so a few gaps are 1–4px wider, buttons and tabs are slightly
    rounder, and the sample-data banner uses the same amber as paused badges.
  • Variable names from before 0.1.8 (--bg, --ink, --lime, …) still work as aliases until 0.2.0.

See docs/design-tokens.md for
the token groups, naming and stability rules. Nothing in the work record changed, so a partner on 0.1.7
keeps working.

Verification

The suite contains 135 tests, including checks that the dashboard reads only defined tokens and no
literal colors or sizes, that tokens.html matches the current styles, and that the token pages are
served under the dashboard's content security policy. The release check was exercised against a
mismatched line, a matching line and a token removed in a patch release.