Bump @phcdevworks/spectre-tokens from 3.5.0 to 4.0.0

[dependabot]

Bumps @phcdevworks/spectre-tokens from 3.5.0 to 4.0.0.

Release notes

Sourced from @​phcdevworks/spectre-tokens's releases.

Tailwind Integration Removal and Token Contract Expansion

Release Title: Tailwind Integration Removal and Token Contract Expansion

Contract change type: breaking

Removed

• Removed the tailwindTheme and tailwindPreset root exports and the TailwindTheme type export. Spectre no longer ships a Tailwind CSS integration — consumers should use the tokens runtime object and index.css custom properties directly, or generateCssVariables for a custom CSS build. contract.manifest.json's requiredOutputs.tailwind section and the check:tailwind validation gate are removed. The consumer smoke and integration fixtures no longer exercise a Tailwind config.

Added

• Added colors.palette — the full Tailwind CSS v4.3 raw color ramp (red, orange, amber, yellow, lime, green, emerald, teal, cyan, sky, blue, indigo, violet, purple, fuchsia, pink, rose, slate, gray, zinc, neutral, stone, mauve, olive, mist, taupe; steps 50-950), ported to hex for consistency with the rest of colors. This is a new, separate sub-namespace alongside the existing brand/neutral/accent/success/warning/error/info ramps in colors and does not replace or alter them. src/css.ts's color CSS-variable generation now walks colors recursively to support this extra nesting depth, so existing two-level color groups are unaffected.
• Added typography.heading (h1-h6) and typography.body role tokens so downstream consumers have a semantic heading/body contract instead of hand-picking raw typography.scale steps. Each role is a complete, portable token (fontFamily, fontSize, lineHeight, fontWeight, letterSpacing) expressed via {typography.scale.*} / {typography.families.*} references rather than bare scale/family keys, so every consumer format receives a real, resolvable reference instead of a string only the CSS generator knows how to interpret. Runtime (JS/TS) consumers receive the portable {...} reference strings as-is, for the consumer to resolve; DTCG output emits the same references as standards-based aliases; CSS output resolves them at generation time to fully resolved literal values — --sp-heading-{level}-{family,size,line-height,weight,letter-spacing} and --sp-body-{family,size,line-height,weight,letter-spacing} — none of these variables reference another --sp-font-* variable at runtime. A new check:typography-refs gate, part of npm run check, validates that every heading/body role field is a {...} reference (never a bare string) that resolves to a real typography.json leaf, and that generated CSS carries the fully resolved value through with no dangling references.

Changed

• src/css.ts: color CSS variable generation now recurses through arbitrary nesting depth under colors instead of assuming exactly two levels (group/step), to support colors.palette.<hue>.<step>.

... (truncated)

Changelog

Sourced from @​phcdevworks/spectre-tokens's changelog.

[4.0.0] - 2026-07-25

Release Title: Tailwind Integration Removal and Token Contract Expansion

Contract change type: breaking

Removed

• Removed the tailwindTheme and tailwindPreset root exports and the TailwindTheme type export. Spectre no longer ships a Tailwind CSS integration — consumers should use the tokens runtime object and index.css custom properties directly, or generateCssVariables for a custom CSS build. contract.manifest.json's requiredOutputs.tailwind section and the check:tailwind validation gate are removed. The consumer smoke and integration fixtures no longer exercise a Tailwind config.

Added

• Added colors.palette — the full Tailwind CSS v4.3 raw color ramp (red, orange, amber, yellow, lime, green, emerald, teal, cyan, sky, blue, indigo, violet, purple, fuchsia, pink, rose, slate, gray, zinc, neutral, stone, mauve, olive, mist, taupe; steps 50-950), ported to hex for consistency with the rest of colors. This is a new, separate sub-namespace alongside the existing brand/neutral/accent/success/warning/error/info ramps in colors and does not replace or alter them. src/css.ts's color CSS-variable generation now walks colors recursively to support this extra nesting depth, so existing two-level color groups are unaffected.
• Added typography.heading (h1-h6) and typography.body role tokens so downstream consumers have a semantic heading/body contract instead of hand-picking raw typography.scale steps. Each role is a complete, portable token (fontFamily, fontSize, lineHeight, fontWeight, letterSpacing) expressed via {typography.scale.*} / {typography.families.*} references rather than bare scale/family keys, so every consumer format receives a real, resolvable reference instead of a string only the CSS generator knows how to interpret. Runtime (JS/TS) consumers receive the portable {...} reference strings as-is, for the consumer to resolve; DTCG output emits the same references as standards-based aliases; CSS output resolves them at generation time to fully resolved literal values — --sp-heading-{level}-{family,size,line-height,weight,letter-spacing} and --sp-body-{family,size,line-height,weight,letter-spacing} — none of these variables reference another --sp-font-* variable at runtime. A new check:typography-refs gate, part of npm run check, validates that every heading/body role field is a {...} reference (never a bare string) that resolves to a real typography.json leaf, and that generated CSS carries the fully resolved value through with no dangling references.

Changed

• src/css.ts: color CSS variable generation now recurses through arbitrary nesting depth under colors instead of assuming exactly two levels

... (truncated)

Commits

• a1c83c2 Restore jiti as a devDependency for ESLint's flat config loader
• 29b677e Fix CI break from README heading-casing normalization
• cdf8d3f Normalize README section order and heading casing
• 09ef269 Normalize .gitignore structure and add Thumbs.db
• 59afbaa Make Copilot/Jules commit-authority grant self-visible in their own files
• 605488f Grant Codex autonomous release authority (tag + GitHub Release)
• 0c51372 Normalize AI agent docs and grant equal commit authority
• ab4a7ef Release v4.0.0: finalize Tailwind removal docs and version bump
• 94586a6 Remove Tailwind CSS integration exports
• 5133d49 Add Phase 10 utility-token roadmap in TODO
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Looks like @phcdevworks/spectre-tokens is up-to-date now, so this is no longer needed.