Labels filtering and colouring, mirroring shapes

[xinaesthete]

Annotated labels elements can now be filtered and coloured through the same API as shapes, as originally asked for. The work then pulled in three things it turned out to depend on: a shared colour-encoding core, a precomputed-buffer escape hatch, and the column dtype.

Labels filtering and colouring (37fd9ea)

A labels layer takes fillColorByColumn and a featureState with shapes' field names and meanings — fillColorByFeatureId / hiddenFeatureIds / fadedFeatureIds / filteredOpacityMultiplier — keyed by the label's integer instance id as a string, which is the identity the tooltip already resolves against the associated table.

Shapes resolve per-feature colour from a texture indexed by feature index. A label has no geometry — it is a raster pixel value — so the analogue is a lookup table indexed by label id: the bitmask fragment shader samples the instance-id raster and looks the integer up. Same primitive, same property that matters: a feature-state change re-uploads only the small table, never the tiles.

• The LUT texture is owned by LabelsLayer and shared across tile sublayers; per-tile textures would multiply a table that is already megabytes for a large segmentation.
• Picking consults the same table, so a hidden label can never be picked.
• LabelsResolver gains a fillColor resource (rows only — colours stay a pure projection, as for shapes).

Verified in the browser against the blobs fixture: labels hide, recolour and fade per id, and clearing the state returns them to the plain uniform-colour path.

Colour schemes, OkLab default (b150e86) — behaviour change

fillColorByColumn now carries the scheme, not just the column: categoricalPalette ('oklab' or your own RGB list) and numericRamp, both JSON-serializable so they survive a saved Render Stack.

The categorical default changes. It was a six-colour list that cycled, so a cell-type column with more than six categories drew two categories the same colour — a failure invisible in the render. The default is now the unbounded golden-angle OkLab scheme @spatialdata/layers already used for points, which is a pure function of the category index and cannot repeat. Pass an explicit list to pin specific colours.

Precomputed colour buffers (de1738b)

For colour driven by data a config cannot carry — a computed column, an external annotation, a live selection — the only route was a featureId → colour dictionary. That makes a host stringify integers it already had, then costs a Map copy and (for labels) a parse per entry, to arrive at the buffer the renderer wanted anyway.

FeatureColorBuffer { colors: Uint8Array; count: number } is now the currency both kinds render from, supplied via a featureColorResolver prop on SpatialCanvasViewer — a runtime attachment alongside hostLayerResolver / vivImagePropsResolver, deliberately not the Render Stack, whose props are JSON that must survive being saved.

The resolver context says what the index means: for labels the raster's own pixel value; for shapes the position in the loaded geometry, which is the loader's decision, so the ordering is supplied explicitly to build against. A buffer wins over featureState rather than merging — merging would reinstate the per-feature lookup this removes.

Schema symmetry (ddab672)

spatialLabelsSublayerSchema gains featureState, so the older SpatialLayerProps surface can express per-label filtering too. It omits strokeColorByFeatureId: a label's outline is derived from its fill in the shader. The now-unreachable 'classic' palette name goes with it.

Colouring correctness (bc2104e, a75b283)

Two defects in how a column was read, both from inferring what a column is from what its decoded values look like.

NaN stringified to "NaN" — non-empty and unparseable — so a single failed embedding made a whole UMAP1 column categorical, and categorical mode then gave every distinct float its own colour. The layer rendered as static. A non-finite number now normalises as missing, the way null already did.

More fundamentally, the loader already had to distinguish an AnnData categorical from a string-array from a typed array in order to decode, and threw the answer away. It now reports a TableColumnKind, and loadAssociatedTableFeatureRows carries it beside the values. 'auto' trusts it — which also fixes the mirror-image bug where integer cluster codes read as a continuum. Value sniffing remains only where no kind is on offer, and kinds are best-effort so a source that cannot report them still serves values.

Missing-value handling becomes configurable for the part that genuinely cannot be inferred: missingValues.treatAsMissing names the sentinel strings a given pipeline writes ('NA', 'unknown'), and missingValues.render chooses whether a feature with no value keeps the layer default, hides, or takes an explicit colour. null and NaN stay unconditionally missing. Sentinels resolve before the mode decision, the numeric extent and the category set, so one can never become a category or drag a ramp.

Review follow-ups (e07dcab, bc4f1df)

Findings from review, verified against the code and fixed.

