chore(deps): @moshcoder/moshpit-resolve 0.1.1 -> 0.1.2

Unblocks main, red since #66 merged.

#66 dropped dashes from both local copies of the name grammar while the
published package still allowed them, so moshpit-drift.test.js failed on
blue.lazy-loaded — and not merely on parsing: the two disagreed on where
a tab goes, 'park' against the package and 'clearnet' against the new
rule. That is the anchor earning its place.

0.1.2 carries the rule. The lockfile is the part that matters: CI installs
frozen, so the ^0.1.1 range never picked the new version up on its own.

Scoped to the one package deliberately. Doing this with `pnpm update
--latest` first pulled the whole tree forward — TypeScript 5.9.3 to 7.0.2,
eslint 9 to 10, babel 7 to 8, 3509 lines of lockfile — and broke Lint with
"typescript-eslint does not support TS 7.0". This touches 11 lines.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: ralyodio

apps/desktop/package.json

@@ -24,7 +24,7 @@
     "chromium:package": "chromium/scripts/package.sh"
   },
   "devDependencies": {
-    "@moshcoder/moshpit-resolve": "^0.1.1",
+    "@moshcoder/moshpit-resolve": "^0.1.2",
     "typescript": "^5.6.3",
     "vitest": "^2.1.4"
   }