Repository navigation
test: measure frontend coverage with an honest source denominator (refs #2962) - #3025
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Step9.5 stale-base triage: the target advanced from integrated f6e5d08 to2c18a98deff4d0edb53eff5e6ef78456397c9512 (#3026/#3024,e094917c plus merge). Current PR head remains bd7384f, identical to the local checkout/validated coverage source. Independent Grinch review classified this delta UNRELATED:
No branch update or extra CI run is required for this unrelated delta under the landing policy. Existing successful checks and coverage remain evidence for the unchanged PR head. The red test-debt check and its one isolated same-head rerun remain separate; this triage does not authorize merging a failed check. Evidence: room-shared artifacts and messaging/20261015-194712-room14-ac-dev-rust-grinch-v4-to-room14-ac-tech-lead-v4-2962-main-delta-triage-verdict.md. CODE PASS and Verification10 PASS with the documented1049-range/53-file remap limitation remain valid. |
|
|
Final CI verification after the native completion notice: all triggered Actions runs and applicable external checks succeeded on exact head Skipped platform/frontend jobs follow the workflow's existing light-tier condition: Fresh explicit main fetch still resolves |



Frontend tests previously had no auditable, opt-in V8 coverage report that included eligible source files outside the test import graph. Pin
@vitest/coverage-v8to the runner version and configure explicit TypeScript/TSX coverage with HTML, JSON and summary output, including unexecuted runtime sources. Run it withnpm test -- --coverage --maxWorkers=1; use a freshCOVERAGE_OUTPUTdirectory for each measurement.Source-boundary tests now read the selected source files directly, preserving their selection and assertions while avoiding raw-module coverage collisions. Stale project discovery rejects invalidated requests before reading the transport. Loop automation regressions verify fresh task snapshots, retain failure-path snapshot identity and reuse local interactions without weakening assertions or adding duplication.
Pre-merge checks used clean commit
9f819d3f1e90ff19cf924ca1b35ab83e9a5e78a5. Complete coverage and applicable independent proof were repeated successfully on mergedmaincommita1a694b5962f30f265c1a07b5b91eace18fb683a; the final metrics below match both runs:main.tsxis the only eligible source outside the test import closure. Its nonempty executable mappings remain at zero hits.origin/mainmerge base: 270 files, 117 existing clones, zero new clones.Known reporting limit: 1,049 inverted range ends across 53 files make some HTML highlighting extents imprecise. Independent source/map equality and reporter review validate the counters, denominator and four metrics; exhaustive token-level mapping fidelity is not claimed. This measures the existing Node/jsdom suite, not browser/Tauri behavior.
All applicable remote checks passed on the exact reviewed head, including the previously failing duplication gate. Official full-tier jobs were skipped by the workflow's existing
full=falsecondition. Protected landing completed on 2026-10-15T22:15:57Z asa1a694b5962f30f265c1a07b5b91eace18fb683a. The unchanged incoming main delta was independently classified unrelated in #3025 (comment).Refs #2962. Fresh merged-main measurement and final UI/Grinch proof completed; delivery evidence and final metrics are recorded in the issue. No release, version bump, final application build or installation is included.