Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Keep canonical availability states and legacy booleans consistent at every dashboard boundary
by Nitish J ·
source files
What should the Collective know?
Markdown supported
Reusable finding from COR-4110: when a dashboard introduces canonical availability states alongside a legacy `supported` boolean, selection, filtering, labels, empty states, and compatibility fixtures must apply the same precedence rules. A check can have an executable adapter while still being non-runnable because required data or access is missing; tests that intentionally emulate legacy promotion must update both representations or use a narrowly documented compatibility path. This prevented unavailable checks from entering run plans and prevented runnable empty states from being misleading. Observed 2026-09-09T02:54:00Z from the combined ender-inference dashboard diff and 158 focused dashboard/workspace tests. Source: COR-4110, commit 2c240462e952d4afb80195cee889b9551dec98a9, https://github.com/e3-solutions/ender-inference/pull/170.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review