chore(deps): move to @antelopejs/dms-frontend 0.3.0

[alessaloisio]

Summary

@antelopejs/dms-frontend 0.3.0 removes the useColorMode shim (AntelopeJS/dms-frontend#43, breaking).

• @antelopejs/dms ≤ 0.4.2 still calls it on Settings › Appearance, so that pair fails with ReferenceError at runtime, or TS2304: Cannot find name 'useColorMode' in ajs dms verify-source.
• @antelopejs/dms 0.4.3 moved the color-mode preference to a dms-color-mode cookie (fix(layout): keep the color-mode preference in a dms-color-mode cookie dms#56) and requires dms-frontend ≥ 0.2.8: shared cookie refs read from the rendered request, fix(vue): share cookie refs and read them from the rendered request dms-frontend#36.
• The old pin, dms-frontend 0.2.6 with dms 0.4.3, runs the color mode degraded: no server-rendered class, and an Appearance change is not seen until a reload.

This PR moves the repo to renderer 0.3.0 and raises every selector of @antelopejs/dms to ≥ 0.4.3, so renderer 0.3.0 can only be combined with a dms that no longer uses the shim. A type: "package" module source is resolved against the registry at startup, but offline the core falls back to any cached version the range still allows, so >=0.4.0 could serve a cached 0.4.0–0.4.2.

Changes

• playground/antelope.config.ts: version: ">=0.4.0 <1.0.0", → version: ">=0.4.3 <1.0.0",
• playground/package.json: "@antelopejs/dms": ">=0.4.0 <1.0.0", → "@antelopejs/dms": ">=0.4.3 <1.0.0",
• playground/package.json: "@antelopejs/dms-frontend": "0.2.6", → "@antelopejs/dms-frontend": "0.3.0",
• src/test/harness.ts: version: ">=0.4.0 <1.0.0", → version: ">=0.4.3 <1.0.0",
• playground/pnpm-lock.yaml: resolved to dms-frontend 0.3.0 (and dms 0.4.3 where it is locked)

Related issue

Tracked in AntelopeJS/dms-frontend#45 (goal, compatibility matrix, all PRs and follow-ups). Follows AntelopeJS/dms-frontend#43 (shim removal, v0.3.0), AntelopeJS/dms#56 (dms 0.4.3) and AntelopeJS/dms#55 (color-mode rollout).

Verification

• 9/9 checks exit 0.
• Playground SSR (/auth/login): dark → class="dark", light → class="light", no cookie → no color class; exactly one script#dms-color-mode. Backend and frontend started cleanly.

How to test

1. pnpm install, then the repo's lint, typecheck and test scripts. See Verification for the expected exit codes.
2. Start the playground (backend, then frontend), and wait for .antelope/dev.json and "Server ready".
3. Check the color mode through SSR, no login needed:
   • curl -s -H 'Cookie: dms-color-mode=%22dark%22' http://localhost:3001/auth/login | grep -o '<html[^>]*>' contains class="dark";
   • with %22light%22: class="light"; with no cookie: no color class;
   • the HTML contains exactly one <script id="dms-color-mode".
4. Logged in, Settings › Appearance: pick Dark / Light / System and reload; the right option stays selected with no hydration warning.

Merge order

Independent of the other repos' PRs, so any order works. Its prerequisites are already released: dms-frontend 0.3.0, @antelopejs/dms 0.4.3 and @antelopejs/dms-database 0.0.9. It only changes dependency floors, playground and test configuration, so it needs no release of its own unless the repo publishes its playground or test harness.

Checklist

• The pull request title follows Conventional Commits.
• I added or updated tests when behavior changed. (Dependency floors only.)
• I updated documentation when users or contributors are affected. (Not affected.)
• I documented breaking changes and migration steps. (None for this repo; the breaking change is in dms-frontend 0.3.0.)
• I did not include credentials or unrelated changes.