fix(security): update js-yaml to address CVE-2026-59870

[arran4]

Updated the indirect dependency js-yaml in package-lock.json via npm audit fix to resolve quadratic CPU consumption vulnerability in !!omap resolution (CVE-2026-59870). The update correctly bumps versions 3.15.0 to 3.15.1 and 4.3.0 to 4.3.1.

---

PR created automatically by Jules for task 17087616052964764011 started by @arran4

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[arran4]

@jules should we upgrade the package json dependencies and ensure the code base works?

[google-labs-jules]

@jules should we upgrade the package json dependencies and ensure the code base works?

Hi! js-yaml is not a direct dependency in package.json, it is an indirect dependency (brought in by eslint and ts-jest). Running npm audit fix updated the versions in package-lock.json from 4.3.0 to 4.3.1 and 3.15.0 to 3.15.1, which contains the fix for the CVE. I have run npm test and npm run build and both passed, so the code base works fine with the updated lockfile.