wa-reporting-frontend

Upgrade dependencies and maintain CVE-focused resolution hygiene in a Yarn 4 Node.js project. Use when asked to upgrade one dependency, multiple dependencies, or all dependencies to latest versions, when asked to remediate CVEs from `yarn-audit-known-issues` produced by `yarn npm audit --recursive --environment production --json`, or when asked to check and remove unnecessary `package.json` `resolutions` after upstream dependency upgrades. Follow this precedence for CVE remediation: (1) upgrade the vulnerable package if it is in package.json `dependencies`, (2) otherwise upgrade a direct parent dependency that pulls in the vulnerable transitive package, (3) otherwise use a package-level CVE resolution for the vulnerable package, falling back to descriptor-level resolution only when a broad override is incompatible.

Start, restart, run up, or smoke-check the WA Reporting Frontend app locally with the preferred Flyway-backed seeded Docker Postgres database and auth disabled. Use when asked to run up the app, start the app locally, get the app running with local data, restart local app, seed local database, rebuild local DB data, change local seed size, set LOCAL_DB_SEED_RECORD_COUNT or LOCAL_DB_SEED_RANDOM_SEED, disable auth for local development, or verify local analytics routes.