chore(deps): lock file maintenance

[its-miso]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: (in timezone America/Edmonton)

• Branch creation
  • "before 5am on monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: MiniMax-M2.7@https://litellm.jory.dev/v1 (anthropic) — escalated (fast_low_confidence)

Review Summary

PR PR 612: `chore(deps): lock file maintenance

Recommendation: Approve — This is a low-risk lock file refresh by Renovate Bot.

---

Changes Overview

Only package-lock.json was modified (32 additions, 19 deletions). The following transitive dependencies were updated:

Package	Old Version	New Version	Type
@types/node	25.9.3	26.0.0	Type definitions
body-parser	2.2.2	2.3.0	Runtime middleware
semver	7.8.4	7.8.5	Runtime utility
undici-types	7.24.6	8.3.0	Type definitions
content-type	(nested)	2.0.0	Nested under body-parser

---

Required Checks — Explicitly Addressed

✅ Check for breaking API changes in updated dependencies

Analyzed all four updated packages:

• semver 7.8.4 → 7.8.5: Patch release. No breaking changes.
• undici-types 7.24.6 → 8.3.0: Tracks Node.js built-in type definitions. No runtime impact — this is a TypeScript/type-only package.
• @types/node 25.9.3 → 26.0.0: Type definitions only. The major version bump reflects Node.js 26's updated type surface, but there are no runtime breaking changes — these are compile-time types.
• body-parser 2.2.2 → 2.3.0: Minor version bump within the 2.x series. The diff shows only dependency version bumps (content-type, http-errors, iconv-lite, qs, raw-body, type-is) — no API surface changes to body-parser itself.

Conclusion: No breaking API changes detected. All updates are either type-only definitions or patch/minor bumps with backward-compatible dependency refreshes.

✅ Run full test suite after upgrade

Verified via CI Status: The test suite completed successfully (status: success). CI ran:

• test — passed
• lint — passed
• npm-audit — passed
• build (linux/arm64 and linux/amd64) — passed
• dockerfile-lint — passed
• merge — passed

---

Standards Compliance

• ✅ Follows repository conventions for dependency maintenance (no package.json changes — lock file only)
• ✅ Lock file refresh is routine maintenance
• ✅ No files outside package-lock.json changed
• ✅ CI gates passed before merge

---

Linked Issue Fit

No linked issues. This is a standalone lock file maintenance PR.

---

Evidence Provider Findings

No evidence providers configured for this PR.

---

Tool Harness Findings

No tool calls were made; review conducted from corpus directly.

---

Unknowns / Needs Verification

None. All required checks are satisfied, CI passed, and no breaking API changes identified.