Correctness, in e07dcab: loadAssociatedTableFeatureRows returned [] when kinds were unavailable, claiming "no column has a kind" rather than "we do not know", and breaking the positional alignment the field documents — it returns undefined now, and builds the array so its length matches extraColumns even if a source answers short. featureColorAt bounded reads on count, a caller's claim about its own buffer, so an over-stated one returned a tuple of undefineds typed as a colour; it is bounded by the bytes actually present. The shapes object and circle paths fell back to defaultFillColor for a feature the buffer did not cover while the binary path padded transparent, so one buffer rendered differently depending on which geometry representation the element loaded as — all three are transparent now. LabelsLayer disposed its LUT texture through an optional destroy?.(), so a wrong shape would silently leak a texture nothing reports; destroy is required and called unconditionally. LabelsResolver.fillColors was keyed by element alone, so two layers colouring one element by different columns evicted each other on every plan — a reload ping-pong that never settled; it is keyed by element and column.

Then bc4f1df replaces loadObsColumnKinds with a synchronous getObsColumnKinds. Opening a store already reads every node's attributes and array metadata into the tree — the same tree getObsColumnNames reads names from — so the encoding-type that distinguishes a categorical from a string array, and the dtype that distinguishes a float from a bool, are in memory before anyone asks for values. Deriving the kind during _loadColumn and caching it in a side map was work to recover something we already had. Being sync also lets a caller ask what a column is before deciding whether to load it, which is what a "colour by" UI wants in order to offer the right affordance up front — an async accessor could not give it that at any price. The classifier reads both zarr generations (v3 spells dtypes out, v2 uses numpy typestrings), with an integration assertion across all three fixture versions covering the assumption underneath it, so a zarrextra change that stopped populating the tree would fail rather than quietly degrade every column to "unknown". LabelsLayer also types its LUT texture as luma's Texture rather than a local structural type that could drift.

Docs (0fd5ab8)

The docs site described the shapes-only world this branch replaces. headless-viewer is where the API is written down, so its colour/filter section now covers both kinds, documents the scheme fields (categoricalPalette, numericRamp, missingValues) that had no coverage at all, and calls out the OkLab default change in an admonition next to the field that controls it. featureColorResolver is documented under the runtime-attachment list, because which list it is in is the point.

layer-prop-flow gains the labels LUT beside the shapes colour texture it mirrors, with the anti-patterns that actually bit during review. feature-table-associations had a checklist whose item 2 asked for exactly this work — marked done for the encode path, honest that row-resolution parity is still item 1. core/elements gains getObsColumnKinds() and why it is synchronous; layers/overview describes the shared encoding core; mdv-release-checklist had labels as "render when configured", which now understates them.

The site builds and every new cross-page anchor resolves. Two broken anchors remain, both pre-existing on main and in files untouched here.

Testing

Full workspace build, both lint gates (lint:biome, lint:react) clean, and the whole suite green: 365 core, 206 layers, 119 vis, 38 avivatorish, 7 react, plus 25 root integration tests. New coverage for the label colour LUT, the LUT prop flow, the vis projections, the buffer resolver and its identity contract, the column-kind classifier over both zarr generations, and the missing-value policy.

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features

  • Added column-based color mapping for shapes and labels, with categorical palettes and numeric ramps.
  • Added configurable handling for missing and sentinel values, including hiding or custom colors.
  • Added per-label filtering, fading, and feature-specific color overrides.
  • Added support for host-provided feature color buffers.
  • Added improved column type detection and an expanded, deterministic default color palette.

• Bug Fixes

  • Corrected handling of NaN and other non-finite numeric values during color assignment.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR adds shared feature-color encoding for shapes and labels, declared table column kinds, missing-value policies, label feature-state LUT rendering, and host-provided color buffers. It also threads these features through SpatialCanvasViewer, useLayerData, table loading, renderers, and tests.

Changes

Feature color data and encoding

