Code Quality Trend Dashboard

Generated 2026-05-10T01:24:40Z · lookback 30 days · 14 ratchet runs sampled · latest gate: failing ·

Data availability note: Jest & Pytest failure/passed counts are sourced from ratchet-jest.json / ratchet-pytest.json artifacts on Core Tests (core-tests.yml) runs (real time-series). Coverage %, as any trend, bundle size, and type-error count have no automated time-series yet — see individual panels for details.
Jest failures (latest)
3076
baseline: 4242 · ↓ improved
Pytest failures (latest)
78
baseline: 177 · ↓ improved
'as any' floor
181
from .as-any-baseline.txt · ratchet enforced in CI
Jest passing (latest)
16089
baseline: 31168

Panel 1: Jest Coverage %

Source: Coverage workflow (coverage.yml). Currently manual-only — the on: trigger is workflow_dispatch only pending Codecov setup (#371).

Coverage workflow is manual-only (not automated).Enable auto-runs in coverage.yml to populate this panel.

To populate: enable auto-runs in .github/workflows/coverage.yml by uncommenting the pull_request + push triggers after wiring Codecov (#371).

Panel 2: Pytest Coverage %

Source: Coverage workflow (coverage.yml). Currently manual-only — same trigger gate as Jest coverage above.

Coverage workflow is manual-only (not automated).Enable auto-runs in coverage.yml to populate this panel.

To populate: same steps as Jest coverage panel above.

Panel 3: Jest Failed Tests (30d trend)

Source: ratchet-jest.json artifacts on Core Tests runs. Lower is better.

max: 3076latest: 3076

Baseline (from .ci/test-baseline.json): 4242 failed / 31168 passed · captured 2026-05-02T20:20:00Z

Panel 4: Pytest Failed Tests (30d trend)

Source: ratchet-pytest.json artifacts on Core Tests runs. Lower is better.

max: 78latest: 78

Baseline: 177 failed / 8930 passed · captured 2026-05-02T20:20:00Z

Panel 5: 'as any' Cast Count

TypeScript as any cast count in src/ + electron/. The ratchet gate prevents the count from rising above the floor; history is not yet stored per-run.

Trend not tracked: ratchet job emits pass/fail only.Current floor: 181 (from .as-any-baseline.txt)
MetricValue
Current floor (ratchet baseline)181
Historical peak (before #443 ratchet)3,418
Baseline when ratchet added181 (2026-05-04)

To add trend tracking: emit the count as a workflow summary line or artifact in check-as-any-ratchet.sh so future dashboard runs can parse it.

Panel 6: npm-audit High+Critical Count & Unit Tests Gate

Pass/fail dots from Core Tests runs (which contain the npm audit gate). Green = workflow passed, red = failed. Actual advisory counts are not emitted as artifacts today.

Each dot = one completed run on any branch. Source: Core Tests (core-tests.yml) workflow conclusions.

Data Gaps Summary

MetricCurrent StateHow to Enable
Jest coverage %Manual workflow onlyUncomment push/pull_request in coverage.yml + set CODECOV_TOKEN secret (#371)
Pytest coverage %Manual workflow onlySame as Jest coverage
as any trendCount not in artifactsAdd count output + artifact upload to check-as-any-ratchet.sh
Bundle size (main.js KB)Not trackedAdd build + wc -c step + artifact to unit-tests.yml
Type-error countNot trackedAdd tsc --noEmit step + error count artifact to unit-tests.yml
npm-audit advisory countPass/fail onlyAdd npm audit --json parse step to emit count as artifact