MAIN TASK:

upgrade all packages in package.json where there are pending PATCH upgrades to the latest version

REPO SPECIFIC INSTRUCTIONS:

ignore the package.json description field
how to find latest green build:
how to smoke test: 

launch devserver and navigate to page /blah
run this test command "npm run test --grep smoketest"


how to request code review:

HOW TO UPGRADE:

use one subagent per package and have them work in separate worktrees (pick an appropriate model depending on how complex you think the upgrade will be)

each subagent should start their worktree based on the latest GREEN build

each subagent must then run "p4-vitest-smoketest" with zero failures, and then launch the devserver on their own random port (see worktree setup script/instructions) and they must be able to load the /portal/cyber-trends/global page (using devtrack as backend and logging in as user=devel pass=devel)

create one PR per package

before the subagent starts the upgrade of its package, it should review commits from git history where that same package was upgraded (in some rare cases this might yield info about what other changes are necessary when this package is upgraded, but in most cases this will not yield any additional info and that's ok)

once PR is created, use the repo specific method to request code review (using an appropriate-given-the-complexity-of-the-particular-upgrade model) for it and fix any issues that code review or CI finds

if it's a major version bump, do web research on what the breaking changes are and check if there is an upgrade guide

if the PR is green and all code review comments have been fixed, then merge the PR (note that the recfut/portal main CI must be green when you merge, otherwise just wait a bit until the latest build is green)

keep me posted on progress at regular intervals

upgrade "families of packages"

rely heavily on CI but be proactive about test locally in parallel