Layer / File(s)	Summary
Column kind metadata and missing values packages/core/src/models/*, packages/core/src/tableAssociations.ts, packages/core/src/types.ts, packages/core/tests/*	Table loaders expose declared column kinds. Associated rows return aligned kind metadata. Color encoding trusts declared kinds and supports configurable missing sentinels.
Shared color encoding and shape integration packages/layers/src/featureColorEncoding.ts, packages/layers/src/shapeColorEncoding.ts, packages/layers/src/shapesLayer.ts, packages/layers/tests/*	Shared logic supports OkLab palettes, numeric ramps, missing-value rendering, and deterministic category assignment. Shape rendering accepts indexed host color buffers.
Label feature state and GPU lookup tables packages/core/src/spatialLayerProps.ts, packages/layers/src/labelColorEncoding.ts, packages/layers/src/LabelsLayer.ts, packages/layers/src/LabelsBitmaskTileLayer.ts, packages/layers/src/labelsBitmaskLayerShaders.ts, packages/layers/tests/*	Labels support column-based colors, per-feature overrides, hidden and faded IDs, and filtered opacity. LUTs drive shader colors and picking visibility.
SpatialCanvas label projection and loading packages/vis/src/SpatialCanvas/labelsProjection.ts, packages/vis/src/SpatialCanvas/resolvers/RasterResolvers.ts, packages/vis/src/SpatialCanvas/useLayerData.ts, packages/vis/src/SpatialCanvas/renderers/labelsRenderer.ts, packages/vis/tests/*	Label columns are loaded through resolver tasks. Projection caches build stable fill-color entries and LUTs, then pass them to label layers.
Host feature-color resolver packages/vis/src/SpatialCanvas/featureColorResolver.ts, packages/vis/src/SpatialCanvas/SpatialCanvasViewer.tsx, packages/vis/src/SpatialCanvas/renderers/shapesRenderer.ts, packages/vis/src/SpatialCanvas/useLayerData.ts, packages/vis/tests/featureColorResolver.spec.ts	SpatialCanvasViewer accepts a host resolver. Stable FeatureColorBuffer objects are forwarded to shapes and labels, with host colors taking precedence over feature state.

Estimated code review effort: 4 (Complex) | ~60 minutes

Sequence Diagram(s)

sequenceDiagram
  participant Host
  participant SpatialCanvasViewer
  participant useLayerData
  participant TableResolver
  participant FeatureColorEncoding
  participant LabelsLayer
  Host->>SpatialCanvasViewer: provide featureColorResolver and layer configuration
  SpatialCanvasViewer->>useLayerData: forward resolver and render options
  useLayerData->>TableResolver: load configured label column rows
  TableResolver->>useLayerData: return values and declared column kinds
  useLayerData->>FeatureColorEncoding: assign colors and build label LUT
  FeatureColorEncoding->>LabelsLayer: provide stable feature colors
  LabelsLayer->>LabelsLayer: upload LUT and render or discard labels

Loading

Possibly related PRs

• Taylor-CCB-Group/SpatialData.js#19: Introduced table and observation association APIs extended here with column-kind loading.
• Taylor-CCB-Group/SpatialData.js#22: Introduced label rendering infrastructure extended here with feature coloring and filtering.
• Taylor-CCB-Group/SpatialData.js#32: Introduced the viewer and layer-data flow extended here with host feature-color resolver support.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 40.82% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the primary change: adding label filtering and colouring with an API that mirrors shapes.

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/labels-filtering-coloring-3198b1

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 5

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/vis/src/SpatialCanvas/resolvers/RasterResolvers.ts (1)

332-364: 🩺 Stability & Availability | 🟠 Major | ⚡ Quick win

Key label fill-colour rows by layer config, not element key.

LabelsResolver stores fill-colour rows in fillColors keyed by ctx.elementKey, while two labels layers may reference the same element with different fillColorByColumn.columnName values. When these layers reconcile concurrently, each task schedules a column against the shared cache entry, then the last load updates that entry. The next pass invalidates the other layer’s cached column and re-requests it, so the same entries can keep ping-ponging.

getLabelFillColorEntry() then reads this shared labelsResolver.getFillColorRows(key), so the per-layer labelFillColorData cache cannot stabilize two layers on one element with different fill columns. Key fillColors by the layer/entry/config identity used by LabelsLayer, or store separate column rows per element.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/vis/src/SpatialCanvas/resolvers/RasterResolvers.ts` around lines 332
- 364, Update LabelsResolver’s fillColors storage and its accessors, including
getLabelFillColorEntry(), so fill-colour rows are isolated by layer/config
identity or by element plus column rather than only ctx.elementKey. Ensure
plan() reuses the correct cached rows for each fillColorByColumn.columnName,
allowing concurrent layers sharing an element to retain separate columns without
invalidating and reloading each other’s entries.

🧹 Nitpick comments (5)

packages/core/tests/tableElement.spec.ts (1)

66-67: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Do not replace the private source through any.

This assertion bypasses the TableElement source contract. Spy on the source class method, or add a typed test factory for the source dependency, so this test fails when the source API changes.

As per coding guidelines, avoid type assertions when a narrower API contract can express the same fact.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/core/tests/tableElement.spec.ts` around lines 66 - 67, Update the
test setup around loadObsColumnKinds to avoid assigning table.tableSource
through any. Spy on the actual source class method or use a typed test factory
for the source dependency, while preserving the mocked resolved column kinds and
ensuring the test remains coupled to the TableElement source contract.

Source: Coding guidelines

packages/core/tests/tableAssociations.spec.ts (1)

257-259: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Use a narrow association-loader dependency type.

loadAssociatedTableFeatureRows only needs the association lookup and table-loading methods. The double assertion hides differences between this mock and the production contract.

Define a narrow input interface for the methods this function consumes. Type this mock against that interface instead of asserting it is SpatialData.

As per coding guidelines, avoid type assertions when a narrower API contract can express the same fact.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/core/tests/tableAssociations.spec.ts` around lines 257 - 259, Define
a narrow input interface for the association-loader dependency used by
loadAssociatedTableFeatureRows, containing only its association lookup and
table-loading methods. Type the spatialData mock in tableAssociations.spec.ts
against that interface and remove the double assertion, while leaving unrelated
SpatialData contract requirements out of the mock.

Source: Coding guidelines

packages/layers/src/LabelsLayer.ts (1)

348-352: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Replace the assertion with a declaration type.

channelColors?.[0] ?? [255, 255, 255] widens the fallback literal to number[], which forces the as LabelRgbColor. An annotation on the declaration expresses the same fact and keeps the tuple check on the fallback.

♻️ Proposed change

-    const defaultColor = (channelColors?.[0] ?? [255, 255, 255]) as LabelRgbColor;
+    const defaultColor: LabelRgbColor = channelColors?.[0] ?? [255, 255, 255];

As per coding guidelines: "Avoid type assertions (as); use satisfies, as const, discriminated unions, and small helpers that return precise types."

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/layers/src/LabelsLayer.ts` around lines 348 - 352, Update
_resolveFeatureColorLut to replace the defaultColor `as LabelRgbColor` assertion
with an explicit declaration type, preserving the existing channelColors
fallback and tuple validation.

Source: Coding guidelines

packages/layers/tests/labelColorEncoding.spec.ts (1)

96-178: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Replace the repeated as Uint8Array assertions with a narrowing helper.

Each assertion hides the case where buildLabelColorLut returns undefined. A helper narrows once and fails with a clear message instead of reading properties of undefined.

♻️ Proposed helper

+function expectLut(lut: LabelColorLut | undefined): LabelColorLut {
+  expect(lut).toBeDefined();
+  if (!lut) throw new Error('expected a lookup table');
+  return lut;
+}

-    expect(lut?.count).toBe(4);
-    expect(rgbaAt(lut?.colors as Uint8Array, 3)).toEqual([10, 20, 30, 255]);
-    expect(rgbaAt(lut?.colors as Uint8Array, 1)).toEqual([255, 255, 255, 255]);
+    const table = expectLut(lut);
+    expect(table.count).toBe(4);
+    expect(rgbaAt(table.colors, 3)).toEqual([10, 20, 30, 255]);
+    expect(rgbaAt(table.colors, 1)).toEqual([255, 255, 255, 255]);

As per coding guidelines: "Avoid type assertions (as); use satisfies, as const, discriminated unions, and small helpers that return precise types."

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/layers/tests/labelColorEncoding.spec.ts` around lines 96 - 178,
Replace the repeated `as Uint8Array` assertions in the label colour lookup tests
with a small narrowing helper that accepts the result of `buildLabelColorLut`,
asserts it is defined with a clear failure message, and returns its colors as
`Uint8Array`. Update the affected `rgbaAt` calls to use this helper while
preserving the existing expectations.

Source: Coding guidelines

packages/vis/src/SpatialCanvas/types.ts (1)

186-191: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Extract the shared feature-state fields.

LabelsLayerConfig.featureState repeats ShapesLayerConfig.featureState minus strokeColorByFeatureId. A shared base type keeps both in step when a field is added, in the same way FillColorByColumn<TMode> now shares the colour configuration.

♻️ Proposed shared type

+/** Per-feature filtering and colouring, shared by shapes and labels. */
+export interface FeatureStateConfig {
+  fillColorByFeatureId?: Record<string, [number, number, number, number]>;
+  hiddenFeatureIds?: string[];
+  fadedFeatureIds?: string[];
+  filteredOpacityMultiplier?: number;
+}

