Biomarker charts objective · safety.viz v1.9.0 · 3 October 2026

The safety.viz kit: what changed, and what did not

safety.viz's bundle gained one thing: a frozen list, called kit, of 36 parts its own thirteen charts are already built from. It exists so a second chart library on the same page can build its charts from the same parts instead of copying them. Nothing in safety.viz moved, was renamed or behaves differently.

What was added1 export

Parts in it36

Charts changed0 of 13

Screenshots changed0

On dev3 Oct, 00:56 UTC

Ships inv1.9.0

Decisions for you

From v1.9.0 these 36 parts are public surface: changing how any of them is called becomes a breaking change for bio.viz. That is the one real cost, and it is yours to accept at the v1.9.0 release candidate.
It is milestoned v1.9.0, not the v1.10.0 the task first said, because it merged to dev after v1.8.0 shipped and so rides the next release. Say so if you want it held out.
One part, reconcileFilters, joined after the task was written, because the v1.8.0 review made it the step every chart now calls to settle its filters. Without it bio.viz's filters would behave differently from safety.viz's.

Why it exists

bio.viz, the biomarker chart library, runs beside safety.viz on the same page. The design decision you agreed on 2 October was that it borrows safety.viz's shared parts rather than copying them.
Before the kit, those parts lived inside safety.viz's source as internal functions. A second library could not reach them from the published bundle at all.
The kit is the reach: one name on the bundle, SafetyViz.kit, pointing at exactly the functions safety.viz's charts already call. It is a re-export, not new code and not a refactor.
The payoff: bio.viz's charts have the same sidebar, filters, record listing and participant profile as safety.viz's, draw with the same copy of Chart.js, and cannot drift away from them, because they are literally the same functions.

How the two libraries meet on a page

One web page

safety.viz bundle

The thirteen safety charts, unchanged
Its own copy of Chart.js

SafetyViz.kit: 36 parts, the same functions the thirteen charts use, read-only

bio.viz bundle

Four biomarker charts (group comparison, scatter, correlation matrix, and the screen in progress)
The variable-and-frame core, and the connection to R
No Chart.js and nothing of safety.viz inside it

bio.viz's charts look for SafetyViz.kit on the page and build their sidebar, filters, listing, profile rail and canvases from it

What changed in safety.viz, and what did not

Changed

A new file, src/kit.js, that gathers the 36 parts and freezes the list.
One export line in src/main.js, so the bundle carries kit. The committed bundle differs by that object and nothing else.
A kit page in the API reference, listing every part, where it comes from and how to call it.
A requirement matrix for the kit, tests named to it, and a line in the v1.9.0 release notes saying the parts are public surface from now on.

Not changed

No function moved, was renamed or got a new signature.
No chart, settings schema or default changed; all thirteen charts behave as they did.
No screenshot in any chart's evidence differs, and every existing evidence record is identical; only kit records were added.
Nothing for a safety.viz user to do or notice.

The 36 parts

Grouped by where they live in safety.viz. Each is the very function object safety.viz's charts use; a test fails if any is not.

Group	What it is for	Parts
Drawing engine	Chart.js 4.5.1, the copy safety.viz already carries, so a page loads one. Bar, line and scatter are registered; anything else is a plugin on it.	`Chart`
The page frame	The sidebar of controls, the chart area, the view switcher and the shared styles every chart sits in.	`renderShell`, `controlBuilders`, `renderViewSelector`, `applyShellStyles`, `createElement`, `option`, `multiSelect`
Filters	The filter controls and the rules for what a filter lets through, including the reconciling step every chart now calls.	`reconcileFilters`, `renderFilterControl`, `normalizeFilterSpec`, `initFilterState`, `filterMatches`, `ALL_VALUE`
Axis limits	The minimum and maximum inputs for an axis.	`syncAxisLimits`, `seedLimitInput`, `applyLimitEdit`, `clearAxisLimits`, `formatLimit`, `limitDigits`
Record listing	The table of participants under a chart: search, sort, pages and a CSV download.	`renderListing`, `searchRows`, `sortRows`, `paginate`, `buildCsv`, `exportCsv`
Participant profile	The side panel that opens one participant's results when a row or point is clicked.	`mountProfileRail`, `unmountProfileRail`, `syncProfileRail`, `resetProfileRail`, `buildProfileRows`
Box drawing	How a box and its whiskers are drawn.	`drawBoxWhisker`, `boxWhiskerPlugin`
Measure list	Which measures a chart offers, and in what order.	`resolveMeasureList`, `presentMeasures`
Survival curve	The Kaplan–Meier estimate behind safety.viz's time-to-event curve, for bio.viz's stratified survival chart to draw from rather than reimplement.	`kmEstimate`

Left out on purpose: the two status banners, prototypeBanner and experimentalBanner, because their wording is about safety.viz's own release status.

How it was proven

Unit tests named KIT-API hold each of the 36 parts identical to the function its own module exports, hold the list to exactly those 36, and fail if a module gains an export that is neither listed nor deliberately left out.
Browser tests named KIT-USE drive a test page that loads only the committed bundle and builds a working page from the kit alone: a sidebar, a filter that narrows a bar chart drawn with kit.Chart, a click that fills the record listing, and a listing row that opens the participant rail. A test fails if that page reaches for any of safety.viz's charts directly.
All 2,124 unit tests and 350 browser tests passed; CI passed on the final commit; no screenshot changed. You ran the evidence workflow on the branch so the evidence records name the Linux runner, and that run changed provenance only.
The orchestrating session re-ran every check itself in a fresh copy before each step, and read the bundle's exported names directly: dev's names plus kit, none removed.

Two things worth knowing

Rough edges, not blockers

The listing's CSV download, exportCsv, always names its file after the safety histogram. bio.viz builds its own download from buildCsv instead, so its files are named for its charts. Fixing exportCsv itself would now be a kit change.
Separately from the kit, the v1.8.0 review changed what a filter's start setting means: it now only sets what a filter opens on, and only all: false removes the All option. bio.viz takes that in when it re-copies safety.viz's bundle from dev.

How it got here

2 October, morningYou agreed that bio.viz borrows safety.viz's parts rather than copying them, and approved the task.
2 October, afternoonBuilt and verified as a draft, then held unmerged while the v1.8.0 release candidate was open, at your decision ("Build now, merge after v1.8.0 is cut"). bio.viz's first chart was built against the draft meanwhile ("Start now against the draft").
2 October, 21:41 UTCv1.8.0 shipped. The kit was brought up to dev; reconcileFilters joined; the milestone moved to v1.9.0.
3 October, 00:45 UTCYou ran the evidence workflow on the branch.
3 October, 00:56 UTCMerged to dev. It reaches main with v1.9.0, through your review of that release candidate.

Who uses it, and what comes next

bio.viz's three charts on its dev site already run on it, from a copy of the draft. They now re-copy safety.viz's bundle from dev (bio.viz task 37).
gsm.bio's three R widgets carry the same copy of safety.viz's bundle, as a recorded stand-in until gsm.safety ships one with the kit.
The demo app requirement you approved yesterday puts the biomarker charts in safety.viz's demo app; the app hands them the kit from its own bundle.