test: anchor both copies of the resolution policy to the published package

[ralyodio]

The resolution rules exist twice here — moshpit-resolve.ts and a hand port into the extension, because the extension is plain JS and pnpm build is tsc, which compiles but doesn't bundle. A package can't be imported at runtime from an unbundled extension, so the copies stay.

What the existing test misses

moshpit.test.js compares the two copies against each other. That catches one drifting and misses both drifting together — which is the likely case, since the same person edits them in the same commit for the same reason.

This anchors each copy to @moshcoder/moshpit-resolve instead. The package is the reference; either copy leaving it is caught, including when they leave together.

Verified that specific gap

Changed CONSOLE_LABEL in both copies identically:

× extension  > agrees on the console label
× extension  > decides resolution identically across the whole input space
× extension  > shares the defaults
× typescript > agrees on the console label
× typescript > decides resolution identically across the whole input space
× typescript > shares the defaults

A copy-to-copy comparison stays green on that.

Behaviour, not bytes

The copies legitimately differ — comments, TypeScript types, and the chrome-coupled config reader the package deliberately doesn't carry. There's a test for that last one too: if moshpitConfig ever appears in the package, it has stopped being usable outside a browser.

Coverage: hostname parsing, gateway/parking URLs including a self-hosted pit, the console label, decideResolution across the full cross-product of mode × clearnet-resolves × registry-answer, and the shared defaults.

It actually runs

A dev dependency, and apps/desktop is a pnpm workspace member — so the root pnpm install --frozen-lockfile CI already runs reaches it. 111/111 desktop suite.

🤖 Generated with Claude Code

[github-actions]

vu1nz Security Review

0 finding(s) in PR #?

No security issues found.