[pbroom]

toSrgbGamut/toP3Gamut only reduce OKLCH chroma at fixed L and h, which
under-shoots what CSS (and colorjs.io) produce: oklch(0.7 0.35 150) maps
to C=0.193 instead of the CSS Color 4 result C=0.210.

• Add GamutMapOptions { method?: 'chroma-reduction' | 'css' } to
  toSrgbGamut, toP3Gamut, toSrgbGamutInto and toP3GamutInto (types
  GamutMapMethod/GamutMapOptions exported). 'css' implements the CSS
  Color 4 binary search with local MINDE (deltaE OK JND 0.02, epsilon
  1e-4, clip in the target gamut) allocation-free on scratch objects; it
  matches colorjs.io toGamut({ method: 'css' }) to ~1e-15 dE_OK for both
  sRGB and P3.
• Default stays 'chroma-reduction': the CSS method shifts L and h, while
  contrast regions, plane geometry, slider tracks and the driver's
  displayed state rely on L/h being preserved, so it is not strictly
  better for existing tests or callers. Both methods return colors that
  pass inSrgbGamut/inP3Gamut (with GAMUT_EPSILON slack) unchanged and
  snap the lightness endpoints, so membership and mapping stay
  consistent.
• toSrgbGamut/toP3Gamut get a one-argument overload so passing them
  straight to Array.prototype.map keeps type-checking (the index
  argument is ignored at runtime).
• driver: mapDisplayedColors(requested, { gamutMapMethod }) and
  CreateColorStateOptions.gamutMapMethod forward the method; the default
  is unchanged.
• maxChromaAt reuses one scratch probe instead of allocating a Color per
  bisection step.
• The gamut-region solver's search-gap handling (oklchChromaField) is
  about maxChromaAt's bisection bracket, not the mapping method, so it
  is left as is.

Part of a stacked set of PRs (#204 → #221) from the color-kit assessment. Validated per branch with pnpm build and pnpm test; lint, format, typecheck, size, artifact, preprod and agents checks pass at the top of the stack.

🤖 Generated with Claude Code

[pbroom]

• refactor(react)!: remove UI components; ship state and plane hooks only #249
• docs(react): rebuild the React docs around the plane hooks #248
• feat(react): add plane renderer, geometry and adaptive-quality hooks #247
• feat(docs): syntax highlighting palette for code samples #246
• feat(docs): native API map at /api/map #245
• docs: add concept pages, guides and entry-point narratives #244
• feat(docs): live plane hero on home and the example system #243
• feat(docs): generated API reference from TypeDoc JSON #242
• refactor(core)!: derive plane query budgets from step counts and drop PlaneWithSense #241
• fix(react): render input aria-label once, on the inner input #240
• fix(driver): map absolute percents as range positions and keep tiny-step precision #239
• fix(core): uncap saturate chroma and resolve planeHue as an OKLCH hue #238
• fix(driver): reject unknown gamuts and align validation error types #237
• chore(docs): remove Sandpack, the shadcn kit and the legacy docs shell #236
• docs(core,driver,react): document the public API #235
• chore: pin control-kit to a commit with its own pnpm workspace #234
• docs: update implementation backlog for the contrast solver replacement #232
• refactor(react)!: remove ColorPlane's deprecated edge option and webgl renderer alias #231
• fix(driver): validate the gamut in getColorAreaFallbackPoint #230
• feat(driver,react): keep the previous hue when an achromatic color is entered #229
• refactor(core)!: replace the hybrid contrast solver with chroma-column tracing #228
• perf(core): trim what contrastRatio pulls in #227
• perf(core): pack the named-color table #226
• feat(core): point 'p3' users to 'display-p3' #225
• chore: ignore local .claude files in prettier #224
• refactor(core)!: retire the legacy contrast-region engine #223
• fix(core): keep hybrid contrast contours connected through folds #222
• chore: add changesets for the assessment stack #221
• docs: generated API reference and repo polish #220
• chore: adopt changesets for versioning and release notes #219
• chore: fix facade peers, licensing, and lint ignores #218
• refactor(react): reuse core contrast and transfer functions #217
• refactor(core)!: make the contrast-region engine explicit #216
• refactor(core)!: remove pre-launch aliases and trim the root export surface #215
• refactor!: name the Display P3 space 'display-p3' everywhere #214
• refactor(driver): share pointer drag throttling between slider and area #213
• feat(react): keyboard, ARIA, disabled, and focus support for sliders and areas #212
• fix(react): stable refs, WebGL context loss, and handler composition #211
• fix(react): apply controlled updates against the latest snapshot #210
• feat(core): selectable gamut mapping method #209 👈 (View in Graphite)
• fix(core): compute contrast from unrounded values #208
• fix(core): consistent achromatic hue handling and single transfer function #207
• feat(core): parse CSS Color 4 syntax #206
• fix(core): reject malformed color input instead of producing NaN #205
• chore: add fast-check and axe-core test dependencies #204
• docs: graphics and performance APIs demo page #203
• feat(core): tuple and typed-array interop for GPU and three.js #202
• feat(core): allocation-free *Into variants for hot paths #201
• feat(core): interpolation space option for mix/interpolate/generateScale #200
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[greptile-apps]

Confidence Score: 4/5

[Medium risk] Adds selectable gamut mapping algorithm to color processing.

The PR is not ready to merge because requested-color updates can silently discard the selected mapping method.

Findings

1.  Selected mapping resets on update ▶

Summary

The PR adds selectable chroma-reduction and CSS gamut mapping to core and forwards the choice through driver state creation.

• It retains chroma reduction as the default and adds mapping tests and API documentation.
• Subsequent state re-derivation does not retain an explicitly selected CSS method.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A["createColorState(method: css)"] --> B["State: displayed with CSS; meta.method = css"]
  B --> C["useColor requested-color update"]
  C --> D["createColorState without method"]
  D --> E["State: displayed with chroma reduction; meta.method reset"]

Loading

_{Reviews (1) · Last reviewed commit: "feat(core): selectable gamut mapping met..."}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
color-kit	Ready	Preview	Oct 10, 2026 7:11pm UTC

[pbroom]

Merge activity

• Oct 10, 6:47 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Oct 10, 7:06 PM UTC: Graphite rebased this pull request as part of a merge.
• Oct 10, 7:06 PM UTC: @pbroom merged this pull request with Graphite.