chore(flake): sync version + npmDepsHash [skip-flake-sync]

[jasonodoom]

Auto-generated by flake-sync.yml. Merges automatically once CI passes.

• version: 0.11.0 -> 0.11.0
• npmDepsHash: sha256-Bw2AayHybNF9NJBcjm3cL6KgNz4cvF5WS/3esbJB1jQ= -> sha256-IbxMY+aZeS4KOv0kolu/n0pN7DUG9pR7Nt84fyF1A3M=

[jasonodoom]

Superseded and closing. This proposes sha256-IbxMY+aZeS4KOv0kolu/n0pN7DUG9pR7Nt84fyF1A3M=, computed from the lockfile as it stood on 26 July. The conflict is because the line it edits no longer exists: #29 fixed the same drift minutes later, and #43 updated the hash again after last night's dependency patches.

Current main carries sha256-w4a+PeWnGNeLLfncGXKwuuLiziqBGlH7qNzR53IqiVc=, which is what prefetch-npm-deps package-lock.json computes for the lockfile on main today. Merging this would replace a correct hash with a stale one and break nix build.

Cause of the duplicates: seven queued pull requests merged between 22:00 and 22:06 UTC that day. Each push to main started a sync run, each correctly saw the same drift, and each opened its own pull request. The [skip-flake-sync] marker stopped the loop once #29 landed, so this was redundancy rather than a loop.