-  featureState?: {
-    fillColorByFeatureId?: Record<string, [number, number, number, number]>;
-    hiddenFeatureIds?: string[];
-    fadedFeatureIds?: string[];
-    filteredOpacityMultiplier?: number;
-  };
+  featureState?: FeatureStateConfig;

ShapesLayerConfig then uses FeatureStateConfig & { strokeColorByFeatureId?: [number, number, number, number] extends never ? never : Record<string, [number, number, number, number]> }, or more simply an interface that extends FeatureStateConfig and adds strokeColorByFeatureId.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/vis/src/SpatialCanvas/types.ts` around lines 186 - 191, Extract the
common fields of LabelsLayerConfig.featureState and
ShapesLayerConfig.featureState into a shared FeatureStateConfig type, including
fillColorByFeatureId, hiddenFeatureIds, fadedFeatureIds, and
filteredOpacityMultiplier. Update both layer configurations to reuse this type,
with ShapesLayerConfig additionally defining strokeColorByFeatureId.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@packages/core/src/tableAssociations.ts`:
- Around line 187-195: Update the column-kind loading flow around
loadObsColumnKinds so a rejected or unavailable kind lookup preserves missing
metadata instead of defaulting to an empty array. Return undefined for
extraColumnKinds, or an undefined-filled array matching extraColumns.length,
while preserving positional alignment for successfully loaded kinds.

