chore(deps): bump nixpkgs from 15f4ee4 to 549bd84

[dependabot]

Bumps nixpkgs from 15f4ee4 to 549bd84.

Commits

• 549bd84 cwal: 0.8.4 -> 0.8.5 (#516696)
• b4d504e code-cursor: 3.2.11 -> 3.2.21 (#516725)
• 5c4f318 code-cursor: 3.2.11 -> 3.2.21
• b1d01cf json-sort: 1.0.0 -> 1.1.0 (#516707)
• 8d92991 python3Packages.waymax: set license (#516507)
• 680ee27 pgdog: 0.1.38 -> 0.1.39 (#516702)
• e3187c5 json-sort: 1.0.0 -> 1.1.0
• bc57aba fluxcd: rewrite update script to use nix-update (#515726)
• db6e8bd pgdog: 0.1.38 -> 0.1.39
• 8c767e4 zerofs: 1.0.8 -> 1.1.0 (#515795)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[hyperpolymath]

Closing — CI failures here are dominated by known systemic issues already tracked separately:

• hypatia#213 (hypatia-cli exits 1 with no diagnostic on every consumer-repo CI run)
• idaptik#77 (Dogfood Gate / RSR Anti-Pattern pre-existing failures)
• neurophone#41 (external-action failures: a2ml, k9, hypatia, fuzz)

A separate workflow-linter.yml root-cause bug was also fixed today (YAML parse error + self-flagging grep) in gitbot-fleet and 9 affected repos.

Dependabot will regenerate this PR on its next polling cycle against a healthier CI baseline. Closing now to clear noise — current dep version remains in place (safe status quo).

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

[hyperpolymath]

Reopening — the close justification ("CI failures dominated by known systemic issues") was correct that the failures were systemic, but the conclusion to close was the wrong call: routine dependency bumps shouldn't be abandoned over external/infrastructure red CI.

Root cause for the recurring systemic red is being addressed: the pinned SHA for actions/upload-artifact@65c79d7... no longer resolves, breaking every Hypatia Security Scan + Static Analysis Gate workflow that uses it. Estate-wide fix PRs in flight:

• hyperpolymath/proof-of-work#44
• hyperpolymath/affinescript-vite#9

Once that SHA bump lands in this repo too (small follow-up), this PR's CI should clear and it can be merged normally.

🤖 Reopened by Claude Code as part of WIP recovery from a batch-close that abandoned routine bumps.