[1.134.1] — 2026-08-05
Validation-hardening — fixes surfaced by a full-project audit (all locales + code).
Fixed
successfactorsno longer discards scraped jobs on a mid-scan failure (regression in the v1.134.0 dead-board-throw port) — its RMK pagination loop had notry/catch, so a failure on page 2+ (after page 1 succeeded) threw and dropped everything already collected. Worse, if that mid-pagination failure was a 404 (plausible on an out-of-rangestartrowbehind a WAF),en-scanner's permanent-failure check would quarantine a live tenant as dead for days. Now mirrorsphenom/radancy: a page-0 failure (nothing fetched) still throws (dead board), but a later-page failure keeps the partials (+1regression test).#/scanfilter chips are now keyboard-operable (WCAG 2.1.1) — the stack/level/dynamic-keyword facet chips (and the "clear" chip) were<span onClick>with notabindex/role, so keyboard and screen-reader users couldn't reach or toggle them (the.chip:focus-visibleCSS was dead). They now carryrole="button",tabindex="0",aria-pressed(toggles), and Enter/Space activation.- Three hardcoded English strings are now localized — the
#/scantrust-badge tooltip ("Trust …"), the#/scanrelocation column header ("Reloc"), and the#/dashboardscore header ("Score") were bare literals the i18n parity gate couldn't see (they were never keys), so they stayed English in all 16 non-English locales. Nowscan.trustTip+scan.col.reloc(2 new keys ×17) and a reuse of the existingtrack.col.score. A source-static guard locks them so the gap can't silently return.
Security
fast-uri3.1.4 → 3.1.5 in thesite/build lockfile (Dependabot GHSA — high: host confusion via a backslash authority introducer). Transitive dev-only dependency of the cvstart.org Astro toolchain;npm auditnow reports 0 vulnerabilities and the Astro build is unchanged (86 pages, green). Does not touch the SPA or server (express+js-yamlonly).