In `@packages/core/tests/spatialLayerProps.spec.ts`:
- Around line 117-129: Rename the test describing the labels stroke override to
state that the schema strips or removes the field rather than rejects it, and
revise the adjacent comment to describe successful parsing with the unsupported
property omitted. Keep the existing safeParse success and absence assertions
unchanged.

In `@packages/layers/src/featureColorEncoding.ts`:
- Around line 56-65: Update the validation guarding the color read in the
feature color lookup function to reject counts that exceed the available RGBA
rows, using Math.floor(buffer.colors.length / 4) as the effective row limit.
Ensure indexes are also rejected when they are outside that available-row limit,
so the returned FeatureRgbaColor tuple never contains undefined components.

In `@packages/layers/src/LabelsLayer.ts`:
- Line 374: Update the texture cleanup in the LabelsLayer methods around the
feature color texture and the additional release call sites to use the correct
texture destruction API consistently with the tile layer, rather than
optional-chaining potentially incorrect destroy/delete method names. Remove the
misleading optional method shape so cleanup invokes the established release
operation and cannot silently skip GPU resource disposal.

In `@packages/layers/src/shapesLayer.ts`:
- Around line 953-985: The featureColors fallback is inconsistent between
polygon and circle geometry paths. In packages/layers/src/shapesLayer.ts lines
953-985, update createPolygonDeckLayer’s fillAt to use TRANSPARENT_RGBA when
featureColorAt returns undefined with a buffer; apply the same fallback in
createCircleDeckLayer’s getFillColor at lines 1125-1136, while preserving
defaultFillColor behavior when no buffer is supplied.

---

Outside diff comments:
In `@packages/vis/src/SpatialCanvas/resolvers/RasterResolvers.ts`:
- Around line 332-364: Update LabelsResolver’s fillColors storage and its
accessors, including getLabelFillColorEntry(), so fill-colour rows are isolated
by layer/config identity or by element plus column rather than only
ctx.elementKey. Ensure plan() reuses the correct cached rows for each
fillColorByColumn.columnName, allowing concurrent layers sharing an element to
retain separate columns without invalidating and reloading each other’s entries.

---

Nitpick comments:
In `@packages/core/tests/tableAssociations.spec.ts`:
- Around line 257-259: Define a narrow input interface for the
association-loader dependency used by loadAssociatedTableFeatureRows, containing
only its association lookup and table-loading methods. Type the spatialData mock
in tableAssociations.spec.ts against that interface and remove the double
assertion, while leaving unrelated SpatialData contract requirements out of the
mock.

