varvis-download

Use when asked to find, scan for, audit, or review varvis-download for bugs, defects, or regressions, when triaging a suspected defect or an external reviewer's finding, or before reporting any code-scan finding as confirmed.

Use when a js/ or tests/ file in varvis-download is near or over the 600-line architecture budget, when `npm run architecture:check` warns or blocks, when a task touches a file pinned in KNOWN_OVERSIZED_FILES, or when extracting a concern into a new CommonJS module or test file.

Use when writing or updating a Jest test in varvis-download, mocking HTTP/undici, winston loggers, the filesystem, child_process/spawn, timers or setTimeout backoff, readline prompts, or analysis objects, deciding where a new test file goes, or when a focused `--coverage` run fails the global coverage thresholds.

Use when adding or editing an exported function, class, or method in js/**/*.cjs or root *.cjs in varvis-download, adding a shared domain type, typing a dependency that ships no types, or when `npm run type-check` (tsc --noEmit, strict checkJs) or the eslint-plugin-jsdoc rules fail.