Cross-tabulation: test evidence

Every requirement of this module, the tests named for it, and what each test recorded the last time the evidence was rebuilt.

Requirements
39
Tests named for them
39 14 unit · 25 browser
Result
pass every test passing
Screenshots
10
Recorded
2026-10-09 12:12 UTC
Environment
linux 6.17.0-1022-azure · node v22.23.3 · playwright 1.61.1 · chromium 149.0.7827.55

The requirements are the rows of the module’s requirement matrix. A test is named for a requirement by starting its name with the requirement’s ID. The results are read from the committed evidence set; continuous integration reruns every test and fails when the committed set no longer matches.

Requirements and their tests

39 requirements · 39 tests

RequirementTests and evidence
CT-KIT-001pass

The chart is built from safety.viz's kit on the page and draws its bars with the kit's Chart.js, bundling neither; without safety.viz on the page it is refused with a message saying what is missing.

  • pass browser CT-KIT-001: the chart is built from safety.viz’s kit on the page and draws its bars with the kit’s Chart.js; without safety.viz it says what is missing (#44)
CT-CFG-001pass

Every setting has a default; row_by and col_by are each a column or a cut variable; percent is row, col or none; test is chisq, fisher or none; a setting that is not known, or a value it cannot take, is refused with a sentence naming it.

  • pass unit cross-tabulation: settings CT-CFG-001: every setting has a default; the rows and the columns are each a column or a cut variable; the percentages, the test and the statistic are checked (#44)
CT-DATA-001pass

The counts, the row and column totals and the grand total are desktop R's table() of the same participants, each in R's category, for every case; a value that is empty or only white space is missing, as R's recipe reads it.

  • pass unit cross-tabulation: the table CT-DATA-001: the counts, the row and column totals and the grand total are desktop R’s table() of the same participants, for every case (#44)
CT-DATA-002pass

Each cell's row and column percentages are its count of its row's or its column's total, as desktop R works them out.

  • pass unit cross-tabulation: the table CT-DATA-002: the row and the column percentages are each count of its row’s or its column’s total, as desktop R works them out (#44)
CT-DATA-003pass

A biomarker cut by the shared cut rule makes the rows or the columns, low to high, worked out on the participants the filters keep.

  • pass unit cross-tabulation: the table CT-DATA-003: a biomarker cut by the shared cut rule makes the rows or the columns, low to high, worked out on the participants the filters keep (#44)
CT-DATA-004pass

Each percentage is printed to one decimal as R's sprintf() prints it, a value exactly halfway to the even digit (6.25 as 6.2%), for every cell of every case and for R's own samples.

  • pass unit cross-tabulation: the table CT-DATA-004: each percentage is printed to one decimal as R’s sprintf() prints it, a value exactly halfway to the even digit (6.25 as 6.2%), for every cell of every case (#78)
CT-DRAW-001pass

Arm by response on the synthetic study: every count, the totals and each row's percentages on the page are desktop R's, and the stacked bars are the same percentages, drawn to 100.

  • pass browser CT-DRAW-001: arm by response: every count, the totals and each row’s percentages are desktop R’s, and the stacked bars are the same percentages (#44)
Screenshot captured by a test of CT-DRAW-001: arm by responseScreenshot captured by a test of CT-DRAW-001: as the gallery shows it
CT-DRAW-002pass

With column percentages each cell's percentage is of its column's total and the bars stack each column by the rows; with none there are no percentages.

  • pass browser CT-DRAW-002: column percentages are each count of its column’s total, and the bars then stack each column by the rows; with none there are no percentages (#44)
CT-DRAW-003pass

Response by CRP at Baseline cut at its median: the columns are the cut's groups, low to high, with desktop R's counts; the footnote states the cut and that every participant the filters keep with a value is cut, whether or not they have a category the other way; the Columns control offers the cut variables the settings name.

  • pass browser CT-DRAW-003: a biomarker cut by the shared cut rule makes the columns, low to high, with desktop R’s counts, and the footnote states the cut; the Columns control offers it (#44)
Screenshot captured by a test of CT-DRAW-003: response by crp median
CT-STAT-001pass

R is asked once per table, with one row per participant, the function, the arguments, the identity and the row count that desktop R's recipe writes; the categories are named in the order the table draws them, a cut's low to high and a column's by name with numbers as numbers and A to Z read as a to z (gsm.bio's order), the same in every browser language.

  • pass unit cross-tabulation: what R is asked, and what the line says CT-STAT-001: R is asked once per table, with the function, the arguments, the identity and the row count desktop R’s recipe writes, and one row per participant (#44)
CT-STAT-002pass

R's chi-square and Fisher results are printed with their method and counts, labelled exploratory and unadjusted, and Fisher's odds ratio with its interval, named by which row is over which and the odds of which column.

  • pass unit cross-tabulation: what R is asked, and what the line says CT-STAT-002: R’s chi-square and Fisher results are printed with their method and counts, labelled exploratory and unadjusted, and Fisher’s odds ratio with its interval (#44)
CT-STAT-003pass

The small-expected-count warning is R's: printed with the result as R worded it when R gives it, and not otherwise.

  • pass unit cross-tabulation: what R is asked, and what the line says CT-STAT-003: the small-expected warning is R’s, printed with the result when R gives it and not otherwise (#44)
CT-STAT-004pass

Handed to a connection as stored results, each of desktop R's answers is found by the chart's request for its table.

  • pass unit cross-tabulation: what R is asked, and what the line says CT-STAT-004: handed to a connection as stored results, each of R’s answers is found by the chart’s request for its table (#44)
CT-STAT-005pass

With R's answers stored in the page, the chi-square and the Fisher results print with their method and counts, Fisher's odds ratio with its interval, and what the chart asked is the key R wrote.

  • pass browser CT-STAT-005: with R’s answers stored in the page, the chi-square and Fisher results print with their method and counts, Fisher’s odds ratio with its interval, and the identity R wrote is the chart’s (#44)
Screenshot captured by a test of CT-STAT-005: fisher with odds ratio
CT-STAT-006pass

R's small-expected-count warning is printed with the result for a table with an expected count below 5 (response by CRP at Baseline cut at 8), and not for one without.

  • pass browser CT-STAT-006: R’s small-expected-count warning is printed with the result for a table with an expected count below 5, and not for one without (#44)
Screenshot captured by a test of CT-STAT-006: small expected counts
CT-STAT-007pass

With no R attached the line says statistics are unavailable, the table and the bars are still drawn, and nothing is fetched; with no test chosen R is asked nothing.

  • pass browser CT-STAT-007: with no R attached the line says statistics are unavailable, the table and the bars are still drawn, and nothing is fetched (#44)
CT-STAT-008pass

The test is of the participants the filters keep, as desktop R gives it for the women alone, and the line says the filter.

  • pass browser CT-STAT-008: the test is of the participants the filters keep, as desktop R gives it for the women alone, and the line says the filter (#44)
CT-STAT-009pass

Once the connection is replaced, a late answer from the old one changes neither the line nor what chart.statistics() reports.

  • pass browser CT-STAT-009: once the connection is replaced, a late answer from the old one changes neither the line nor what chart.statistics() reports (#44)
CT-STAT-010pass

A table R withholds, a category below its minimum size, prints R's reason with the table's variables named where R names the columns the chart handed it, and no number.

  • pass unit cross-tabulation: what R is asked, and what the line says CT-STAT-010: a table R withholds, a category below its minimum size, prints R’s reason with the table’s variables named where R names the columns the chart gave it, and no number (#44, #58)
CT-STAT-011pass

In the page, a withheld table's line reads R's reason with the variables named, and no p-value.

  • pass browser CT-STAT-011: a table R withholds prints R’s reason, with the table’s variables named in it, and no number (#44, #58)
CT-STAT-012pass

After a filter changes, the answer to the table no longer on screen is dropped when it arrives, and the line and chart.statistics() hold the answer for the table drawn.

  • pass browser CT-STAT-012: after a filter changes, the answer to the table no longer on screen is dropped when it arrives; the line shows the answer for the table drawn (#44, #58)
CT-STAT-013pass

Changing what the percentages are of redraws the table and the bars and asks R nothing: the line keeps R's answer for the table.

  • pass browser CT-STAT-013: changing what the percentages are of redraws the table and the bars and asks R nothing: the line keeps R’s answer (#44, #58)
CT-STAT-014pass

A column's categories are drawn in one order in every browser language, numbers in their names as numbers (2 mg before 10 mg), and R is handed them in that order, so Fisher's odds ratio is of the table drawn, on the side of 1 the drawn table is, and names its rows and columns.

  • pass unit cross-tabulation: what R is asked, and what the line says CT-STAT-014: a column’s categories are drawn in one order in every browser language, numbers in their names as numbers, and R is handed them in that order, so Fisher’s odds ratio is of the table drawn and says which row is over which (#78)
CT-STAT-015pass

In the page, with the arms named as doses, the table draws 2 mg before 10 mg, R is handed the rows in that order, and Fisher's odds ratio prints as R gave it for the table drawn, named 2 mg over 10 mg.

  • pass browser CT-STAT-015: with the arms named as doses, the table draws 2 mg before 10 mg, R is handed the rows in that order, and Fisher’s odds ratio is printed as R gave it for the table drawn, named 2 mg over 10 mg (#78)
CT-STAT-016pass

Fisher's infinite odds ratio, stored by desktop R as "Inf", prints from the stored answer exactly as live R's does; an estimate stored with no number beside a bound is said not to be shown, and why, and never vanishes.

  • pass unit cross-tabulation: what R is asked, and what the line says CT-STAT-016: Fisher’s infinite odds ratio, stored by R as "Inf", prints from the stored answer as live R’s does; an estimate R stored with no number but a bound says it is not shown, and never vanishes (#78)
CT-STAT-017pass

A table with a category below R's minimum group size prints Fisher's exact test as R computed it, the p-value with its method and counts and the odds ratio with its interval, while the chi-square test of the same table still prints R's reason; R's note that the minimum was not applied names the table's variable, not the column the chart handed R.

  • pass unit cross-tabulation: what R is asked, and what the line says CT-STAT-017: a table with a margin below R’s minimum group size prints Fisher’s exact test as R computed it, the p-value with its method and counts and the odds ratio with its interval, while the chi-square test of the same table still prints R’s reason; R’s note that the minimum was not applied names the table’s variable, not the column the chart handed R (#104)
CT-STAT-018pass

In the page, for a table with a column below R's minimum group size, the line prints Fisher's p-value, odds ratio and R's note with the table's variable named, and at 390px the page does not scroll sideways; a p-value R gives as 1 prints p > 0.999; by chi-square the same table prints R's reason and no number.

  • pass browser CT-STAT-018: for a table with a column below R’s minimum group size, the page prints Fisher’s exact test as R computed it, with R’s note naming the table’s variable, and at 390px does not scroll sideways; the chi-square test of the same table still prints R’s reason and no number (#104)
CT-LIST-001pass

Clicking a count lists that cell's participants, the ones desktop R puts in that cell, in the kit's listing, and a row of it opens safety.viz's participant profile of that participant.

  • pass browser CT-LIST-001: clicking a count lists that cell’s participants in the kit’s listing, and a row of it opens the participant’s profile (#44)
Screenshot captured by a test of CT-LIST-001: participants of a cell
CT-FAIL-001pass

When drawing fails the chart says so in its footnote, empties the listing and the rail, keeps its controls and leaves nothing half drawn, and draws again once it can.

  • pass browser CT-FAIL-001: when drawing fails the chart says so in its element and keeps its controls, leaving nothing half drawn, and draws again once it can (#44)
CT-DROP-001pass

With a participant table, participants it does not have and rows with no participant id are counted by reason; a participant table without the id column is refused with a sentence; filters that let nobody through say so; the id column and the table change together.

  • pass browser CT-DROP-001: with a participant table, participants it does not have and rows with no participant id are counted by reason; a participant table without the id column is refused with a sentence; filters that let nobody through say so; the id column and the table change together (#44)
CT-MOBILE-001pass

At 390 pixels the controls are folded away, the table fits or scrolls inside its own box, and the page does not scroll sideways.

  • pass browser CT-MOBILE-001: at 390px the controls are folded away, the table fits or scrolls inside its own box, and the page does not scroll sideways (#44)
Screenshot captured by a test of CT-MOBILE-001: the table on a phone
CT-SITE-001pass

The live demo holds at a 390-pixel-wide viewport with no horizontal scroll, with the controls open.

  • pass browser CT-SITE-001: the live demo holds at a 390px-wide viewport with no horizontal scroll, with the controls open (#44)
Screenshot captured by a test of CT-SITE-001: demo on a phone
CT-SITE-002pass

The gallery lists the chart with links to its live demo, its evidence page and its API reference; the demo opens on arm by response, draws the table where R cannot be reached and says so, and offers CRP at Baseline cut at its median.

  • pass browser CT-SITE-002: the gallery lists the chart with links to its live demo, its evidence page and its API reference, and the demo opens on arm by response (#44)
CT-SITE-003pass

The API reference has a table row for every setting the chart has, with the default the code has; the site build fails when one is missing.

  • pass unit cross-tabulation: the API reference CT-SITE-003: the reference names every setting the chart has, with its default, and a setting it leaves out is a problem (#44)
CT-SITE-004pass

On the demo page, whose stylesheet styles every table, heading cell and cell by its tag, the table of counts keeps the chart's own look: its face, size, weight, spacing, rules, ground and margins are the same, part for part, as on a page with no stylesheet, with no capitals and no letter-spacing, and the table is the size it is with the page's stylesheet switched off.

  • pass browser CT-SITE-004: on the demo page, whose stylesheet styles every table, heading and cell by its tag, the table of counts keeps the chart’s own look and size, the same as on a page with no stylesheet (#97)
CT-LIVE-001pass

Against R started in the browser on the demo: arm by response, by chi-square and by Fisher's exact test, every count, statistic and p-value equals desktop R's within 1 part in 10^8.

  • pass browser CT-LIVE-001: arm by response, by chi-square and by Fisher’s exact test, with R started in this browser: every count, statistic and p-value is desktop R’s (#44)
Screenshot captured by a test of CT-LIVE-001: r in the browser
CT-LIVE-002pass

Against R in the browser: response by CRP at Baseline cut at its median, by both tests, and cut at 8, where R warns of small expected counts, equal desktop R's, warning included.

  • pass browser CT-LIVE-002: response by CRP at Baseline cut at its median, by both tests, and cut at 8, where R warns of small expected counts, are desktop R’s (#44)
CT-LIVE-003pass

Against R in the browser: the women alone, by the filter, equals desktop R's.

  • pass browser CT-LIVE-003: the women alone, by the filter, is desktop R’s (#44)
CT-LIVE-004pass

Against R in the browser: response by CRP at Baseline cut at 9.5 and at 10, three and two participants above the cut, by Fisher's exact test equals desktop R's, and by chi-square the table cut at 10 is withheld with R's reason.

  • pass browser CT-LIVE-004: response by CRP at Baseline cut at 9.5 and at 10, which leave three and two participants above the cut: Fisher’s exact test is computed by R in this browser and is desktop R’s, and the chi-square test of the table cut at 10 is withheld with R’s reason (#104)
Screenshot captured by a test of CT-LIVE-004: fisher on a small margin

Visual evidence

Every screenshot below is a committed baseline: the same picture is what the browser tests compare the page with and what is shown here. Click one for the picture at its full size.

Tests run with every module

109 tests of the site, the evidence pipeline and the repository’s own checks

These are recorded in every module’s evidence set. A requirement ID one of them carries belongs to another module’s page.

  • pass browser CORE-SITE-001: the home page names the library and its version, and shows the version its bundle reports (#1)
  • pass browser CORE-SITE-002: the home page holds at a 390px-wide viewport with no horizontal scroll (#1)
  • pass browser CORE-SITE-003: the gallery is reached from the home page and lists the published charts, or says that none is published yet (#7)
  • pass browser CORE-SITE-004: the gallery lists each shared part, and its two links lead to that module’s evidence page and API reference (#7)
  • pass browser CORE-SITE-006: every module has an evidence page that lists each requirement of its matrix (#7)
  • pass browser CORE-SITE-006: the connection to R’s evidence page lists every RCON- and PVAL- requirement with the tests that prove it (#7)
  • pass browser CORE-SITE-007: a screenshot a test captured is shown under its requirement on the evidence page (#7)
  • pass browser CORE-SITE-009: every module has an API reference page that documents each name it exports (#7)
  • pass browser CORE-SITE-009: the connection to R’s API reference documents createConnection and formatStatistic (#7)
  • pass browser CORE-SITE-012: the gallery holds at a 390px-wide viewport with no horizontal scroll (#7)
  • pass browser CORE-SITE-013: each module’s evidence page holds at a 390px-wide viewport with no horizontal scroll (#7)
  • pass browser CORE-SITE-014: each module’s API reference holds at a 390px-wide viewport, with its tables restacked (#7)
  • pass browser CORE-SITE-015: the site serves the synthetic study, and the gallery gives its row counts and the commit it was copied from (#7)
  • pass browser CORE-SITE-019: every page is styled by safety.viz’s stylesheet as it was copied, published with its record, and then by the site’s own (#91)
  • pass browser CORE-SITE-019: the gallery’s cards, a module’s tabs, the fact panel, the evidence table and the reference’s sidebar are drawn by safety.viz’s rules (#91)
  • pass browser CORE-SITE-020: every page carries the header and the footer: the name and version, a Gallery list of every published chart, and links that all lead somewhere (#91)
  • pass browser CORE-SITE-020: the Gallery list opens from its button and from the keyboard, leads to a chart’s live demo, and the header marks the page a reader is on (#91)
  • pass browser CORE-SITE-021: the header holds at a 390px-wide viewport on every kind of page, and the Gallery list opens under it, on the screen (#91)
  • pass browser CORE-SITE-022: a row of the evidence table is laid out by its own words: the two columns are three fifths and two fifths of the table on every module’s page, and a row keeps its columns when another row is given a test with a long name (#85)
  • pass browser CORE-SITE-024: on the gallery and the home page every card says what its module is in the registry’s card text, at most two sentences and five lines at 1280px; with the first row of charts at the top of a 1280 by 800 window the second row’s pictures are in it; and a chart’s fuller text is at the head of its live demo (#96)
  • pass unit API reference page CORE-SITE-009: a link to another reference file goes to that module’s page, and the page names the file it was rendered from (#7)
  • pass unit API reference page CORE-SITE-009: the page is the reference file, rendered: its title, sections, tables and code (#7)
  • pass unit API reference page CORE-SITE-009: the sections are listed at the top, each linked to its place on the page (#7)
  • pass unit API reference: held to the code CORE-MAN-006: an export listed as data is documented as one, under one heading, and its fields are not held one by one (#32)
  • pass unit API reference: held to the code CORE-SITE-010: a constant whose value the reference does not give is a problem (#7)
  • pass unit API reference: held to the code CORE-SITE-010: a function the reference documents that the bundle does not export is a problem (#7)
  • pass unit API reference: held to the code CORE-SITE-010: a namespace in the surface stands for each of its members, and a constant carries its value (#7)
  • pass unit API reference: held to the code CORE-SITE-010: a parameter the source documents and the reference leaves out is a problem (#7)
  • pass unit API reference: held to the code CORE-SITE-010: a reference that documents every export, parameter and constant has no problems (#7)
  • pass unit API reference: held to the code CORE-SITE-010: an export no module claims, a surface the bundle lacks and an empty surface are each a problem (#7)
  • pass unit API reference: held to the code CORE-SITE-010: an export with no heading in the reference is a problem (#7)
  • pass unit API reference: held to the code CORE-SITE-010: the committed references document everything the committed bundle exports (#7)
  • pass unit API reference: held to the code CORE-SITE-010: the connection’s reference is held to the parameters its source documents (#7)
  • pass unit API reference: held to the code GC-SITE-004: a chart’s reference names every setting the chart has, and a setting it leaves out is a problem (#9)
  • pass unit evidence normalizer buildEvidenceSets splits records per module and duplicates shared scaffold records (#1)
  • pass unit evidence normalizer buildRun builds GitHub Actions run provenance from the environment (#1)
  • pass unit evidence normalizer compareEvidence flags status drift and test-set changes, ignoring screenshots (#1)
  • pass unit evidence normalizer compareEvidence ignores provenance so --check never drifts on generatedAt/environment/run (#1)
  • pass unit evidence normalizer CORE-SITE-011: a requirement row with no test named for it is reported (#7)
  • pass unit evidence normalizer CORE-SITE-011: a test that names a requirement in no matrix is reported with the test (#7)
  • pass unit evidence normalizer moduleForFile routes test files to modules by path (#1)
  • pass unit evidence normalizer normalizePlaywright walks nested suites into browser-suite records (#1)
  • pass unit evidence normalizer normalizeVitest maps assertion results to unit-suite records (#1)
  • pass unit evidence normalizer parseTestName extracts requirement IDs and issue refs (#1)
  • pass unit evidence normalizer parseTestName recognizes any requirement-ID prefix, not just SH (#1)
  • pass unit evidence normalizer provenance lives in dedicated top-level keys; the records array stays timestamp-free (#1)
  • pass unit evidence page CORE-SITE-006: a requirement with no test says so, and the summary counts it (#7)
  • pass unit evidence page CORE-SITE-006: each requirement shows the tests named for it, unit or browser, with the result each recorded (#7)
  • pass unit evidence page CORE-SITE-006: every requirement is listed in the matrix’s order with its text (#7)
  • pass unit evidence page CORE-SITE-006: tests that carry none of the module’s requirements are listed apart, as run with every module (#7)
  • pass unit evidence page CORE-SITE-006: with every requirement tested and passing the summary says every test is passing (#7)
  • pass unit evidence page CORE-SITE-007: a screenshot is shown under the requirement it was captured for, and only there (#7)
  • pass unit evidence page CORE-SITE-007: the build is told of a screenshot the evidence names that is not committed (#7)
  • pass unit evidence page CORE-SITE-008: results recorded on a developer’s machine say so, and absent provenance is not invented (#7)
  • pass unit evidence page CORE-SITE-008: the page says when and where the results were recorded and links the run (#7)
  • pass unit evidence page the page links the module’s requirement matrix and its committed evidence set (#7)
  • pass unit gallery CORE-SITE-003: a chart that is registered but not yet available is not listed as published (#7)
  • pass unit gallery CORE-SITE-003: a chart’s card shows its picture once that screenshot is committed, and no picture before (#9)
  • pass unit gallery CORE-SITE-003: a registered chart is listed under Charts with links to its evidence page and API reference (#7)
  • pass unit gallery CORE-SITE-003: with no chart registered the gallery says that no chart is published yet (#7)
  • pass unit gallery CORE-SITE-004: each shared part is listed with links to its evidence page and API reference (#7)
  • pass unit gallery CORE-SITE-004: the registry as committed lists the core and the connection to R as shared parts (#7)
  • pass unit gallery CORE-SITE-015: the gallery says what each table of the synthetic study holds, its rows, and the commit it was copied from (#7)
  • pass unit gallery CORE-SITE-016: a chart registered as experimental is published with an Experimental badge and the reason, on its gallery card, on the home page and on its live demo; the committed registry gives the stratified survival chart that status (#78)
  • pass unit gallery CORE-SITE-023: a card says what its module is in the registry’s card text, at most two sentences and 200 characters, on the gallery and on the home page, and not in the fuller text, which stays at the head of a chart’s live demo; the registry as committed holds every module to it, and the group comparison’s card names its tiles, its picture over time and its single visit (#96)
  • pass unit gallery CORE-SITE-023: the registry refuses an entry with no card text, with more than two sentences, or with more than 200 characters (#96)
  • pass unit gallery the home page heads its word about the charts for one chart and for several (#26)
  • pass unit gallery the home page links each module’s evidence page and API reference, and the gallery (#7)
  • pass unit gallery the home page says there are no charts yet only while none is published (#9)
  • pass unit markdown: blocks a relative link points at the repository, and a link to another reference file at its page (#7)
  • pass unit markdown: blocks CORE-SITE-009: a fenced block is code, escaped and left as written, and a # inside it is not a heading (#7)
  • pass unit markdown: blocks CORE-SITE-009: a table keeps each column heading on every cell, so it can restack on a narrow screen (#7)
  • pass unit markdown: blocks CORE-SITE-009: headings get the anchors GitHub gives them, repeated ones numbered (#7)
  • pass unit markdown: blocks CORE-SITE-009: paragraphs join their lines, and bullet and numbered lists keep theirs apart (#7)
  • pass unit markdown: inline keeps a code span inside a link label, and links a bare address in angle brackets (#7)
  • pass unit markdown: inline mdText strips the marks and keeps the words (#7)
  • pass unit markdown: inline reads nothing inside a code span as a link or as emphasis (#7)
  • pass unit markdown: inline renders code, links, bold and italic, and escapes everything else (#7)
  • pass unit module registry CORE-SITE-005: an entry that does not say whether it is a chart or a shared part is refused (#7)
  • pass unit module registry CORE-SITE-005: an entry without its matrix or its API reference is refused, as is a name registered twice (#7)
  • pass unit module registry CORE-SITE-005: the registry as committed is well formed (#7)
  • pass unit R check page RCON-PAGE-001: the page has a button that starts R, the stated tolerance and the versions desktop R used (#3)
  • pass unit R check page RCON-PAGE-002: the recorded megabytes, requests and seconds are shown for cold, reload and warm, with how they were measured (#3)
  • pass unit R check page RCON-PAGE-003: with no recorded measurement the page says so and prints no number in its place (#3)
  • pass unit repo hygiene no source or test file carries a machine-specific absolute path (#1)
  • pass unit requirements-lib: freshness guard flags added and removed requirement IDs (#1)
  • pass unit requirements-lib: freshness guard flags changed requirement text (#1)
  • pass unit requirements-lib: freshness guard reports fresh when the committed set matches a fresh extraction (#1)
  • pass unit requirements-lib: matrix parsing ignores the header, separator, and non-requirement content (#1)
  • pass unit requirements-lib: matrix parsing keeps an escaped pipe inside a requirement cell as a single row (#1)
  • pass unit requirements-lib: matrix parsing maps each requirement ID to its reviewed text (#1)
  • pass unit requirements-lib: requirement set wraps the parsed map with module + matrix provenance (#1)
  • pass unit requirements-lib: unregistered matrices passes when every matrix file is registered, ignoring the README and non-markdown files (#1)
  • pass unit requirements-lib: unregistered matrices reports a matrix file no module in site/config.json names (#1)
  • pass unit site pages CORE-SITE-001: the home page names the library and its version (#1)
  • pass unit site pages escapeHtml escapes the five HTML-significant characters (#1)
  • pass unit site pages renderShell fills title, description, version and root, and leaves no token behind (#1)
  • pass unit site pages summarizeModule counts requirement rows and passing test records (#1)
  • pass unit site pages the home page links to the R check page (#3)
  • pass unit site pages the home page lists each registered module with its counts and a link to its matrix (#1)
  • pass unit site validation: internal links flags internal links and asset references that do not resolve (#1)
  • pass unit site validation: internal links passes a site whose internal links all resolve, ignoring external and fragment links (#1)
  • pass unit the copied site styles CORE-SITE-018: a copied file that is changed, missing, or beside one the record does not name fails the check, and the second check holds each file to safety.viz at the recorded commit (#91)
  • pass unit the copied site styles CORE-SITE-018: safety.viz’s site stylesheet and page shell are in site/vendor/safety.viz-site/ with a record naming the repository, its dev branch, the commit and each file, and the copy matches its record (#91)
  • pass unit the page shell CORE-SITE-020: the header’s Gallery entry lists each published chart, leading to its live demo, and is a plain link while none is published (#91)
  • pass unit the page shell CORE-SITE-020: the shell’s header, navigation and footer are the copied shell’s, and its header script is the copied shell’s, character for character (#91)
  • pass unit the pages and the two stylesheets CORE-SITE-019: every class a page writes is styled by one of the two stylesheets, and the site’s own styles no class the pages do not write (#91)
  • pass unit the pages and the two stylesheets CORE-SITE-019: every page loads the copied stylesheet and then the site’s own, by paths that hold at any depth (#91)
  • pass unit the pages and the two stylesheets CORE-SITE-019: the site’s own stylesheet redefines none of safety.viz’s tokens, writes every colour and typeface as one of them, and names no element by its tag alone but the page’s body (#91, #112)

Checking this page

npm ci
npm run evidence:check   # rerun every test and compare with the committed evidence set
npm run evidence         # rebuild docs/evidence/cross-tab/evidence.json