In `@packages/core/tests/tableElement.spec.ts`:
- Around line 66-67: Update the test setup around loadObsColumnKinds to avoid
assigning table.tableSource through any. Spy on the actual source class method
or use a typed test factory for the source dependency, while preserving the
mocked resolved column kinds and ensuring the test remains coupled to the
TableElement source contract.

In `@packages/layers/src/LabelsLayer.ts`:
- Around line 348-352: Update _resolveFeatureColorLut to replace the
defaultColor `as LabelRgbColor` assertion with an explicit declaration type,
preserving the existing channelColors fallback and tuple validation.

In `@packages/layers/tests/labelColorEncoding.spec.ts`:
- Around line 96-178: Replace the repeated `as Uint8Array` assertions in the
label colour lookup tests with a small narrowing helper that accepts the result
of `buildLabelColorLut`, asserts it is defined with a clear failure message, and
returns its colors as `Uint8Array`. Update the affected `rgbaAt` calls to use
this helper while preserving the existing expectations.

In `@packages/vis/src/SpatialCanvas/types.ts`:
- Around line 186-191: Extract the common fields of
LabelsLayerConfig.featureState and ShapesLayerConfig.featureState into a shared
FeatureStateConfig type, including fillColorByFeatureId, hiddenFeatureIds,
fadedFeatureIds, and filteredOpacityMultiplier. Update both layer configurations
to reuse this type, with ShapesLayerConfig additionally defining
strokeColorByFeatureId.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4efa4caa-19c5-4c85-94eb-4a2f96a769f3

📥 Commits

Reviewing files that changed from the base of the PR and between 895d8ad and 4b054c2.

📒 Files selected for processing (47)

• .changeset/column-kinds-and-missing-values.md
• .changeset/feature-color-buffer-resolver.md
• .changeset/feature-colour-schemes.md
• .changeset/labels-feature-filtering-and-colouring.md
• .changeset/labels-sublayer-feature-state.md
• .changeset/nan-is-a-missing-value.md
• packages/core/src/models/VAnnDataSource.ts
• packages/core/src/models/index.ts
• packages/core/src/spatialLayerProps.ts
• packages/core/src/tableAssociations.ts
• packages/core/src/types.ts
• packages/core/tests/spatialLayerProps.spec.ts
• packages/core/tests/tableAssociations.spec.ts
• packages/core/tests/tableElement.spec.ts
• packages/layers/src/LabelsBitmaskTileLayer.ts
• packages/layers/src/LabelsLayer.ts
• packages/layers/src/featureColorEncoding.ts
• packages/layers/src/index.ts
• packages/layers/src/labelColorEncoding.ts
• packages/layers/src/labelsBitmaskLayerShaders.ts
• packages/layers/src/shapeColorEncoding.ts
• packages/layers/src/shapesLayer.ts
• packages/layers/tests/featureColorEncoding.spec.ts
• packages/layers/tests/labelColorEncoding.spec.ts
• packages/layers/tests/labelsLayer.spec.ts
• packages/layers/tests/shapeColorEncoding.spec.ts
• packages/layers/tests/shapesLayer.spec.ts
• packages/vis/demo/src/App.tsx
• packages/vis/demo/src/HeadlessBlobsDemo.tsx
• packages/vis/demo/src/VivContrastExtension.ts
• packages/vis/demo/src/main.tsx
• packages/vis/src/SpatialCanvas/SpatialCanvasViewer.tsx
• packages/vis/src/SpatialCanvas/featureColorResolver.ts
• packages/vis/src/SpatialCanvas/index.tsx
• packages/vis/src/SpatialCanvas/labelsProjection.ts
• packages/vis/src/SpatialCanvas/public.ts
• packages/vis/src/SpatialCanvas/renderers/labelsRenderer.ts
• packages/vis/src/SpatialCanvas/renderers/shapesRenderer.ts
• packages/vis/src/SpatialCanvas/resolvers/RasterResolvers.ts
• packages/vis/src/SpatialCanvas/shapesProjection.ts
• packages/vis/src/SpatialCanvas/types.ts
• packages/vis/src/SpatialCanvas/useLayerData.ts
• packages/vis/src/index.ts
• packages/vis/tests/featureColorResolver.spec.ts
• packages/vis/tests/labelsProjection.spec.ts
• packages/vis/tests/rasterResolvers.spec.ts
• packages/vis/tests/useLayerData.spec.tsx