chore(deps, agent-service): update dependency @types/bun to v1.4.0

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
@types/bun (source)	1.3.14 → 1.4.0

---

Configuration

📅 Schedule: (in timezone Etc/UTC)

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

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

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Automated Reviewer Suggestions

Based on the git blame history of the changed files, we recommend the following reviewers:

• No candidates found from git blame history.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.37%. Comparing base (2113455) to head (43957c3).

Additional details and impacted files

@@            Coverage Diff            @@
##               main    #7894   +/-   ##
=========================================
  Coverage     92.37%   92.37%           
  Complexity     4588     4588           
=========================================
  Files          1173     1173           
  Lines         47347    47347           
  Branches       5306     5306           
=========================================
  Hits          43738    43738           
  Misses         2018     2018           
  Partials       1591     1591           

Flag	Coverage Δ		*Carryforward flag
access-control-service	81.00% <ø> (ø)		Carriedforward from 2113455
agent-service	98.62% <ø> (ø)
amber	88.98% <ø> (ø)		Carriedforward from 2113455
computing-unit-managing-service	73.67% <ø> (ø)		Carriedforward from 2113455
config-service	86.73% <ø> (ø)		Carriedforward from 2113455
file-service	82.59% <ø> (ø)		Carriedforward from 2113455
frontend	94.22% <ø> (ø)		Carriedforward from 2113455
notebook-migration-service	79.13% <ø> (ø)		Carriedforward from 2113455
pyamber	97.52% <ø> (ø)		Carriedforward from 2113455
workflow-compiling-service	77.19% <ø> (ø)		Carriedforward from 2113455

*This pull request uses carry forward flags. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[aglinxinyuan]

The build / agent-service (ubuntu-latest) failure was the LICENSE-binary drift check, not the bump itself — Renovate did update bun.lock correctly, so --frozen-lockfile passed and only the license manifest was stale:

DRIFT (direct) agent-service npm packages — claimed versions differ from bundled:
  ~ @types/bun: LICENSE-binary=1.3.14  bundled=1.4.0

(That step is if: matrix.os == 'ubuntu-latest', which is why the macOS leg was green.)

Pushed a fix commit:

• agent-service/LICENSE-binary — @types/bun 1.3.14 → 1.4.0 (direct, the blocking one)
• agent-service/LICENSE-binary — bun-types 1.3.14 → 1.4.0 (transitive, rides @types/bun; only informational under --ignore-transitive-version, but syncing it keeps the nightly exact-match check on main green)

Both packages are still MIT, so this is a version sync only — no section move.

Verified locally on bun 1.3.3 (matching the CI matrix): bun install --production --frozen-lockfile, license check in both PR (--ignore-transitive-version) and strict mode → OK: 58 agent-service npm packages match LICENSE-binary, then bun install --frozen-lockfile, format:check, typecheck, and bun test — 299 pass, 0 fail.

The commit sits on top of Renovate's, so it'll stop force-pushing over this branch.

[forking-renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.