chore(deps): lock file maintenance

[renovate]

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 UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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 was generated by Mend Renovate. View the repository job log.

[indent-zero]

PR Summary

Second merge of main into the PR branch (ee025774). The previously flagged Cargo.lock regression is now moot: main itself moved petname-macros 3.1.0 → 3.0.0 in PR #1955 (bc434b3b), so this merge reconciles both sides at 3.0.0 and the PR's diff vs main is back to bun.lock + flake.lock only. The PR has since been merged to main as c7e0cb99.

• flake.lock: forward-bumps across devenv, foundry, Handy, home-manager, llm-agents.nix, neovim-nightly-overlay, neovim-src, nix-darwin, nixos-hardware, nixpkgs-nightly, nixpkgs-unstable, NUR, treefmt-nix, xremap; upstream-driven cleanup removes noctalia-qs / systems_4 and renumbers root treefmt-nix_5 → treefmt-nix_4.
• bun.lock: refreshed resolutions against the new main; integrity hashes refreshed, no package.json ranges change.
• Cargo.lock: no longer differs from main — earlier petname-macros@3.0.0 vs 3.1.0 divergence is resolved because main itself is now at 3.0.0.

Issues

All clear! No issues remaining. 🎉

1 issue already resolved

• The Merge remote-tracking branch 'origin/main' into HEAD commit silently downgrades petname-macros 3.1.0 → 3.0.0 in Cargo.lock; main bumped it via chore(deps): lock file maintenance #1960 and this PR branch never touched Cargo.lock, so a clean 3-way merge should have kept 3.1.0 — re-resolve by checking out main's Cargo.lock verbatim before merging. (fixed by commit ee02577)

CI Checks

e2e-check failed because the upstream e2e-run (Ubuntu) job ran out of disk space on the GitHub Actions runner while building cursor-3.2.21 via Nix (error (ignored): write of 10891 bytes: No space left on device → patchelf exit 1 → cascade of dependent derivation failures up to home-manager-generation and make: *** [Makefile:453: nix-build] Error 1). This is a runner capacity issue unrelated to the lock-file changes in this PR; a re-run (or a runner with more free space / additional cleanup of preinstalled tooling) should resolve it.

e2e-check

• e2e-run (Ubuntu, ubuntu-latest) failed with No space left on device while Nix was building cursor-3.2.21 (patchelf step), which then cascaded into failures of code-syncer.service, home-manager-files, and home-manager-generation. The failure originates from the GitHub Actions runner's disk filling up during the Nix build, not from the lock-file changes in this PR.

[cubic-dev-ai]

No issues found across 2 files