# Changelog

## Score

- CAI 58 → 60 (+1.4)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.3) — scores are not directly comparable.

## Lenses

- Code Health 54 → 54 (+0.0)
- Architecture 90 → 90 (-0.1)
- Maturity 69 → 71 (+1.5)
- Readiness 69 → 69 (-0.0)
- Security 51 → 53 (+2.8)
- Performance 100 → 100 (+0.0)

## Resolved (18)

- Documentation: no installation or build instructions (docs/configuration/index.md)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High secret: WD-SECRET-0005 (package-lock.json)
- High vulnerability: [GHSA redacted] (pnpm-lock.yaml)
- Inconsistent parameter ordering and naming for date manipulation operations. `add` takes (timestamp, amount, unit), while `diff` takes (a, b, unit). `startOf` and `endOf` take (timestamp, unit). The `unit` parameter is the last argument in `add` and `diff`, but the second argument in `startOf` and `endOf`. This inconsistency in parameter position for the `unit` argument across similar date manipulation methods can lead to errors.
- Medium CVE: [GHSA redacted] (pnpm-lock.yaml)
- Medium CVE: [GHSA redacted] (pnpm-lock.yaml)
- Medium CVE: [GHSA redacted] (pnpm-lock.yaml)
- Medium CVE: [GHSA redacted] (pnpm-lock.yaml)
- Rotate the exposed credentials — git history can't be un-committed
- TimeSeriesScale exposes getDecimalForValue, but TimeScale (its likely parent or related type) also exposes it. While TimeSeriesScale is a specialized scale, exposing this specific internal calculation method at the public API level for a subclass while the parent also has it suggests potential redundancy or confusion about which scale type should be used for decimal calculations. However, given TimeSeriesScale is a distinct scale type, this is likely intentional specialization. A stronger inconsistency is found below.

## New (26)

- Documentation: no build, run or usage example (README.md)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High vulnerability: [GHSA redacted] (pnpm-lock.yaml)
- Low CVE: [GHSA redacted] (pnpm-lock.yaml)
- Medium CVE: [GHSA redacted] (pnpm-lock.yaml)
- Medium CVE: [GHSA redacted] (pnpm-lock.yaml)
- Medium CVE: [GHSA redacted] (pnpm-lock.yaml)
- doc comments repeat the names (src/controllers/controller.bar.js)
- redundant comment (src/core/core.layouts.js)
- redundant comment (src/core/core.layouts.js)
- redundant comment (src/helpers/helpers.canvas.ts)
- redundant comment (src/helpers/helpers.canvas.ts)
- redundant comment (src/helpers/helpers.canvas.ts)
- …and 6 more
